Only one entry in the systemlogs, cleared log and pfs reboots…
-
+1 - I can confirm this effect.
-
+1 - I can confirm this effect.
Testest updating using this file: pfSense-Full-Update-1.2.3-20090605-0110
System log say: Segmentation fault (coreIm backflashing to pfSense-Full-Update-1.2.3-20090603-1437 version, that one works for me still….
-
That thing again… It pops up now and then, something with the clog binary isn't coming out of the build process right.
Was this a snapshot based on FreeBSD 7.1 or 7.2?
-
my snapshot came from this section …
7.1 1.2.X 1.2.3 - STABLE
-
1.23 RC1 to RC2 with the Auto Updater
-
Have to wait for the next snapshot to see, but it looks like some potential fixes for this went into the tools tree.
-
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)
