Project

General

Profile

Actions

Bug #3749

closed

Upgrade from 2.1.4 to 2.2 does not automatically reboot

Added by Jim Pingle over 9 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Upgrade
Target version:
Start date:
07/08/2014
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:
i386

Description

After an upgrade from 2.1.4 to 2.2, the firewall does not automatically reboot. The architecture stayed the same, but the reboot script failed to run.

The upgrade log has a couple errors early:

tar: Failed to set default locale
x ./tmp/pre_upgrade_command
Firmware upgrade in progress...
Installing /root/latest.tgz.
tar: Failed to set default locale
./var/empty/: Can't set user=0/group=0 for var/emptyCan't update time for var/empty
./boot/loader.rc: Could not unlink
tar: Error exit delayed from previous errors.
Image installed /root/latest.tgz.

After the output from mtree, there is a more significant error:

Out of file descriptors
Tue Jul  8 14:46:30 CDT 2014

Firmware upgrade is complete. Rebooting in 10 seconds.

Only the reboot never happens. Attempting to use the PHP reboot script fails.

: /etc/rc.reboot 
Out of file descriptors

This leaves the system in an inconsistent state (8.3 kernel, 10.x world).

Tested on i386 but may happen on both.

Actions #1

Updated by Renato Botelho over 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #2

Updated by Trond Vindenes over 9 years ago

Tested upgrade of both 32bit and 64bit full installation 2.1.4 to todays latest snapshots:
32bit: Thu Aug 14 10:06:14 CDT 2014
64bit: Thu Aug 14 06:56:40 CDT 2014

"Out of file descriptors" does appear in the console at the end of the upgrade, but it reboots into pfSense 2.2 successfully :)

Actions #3

Updated by Renato Botelho over 9 years ago

  • Status changed from Feedback to Resolved
Actions #4

Updated by Braden McGrath almost 9 years ago

This also happens on 2.1.5, and just occurred for me on a 2.1.5 -> 2.2.2 upgrade (x64/AMD64).

I have remote web access to the system but SSH doesn't seem to be working. Any ideas to finish the reboot at this point? :(

Actions #5

Updated by Braden McGrath almost 9 years ago

Braden McGrath wrote:

This also happens on 2.1.5, and just occurred for me on a 2.1.5 -> 2.2.2 upgrade (x64/AMD64).

I have remote web access to the system but SSH doesn't seem to be working. Any ideas to finish the reboot at this point? :(

Bah, realized after posting I could do /sbin/reboot via Diagnostics -> Command Prompt. That got the system alive again, thankfully the upgrade doesn't fail until the reboot stage... but whatever you guys did to fix it didn't actually fix it for 2.1.5 -> 2.2.2.

Actions #6

Updated by Bipin Chandra almost 9 years ago

i had the exact same issue when i upgraded one box from 2.1.5 to 2.2.2, it didnt reboot, ssh was lost, only web gui was working, luckily i had cron installed so i create a reboot entry which worked and then after reboot, i upgraded again with the latest 2.2.2 file as unbound wasnt running due to some file permission issue, then all came up and working fine so far

Actions #7

Updated by Peter Allebone almost 9 years ago

ALso had the sam issue with 2.1.5 to 2.2.2 with a Vmware cluster of 2 machines in CARP. I saw it hung on reboot in the system logs but didnt know how to reboot it so just tried resetting the VM since I had a snapshot. Came back up fine and worked but nice tip on using the diagnostics-cmd prompt. Will try that next time if it happens again.

Actions #8

Updated by Mark Underhill over 8 years ago

Also had same problem refusing to reboot in 2.2.2. I was able to get to console but reboot failed there too. But on shell I was able to run "shutdown -r now" and that worked. After subsequent upgrade to 2.2.4 reboot worked normally.

Actions

Also available in: Atom PDF