4th feb nanobsd issues
-
i think the cron package install causes this once firmware is upgraded and booting up, that time it tries to install the cron package and crashes and reboots. the second time up it skips the cron install and works well till i force a cron install which installs but crashes and third time up, cron is already there and working so keeps working well, atleast for the past 30mins i used, still waiting for a crash
-
Not just the nanobsd. Happened on my i386 standard install too.
Except it never got over the issue even after several reboots.
Was nice to have a duplicate usb flash drive on hand and ready to go.
This was with the afternoon build. About 5 pm ish I think.
-
Not just Nano, it's all builds since yesterday, see here:
https://redmine.pfsense.org/issues/2793I pulled the snapshot and update files once I realized it was bad. It's a good thing I decided to update my test VM last night or there would be a lot more broken installs out there…
I can't get my VM to stay up long enough to even roll back to a previous update.
-
I'm currently running 2.1-BETA1 (amd64) built on Mon Feb 4 03:47:19 EST 2013, was it the release marked for a few minutes later or just the updater that is broken? I installed it yesterday from memory stick (pfSense-memstick-2.1-BETA1-amd64-20130204-0347). I saw a "update found" right after install that had the build time a few minutes after my downloaded version.
-
this is strange because after a few reboots as i mentioned in my first post, my device is working fine from past 8 hours
-
It was the snapshot from yesterday evening, the timestamp started with 17 (1704 or 1708, depending on if it was amd64 or i386)
-
yes exactly, what i noticed was even reverting to the previous slice gave those errors and after a few reboots worked fine
-
I updated an i386 yesterday and the web interface stopped working today. So I pulled a image from the snapshots link updated that and started getting kernel panic's.
Should of known there were problems as the update server was taken down!
-
I found this the hard way last night at 12AM myself :(
Anyway I could not recover or get it to stay up.
What did seem to work is I did a full clean reinstall with livecd (that buildstamp) and restored the config and 0 issues.
So is it just something that is failing to upgrade?
That said should my next upgrade work or does this one contain something bad and i need to rewipe and start fresh on the next bill?
-
Unless you saved the bad snapshot locally and rewrote it, you didn't do what you thought you did.
I erased the bad snapshot from the snapshot server as soon as I found it was bad. The one that was up there earlier was from early in the day yesterday and was ok.
Now the new one is uploading and it appears to be fine so far.
-
I did the update at around 11pm fine, logged in and started to reload packages. connection lost.
I drove to office and was crashed, every reboot would allow about 1 min of uptime and die again.
I download the live CD and notice it says built on Mon Feb 4 03:44:47 EST 2013 and reinstalled and all was fine.
So are you saying my upgrade caught the bad 17xx time build and the live cd download was 0344 thus why this worked? You must have caught around the same time I did all this that the upgrade grabbed bad one but live cd download an hour later was older :P
So I guess I should be fine, I didn't catch my current time said 0344 doh!
Thanks for the reply and sorry for double post in other thread.
-
Yep, the 03xx was good. 17xx was bad.
-
I am getting this error as well. It is the Feb 4th live cd I downloaded. What is the remedy?
-
Upgrade to a snapshot from the 5th.
-
Upgrade to a snapshot from the 5th.
thanks!..quick question, being new to Pfsense let alone freebsd, if I do a snapshot install, when the stable release comes, will I have to re-configure my system? or will the upgrade sufice?
-
Just upgrade to the release and it's fine.
