Only one entry in the systemlogs, cleared log and pfs reboots…
-
We will see, thanks
-
Same result for 7.1 -stable file: pfSense-Full-Update-1.2.3-20090606-0212
-
Same result for 7.1 -stable file: pfSense-Full-Update-1.2.3-20090606-0212
I confirm.
Any way to resolve without reinstalling a previous version? -
I confirm the same. And on the proven system.
Also believe, and permanently deleted last good :
pfSense-Full-Update-1.2.3-20090603-1437.tgz
Will have to download. -
Yeah the clog issue is still there, and there were a couple that were missing kernels.
Just keep waiting and testing for now, but there may not by anyone around to try to fix it for a while today.
-
Same result for 7.1 -stable file: pfSense-Full-Update-1.2.3-20090606-0212
Same for: pfSense-Full-Update-1.2.3-20090607-0605
-
From the discussion I saw last night, there are two things:
#1: The clog problem springs up when something in a builder gets corrupted so badly it may need redone from scratch, not an easy piece of work.
#2: 1.2.3 is moving to 7.2 anyhow, so the effort to fix #1 may not be worth it
So It would probably be in everyone's best interest to focus testing on the 7.2 based snapshots.
-
Ok, installed latest snapshot of 7.2, but the problem with the logs persist… :(
-
So I see, I just tried it myself.
Even so, fixing it on one builder is less effort than fixing it on two…
If I copy the clog binary from a working system and then reboot, it works.
I'll post an experiment to try in this other thread for 7.2:
http://forum.pfsense.org/index.php?topic=16670.new;topicseen#new -
So I see, I just tried it myself.
Even so, fixing it on one builder is less effort than fixing it on two…
If I copy the clog binary from a working system and then reboot, it works.
I'll post an experiment to try in this other thread for 7.2:
http://forum.pfsense.org/index.php?topic=16670.new;topicseen#newPerferct! it runs!
-
So I see, I just tried it myself.
Even so, fixing it on one builder is less effort than fixing it on two…
If I copy the clog binary from a working system and then reboot, it works.
I'll post an experiment to try in this other thread for 7.2:
http://forum.pfsense.org/index.php?topic=16670.new;topicseen#newThe temp fix works here for me too, yey.
I extracted the clog file from the last working build (pfSense-Full-Update-1.2.3-20090603-1437 ), put it on my webspace and execute the fetch command and chmod, rebooted, everything works :) ;) ;D -
Looks like the clog issue will be fixed in the next snap, whenever that finishes building. I've tested the clog binary that will be in that snapshot and it works for me.
-
Great! Thanks
-
FYI, the logs are fine on the snapshots from today (2009-06-08)
-
Works, thanks.
BTW, is it offcial RC2 ?, thare´s no annoucement about it on webpage.
-
Works, thanks.
BTW, is it offcial RC2 ?, thare´s no annoucement about it on webpage.
It was bumped after the Load Balancing changes so that problem reports might better be classified. I don't think there has been an 'official' rc2 build yet.
-
I did an upgrade this morning to the latest snapshot and am getting the same error.
updates based on 7.1 -
I did an upgrade this morning to the latest snapshot and am getting the same error.
updates based on 7.1There are no longer updates based on 7.1, are you sure you are using the proper snapshots?
The current updater URL for the automatic updates is:
http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/.updatersOr you can view the list of current snapshots for 7.2 here:
http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/updates/ -
Thanks, I was 90% sure that the 7.2 was the problem, so I mentioned it in my original post.
my updater was pointing to 7_1 and I did not know it was 7.2 now.
I'm thinking this will get more people than me.Is there a reason the broken 7.1 release is available for the updater? I'd think no release is better and we would have to look to find the updater link for 7.2??
Thanks for the tip!
-
Thanks, I was 90% sure that the 7.2 was the problem, so I mentioned it in my original post.
my updater was pointing to 7_1 and I did not know it was 7.2 now.
I'm thinking this will get more people than me.Is there a reason the broken 7.1 release is available for the updater? I'd think no release is better and we would have to look to find the updater link for 7.2??
Thanks for the tip!
They may still be useful for some debugging, but their value declines on a daily basis.
The update manifest has been changed so that the 1.2.3 snapshots should be pulling from 7_2 now but I don't know if that will automatically fix people or if they'll have to go into the auto update settings and re-pick the 1.2.x snapshots choice.
