Reboot stuck at "Syncing packages: Unbound" or "IPSec: Initialized Security[…]
-
I'm using pfSense 2.0-BETA5-amd64 built on Feb 5 inside vmware player 3.1.3 without vmware tools installed (yet).
pfSense was working great, so I decided to shutdown and backup the entire virtual machine (not just the exported pfSense configuration.) since vm was under 500 MB.
During reboot, it shows "Syncing packages: Unbound" and doesn't proceed. I waited more than 15 minutes. Pressing ctrl-c twice simply repeats the process and it gets stuck again.
The host and vm both had idle cpu and hd, and the host had 5 GB RAM free out of 8 GB.
When I reboot with more logging, I see "t_delta 15.xxxxxxxxxxxxxx too short" and "t_delta 16.xxxxxxxxxxxxxx too long" messages while stuck syncing Unbound package (where xx is some long hex value.)
When I reboot in safe mode, it gets stuck after displaying "IPSec: Initialized Security Association Processing." console message. Pressing ctrl-c does nothing at this point.
-
Do you have 'Cache Restoration Support' support enabled?
-
Replied in the other thread in the Packages section of the forum but wanted to add some info here as well.
Yes, Cache Restoration Support was enabled. In the most recent snapshot, I decided to just disable Unbound, enable the pfSense DNS Forwarder and then update to the latest snap to avoid the hang. Unbound was just disabled, not uninstalled. I got the following in the logs after the snapshot update and thought they might be helpful in solving the issue. Thanks in advance for your much appreciated hard work.
Feb 16 01:29:47 php: : The command '/usr/sbin/fifolog_create -s 32768 /var/log/unbound.log' returned exit code '1', the output was 'fifolog_create: Wrong file type: File exists' Feb 16 01:29:47 check_reload_status: syncing firewall Feb 16 01:29:24 check_reload_status: syncing firewall Feb 16 01:29:22 php: : Beginning package installation for Unbound. Feb 16 01:29:18 check_reload_status: syncing firewall Feb 16 01:29:17 check_reload_status: syncing firewall Feb 16 01:29:13 php: : Reinstalling package Unbound because its include file(/usr/local/pkg/unbound.inc) is missing! Feb 16 01:29:13 php: : The Unbound package is missing required dependencies and must be reinstalled. Feb 16 01:29:13 php: : The Unbound package is missing required dependencies and must be reinstalled. Feb 16 01:29:13 php: : The Unbound package is missing required dependencies and must be reinstalled. Feb 16 01:29:13 kernel: 118>Syncing packages: -
Reinstallation of unbound doesn't work "fluffy" (on my side). I have to deinstall and then install unbound after every update. Simple reinstall won't work.
So what happens on update? unbound is reinstalled like all other packages. All packages work except unbound: It starts, but no DNS is available. Only cached sites are available. If i want to surf a page which i never (or really rarely) called before, it ends up with a "Not known". After the deinstall and install of unbound all works as expected.
Other thing i encountered, is the fact that the simple call of unbound-status resulted in a complete hang of the whole Web-IF, if i had not installed manually before.
Cache restoration is activated here too. I will test with it disabled and put in here the result.edit:
Did the actual firmware-update from 02/14 to 02/16.
Disabling the Cache-restoration results in a fine-working unbound after firmware-update! Hope that helps. -
Did the actual firmware-update from 02/14 to 02/16.
Disabling the Cache-restoration results in a fine-working unbound after firmware-update! Hope that helps.yeah this is the problem, thanks - I should have it all sorted this weekend. In the interim just disable it until I can issue a fix.
-
I reinstalled without unbound so I'm not sure, but this sound promising. Looking forward to retrying unbound after this is worked out.
Thanks!
-
HI all,
apologies for the delayed response. I have made a couple of changes and cant reproduce the problem since these changes.
So please let me know if you still have issues. -
So cache restoration can be enabled again? I'll try and comment back. Thanks!
-
Thats correct - just reinstall the package. There was also a double syncing of the package happening caused by an extra dependancy which was not needed.
