For some reason the latest update broke my logs
-
It's been working for me on amd64. I just started the builders recompiling their ports again to be on the safe side, so try the next new snapshots.
Hi,
I'm on 2.0-RC3 (amd64) built on Mon Jul 4 16:49:48 EDT 2011 now. (No newer available) and still no logs.
-
There has not been a new snapshot since my last post.
-
Strange, I have never lost logs on my amd64 box and I'm on the same July 4th snapshot. Have you tried a fresh install using a backup config?
-
Might also try to rm /var/log/*.log and then reboot.
A new snap just went up a bit ago, should be ok to try.
-
@onhel:
Strange, I have never lost logs on my amd64 box and I'm on the same July 4th snapshot. Have you tried a fresh install using a backup config?
I did a complete new installation. No restore of old configuration file - JUST "SYSTEM TUNABLES"
But don't know if there was the problem with the logs before I restored this part of the configuration. -
Fresh install from July 05, no logs (amd64). :-(
-
Just updated two boxes and get "Segmentation fault (core" on the logs.
They do not work past that.
2.0-RC3 (i386) built on Thu Jul 7 00:25:19 EDT 2011
-
And yet my amd64 VM that I just updated still has logs and works fine. Seems i386 is broken now though, investigating…
-
Just updated two boxes and get "Segmentation fault (core" on the logs.
They do not work past that.
2.0-RC3 (i386) built on Thu Jul 7 00:25:19 EDT 2011
I noticed the same thing, went back to an earlier snapshot for now
-
hm…
gdb -c core
gdb>btbut
gdb: Command not found. :-\
-
It's definitely something broken in the clog binary, I can copy just the clog binary from another box, reboot, and it's fine. It's not the reading the file that is the problem, it can read a valid file no problem, it's something in the way it's writing out the initial binary format of the file that's making it crash.
-
Should be OK in the next new snap.
-
-
For me logs are back.
HEAD (amd64) built on Wed Jul 6 22:00:09 EDT 2011
thx
