2.1.5->2.2.2 system does not reboot after upgrade, requires power cycle
-
I've upgraded two 2.1.5 systems to 2.2.2. After the upgrade they showed in the dashboard that they were up to date, but uptime showed they were not rebooted. Manual reboots and halts do not work. I had to power cycle the systems. Errors in the logs are:
Apr 28 09:22:33 php: /reboot.php: The command 'nohup /etc/rc.reboot > /dev/null 2>&1 &' returned exit code '2', the output was ''
Apr 28 09:22:33 php: /reboot.php: Stopping all packages.
Apr 28 09:22:33 php: /reboot.php: The command '/usr/local/bin/beep.sh stop' returned exit code '2', the output was 'Out of file descriptors'
-
Known issue with mtree junk. https://redmine.pfsense.org/issues/4653
-
Thanks. I hope it gets sorted soon as it is a real pain having to have someone on site to cycle the power.
-
Known issue with mtree junk. https://redmine.pfsense.org/issues/4653
mtree is not "junk" – far from it.
The problem is that at the problem point in the upgrade, the binaries are for FreeBSD 10 on the disk but the kernel is still running FreeBSD 8.x, so hilarity ensues.
-
I seem to be in the same boat. 2.1.5 > 2.2.2 upgrade on 2 installations. I have openvpn and both endpoints are "upgraded" and still passing traffic. Dashboards report 2.2.2-RELEASE. Should I force reboot from ssh or are there other housekeeping commands before I do? I will not have physical access to my remote site for several days if this all goes south. Thanks
-
I have had the same problem. Reported to support.
Was this an issue for 2.1.5 to other 2.2.x versions?
I had to wait to upgrade due to the limiter problem…which i thought was fixed in 2.2.2 :(
(that is with support also)
-
My issue was resolved by rebooting from web interface. I was not able to ssh into either device.
-
After upgrading today from 2.1.5 to 2.2.2 I am having this same issue. Cant reboot or halt system from the webgui and can't connect with SSH. Do you recommend power cycling the server or should i wait?
-
Waiting won't get you anywhere.
-
So the only answer here to force a reboot?
Does it let you reboot from the GUI after that?
I have four firewalls and I have to travel to get to all of them.
-
-
I have to say I don't find much "hilarity" in this. I don't think updates should be pushed out if they don't actually work as one would expect. I hope this gets fixed in a later release.
-
I have to say I don't find much "hilarity" in this. I don't think updates should be pushed out if they don't actually work as one would expect. I hope this gets fixed in a later release.
The 2.2.3 snapshots don't currently exhibit any of these symptoms, at least not for the scenarios I have tested. If others could try going from 2.1.x to 2.2.3 snapshots and posting the upgrade logs, it would be appreciated.
-
Hi Jimp,
I have tested upgrading with one of the latest nanoBSD development images (pfSense-2.2.3-DEVELOPMENT-4g-i386-nanobsd-vga-upgrade-20150623-1513.img). This upgraded my 2.1.5 (Soekris 6501-50 w/USB) without issue. The unit rebooted, re-installed packages and came up fine. It did leave the filesystem in RW mode, but a flip of the switch under the nanoBSD menu solves that. It also comes back as RO after a reboot.I just ran the "auto-updater" this morning with today's official release of 2.2.3. I upgraded two 2.2.2 units successfully and one 2.1.5 unit successfully, with no rebooting or hanging issues whatsoever. That is a better experience than the earlier versions. :)
Sorry to be ignorant, but from where can I retrieve the upgrade logs? I would like to help if you still need this information.
-
If it all worked fine then there isn't much to report now :-)
We fixed all the known issues we could find with upgrading, 2.2.3 should be a much better experience for everyone all-around.
The upgrade log is in /conf/upgrade_log.txt if you want to review it.
-
Cool, thanks. And thanks to the whole PFSense team for the most recent update!
-
Newbie here. Working through all things pfSense. This was one of them.
I put an old Dell laptop to use with pfSense for routing and radius functions. Had problem where, from the main console menu, when I choose reboot (option 5) it goes until it stops the system and the last message is the "Uptime…" then it just hangs. I have to force a hard power off.
Googled everything I could find, most folks suggested ACPI, so I went looking for it in the BIOS, but it's not there. While I was there I noticed that this system had AHCI enabled for the HD controller, which is fine for windows and intel parties, but I dont' think it helps in pfSense under freeBSD! Or am I wrong here ?
Anyway, I changed the HD controller function back to the Dell default of ATA, not thinking it was connected. When I booted and did a reboot, it worked.
For what it's worth, something about AHCI seems to mess with the reboot process. I'm running 2.2.5
