[SOLVED] Dashboard/Console stuck??

Started by Supermule, July 09, 2015, 09:46:29 AM

Previous topic - Next topic
July 09, 2015, 09:46:29 AM Last Edit: July 30, 2015, 09:37:20 AM by franco
Finding Dashboard/Console stuck.

It upgraded fine during the webgui update.

One more since I cant put images in same post because of very limited upload sizes.

Brian, is the GUI responsive? Is the console hanging there forever? If so, what happens on CTRL+C?

GUI is responsive. CTRL+C makes the console come alive and go to the default screen with options.

Does the proxy log give any hints as to why it hangs? Are you using /tmp + /var MFS options?

System Log:

May 31 19:04:42    kernel: done.
May 31 19:04:24    kernel: done.
May 31 19:04:24    kernel: WARNING: /mnt was not properly dismounted
May 31 19:04:24    kernel: WARNING: /mnt: reload pending error: blocks 88 files 4
May 31 19:04:24    kernel: WARNING: /mnt: mount pending error: blocks 88 files 4
May 31 19:04:24    kernel: WARNING: /mnt was not properly dismounted
May 31 19:04:24    kernel: Trying to mount root from ufs:/dev/da0s1a [rw,noatime]...
May 31 19:04:24    kernel: SMP: AP CPU #3 Launched!
May 31 19:04:24    kernel: SMP: AP CPU #2 Launched!
May 31 19:04:24    kernel: SMP: AP CPU #1 Launched!
May 31 19:04:24    kernel: da0: 20480MB (41943040 512 byte sectors: 255H 63S/T 2610C)
May 31 19:04:24    kernel: da0: Command Queueing enabled
May 31 19:04:24    kernel: da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit)

Proxy Log:

2015/07/09 09:37:38 kid1| Set Current Directory to /var/squid/cache
2015/07/09 09:37:38 kid1| Starting Squid Cache version 3.5.3 for amd64-portbld-freebsd10.1...
2015/07/09 09:37:38 kid1| Service Name: squid
2015/07/09 09:37:38 kid1| Process ID 22264
2015/07/09 09:37:38 kid1| Process Roles: worker
2015/07/09 09:37:38 kid1| With 117000 file descriptors available
2015/07/09 09:37:38 kid1| Initializing IP Cache...
2015/07/09 09:37:38 kid1| DNS Socket created at [::], FD 6
2015/07/09 09:37:38 kid1| DNS Socket created at 0.0.0.0, FD 8
2015/07/09 09:37:38 kid1| Adding domain 22tv from /etc/resolv.conf
2015/07/09 09:37:38 kid1| Adding nameserver 127.0.0.1 from /etc/resolv.conf
2015/07/09 09:37:38 kid1| Adding nameserver 81.19.224.67 from /etc/resolv.conf
2015/07/09 09:37:38 kid1| Adding nameserver 194.239.134.83 from /etc/resolv.conf
2015/07/09 09:37:38 kid1| Adding nameserver 193.162.153.164 from /etc/resolv.conf
2015/07/09 09:37:38 kid1| Adding nameserver 8.8.4.4 from /etc/resolv.conf
2015/07/09 09:37:38 kid1| Logfile: opening log daemon:/var/log/squid/access.log
2015/07/09 09:37:38 kid1| Logfile Daemon: opening log /var/log/squid/access.log
2015/07/09 09:37:38 kid1| Store logging disabled
2015/07/09 09:37:38 kid1| Swap maxSize 0 + 262144 KB, estimated 20164 objects
2015/07/09 09:37:38 kid1| Target number of buckets: 1008
2015/07/09 09:37:38 kid1| Using 8192 Store buckets
2015/07/09 09:37:38 kid1| Max Mem  size: 262144 KB
2015/07/09 09:37:38 kid1| Max Swap size: 0 KB
2015/07/09 09:37:38 kid1| Using Least Load store dir selection
2015/07/09 09:37:38 kid1| Set Current Directory to /var/squid/cache
2015/07/09 09:37:38 kid1| Finished loading MIME types and icons.
2015/07/09 09:37:38 kid1| HTCP Disabled.
2015/07/09 09:37:38 kid1| sendto FD 12: (1) Operation not permitted
2015/07/09 09:37:38 kid1| ipcCreate: CHILD: hello write test failed


But I didnt allow IPv6 but it still works. :) after hitting CTRL+C in the console.

Squid seems to be running.

I think it only seems that way, squid will be running but not functioning properly.
Pretty certain that if you allow ipv6 the issue will be resolved, then you can block ipv6 traffic on the external interfaces if you want to.



If you run on the cli:

configctl proxy status

It should say squid is running as pid #####
Then at least the system knows it has been started, but to make sure it is actually working you need to try it out..

I have seen the IPv6 issue before and noticed that squid spawned two porcesses but did not pass traffic..

It says Squid is not runnning.

Getting this error in dashboard when trying to restart it.

QuoteFatal error: Uncaught exception 'Exception' with message 'Timeout (120) executing :proxy restart' in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php:100 Stack trace: #0 /usr/local/etc/inc/util.inc(148): OPNsense\Core\Backend->configdRun('proxy restart', false) #1 /usr/local/etc/inc/service-utils.inc(560): configd_run('proxy restart') #2 /usr/local/www/status_services.php(40): service_control_restart('squid', Array) #3 {main} thrown in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php on line 100

No matter what I do, I cant restart it via the gui or anywhere else.

Enabled IPv6 on both interfaces. No change.

This is a bug.

You need to set allow ipv6 as i said in my other post.. see link above.
Not on interface. And then reboot as the squid processes wont stop.

Or kill each squid process manually.

That is all. :)

Will try. Get back to you soon.