NanoBSD version 8.1.2011 update does not Reboot and finalize the update

[Clouseau]

I have now tried twice to upgrade my Alix board with NanoBSD image from 8.1.2011:
Latest Version : Sat Jan  8 16:48:05 EST 2011   File size: 65377564

My old image is from december 30. The update process seems to go thru "fine" until it's time to reboot in 10 seconds. It never reboots!

System log has this error line: php: : The command '/etc/rc.reboot > /dev/null 2>&1' returned exit code '2', the output was ''

Anyone has the same issue?

P.S Manual Reboot option from console does not work and neither from webConfigurator. This just refresh the console menu and that's it.

Update on issue ==> Had to make a "hardboot". Now it booted up to new slice with new updated image 8/1 but igmpproxy service had to be started manually. pfSense seems to be working fine.

[rpsmith]

nanobsd - net5501:

same update/reboot problem here.

Roy…

[rpsmith]

nanobsd Sun Jan  9 18:58:16:

Still won't reboot after update.

Roy…

[rcfa]

These are the kind of bugs I'm afraid of the most, because once my boxes are deployed, a bug like that means a round-trip air fare plus hotel, or expensive handling fees, FedEx top-priority overnight shipping, no sleep and a few days worth of internet down time…  :o :(

[quistler]

Same problems with the autoupdate on my VMware pfsense. it's stuck while rebooting.
The solution was to reboot in save mode. with fixed the problem. after that i could normally boot.

Happend on the Saturday and Monday update to me.

[rpsmith]

This problem still exist as of today's snapshot.  However, since no developer has bothered to respond, I will not waist everyone's time by continuing to report it.

Roy…

[Wolfsokin]

@rpsmith:

This problem still exist as of today's snapshot.  However, since no developer has bothered to respond, I will not waist everyone's time by continuing to report it.

Roy…

Dude, it has only been a day and the developers are not paid employees for a company that you pay a fee to so you can use their software. Relax a bit and see what happens.

:edited to add
If this is really a critical problem then maybe you should not be deploying a beta in a production environment.

[rpsmith]

this is my home test firewall.  I use it primarily for testing snapshots.  if you have people volunteering to test your code, you could at least take a minute to acknowledge a problem when they report one.  common courtesy.  no one is forcing anyone to code or for that matter to test snapshots.

Roy…

[Wolfsokin]

@rpsmith:

no one is forcing anyone to code or for that matter to test snapshots.

Exactly. Chill for a few days and see what happens  ;)

[jimp]

Even if using the auto reboot doesn't happen, and the console menu option doesn't work (which is being investigated), you can always drop to a shell and just type "shutdown -r now" or "reboot". Though the shutdown method is preferred between those two, neither is as good as using /etc/rc.reboot or Diagnostics > Reboot from the GUI, when they work.

[Clouseau]

@jimp:

Even if using the auto reboot doesn't happen, and the console menu option doesn't work (which is being investigated), you can always drop to a shell and just type "shutdown -r now" or "reboot". Though the shutdown method is preferred between those two, neither is as good as using /etc/rc.reboot or Diagnostics > Reboot from the GUI, when they work.

Yep, did not try those commands ""shutdown -r now"" or "reboot" - I just made a hardboot and that's it. This is my primary FW at home, but I still want to use these 2.0 beta builds. I really want to follow up how things evolve. This is stable enough to me. You should NOT use this in production or environments that are difficult to reach if these kind of "bugs" hits you. If it works - do not "repair" !

pfSense is great! Good work all of you  8)

[jimp]

I think I know what caused the reboot failure, hopefully will have something checked in today to fix it up.

[jimp]

I think I tracked it down, I just committed a fix and restarted the builders.

N.B.: The next update may still not reboot, but the one after it will, since at the time you do the update you are still running the 'old' code, and won't be on the 'new' code until after the next reboot.

If it doesn't reboot, just go to a shell and run

shutdown -r now

[jlepthien]

Guys, watch out for open tickets… ;-)
http://redmine.pfsense.org/issues/1179

[jimp]

I'm not entirely certain I ever woke up today. :-)

Ticket is updated now

[jlepthien]

@jimp:

I'm not entirely certain I ever woke up today. :-)

Ticket is updated now

I wasn't talking to you ;)

[Clouseau]

@jlepthien:

Guys, watch out for open tickets… ;-)
http://redmine.pfsense.org/issues/1179

Thanks, but I stay here in 2.0-BETA Snapshot Feedback and Problems forum  ;D

[rpsmith]

nanobsd - Wed Jan 12 20:33:23 EST 2011:

rebooted normally after update.

Thanks jimp!

Roy…

[jlepthien]

@Clouseau:

@jlepthien:

Guys, watch out for open tickets… ;-)
http://redmine.pfsense.org/issues/1179

Thanks, but I stay here in 2.0-BETA Snapshot Feedback and Problems forum  ;D

No need for additional threads if there is an open ticket…

[rpsmith]

@jlepthien:

Guys, watch out for open tickets… ;-)
http://redmine.pfsense.org/issues/1179

Cool - Thanks for the link!

Roy…