For some reason the latest update broke my logs

mentalhemroids

Yea!!! It's working again! Thank you!

Wed Jun 29 13:40:13 EDT 2011 Works!

ariyako

confirm log work again on 2.0-RC3 (i386) built on Wed Jun 29 13:40:13 EDT 2011

thanks! :D

Nachtfalke

Hi,

I still have no logs on amd64 snapshot 30 june.

Starting syslog...
Jul  1 20:57:38  syslogd: /var/log/ntpd.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/ppp.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/pptps.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/poes.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/l2tps.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/ipsec.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/openvpn.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/apinger.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/relayd.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/filter.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/vpn.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/portalauth.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/dhcpd.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/system.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/system.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/system.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/system.log: No such file or directory
Jul  1 20:57:38  syslogd: /var/log/system.log: No such file or directory
done.

Nachtfalke

Hi,

I updated to 2.0-RC3 (amd64) built on Fri Jul 1 23:19:47 EDT 2011 but there are still no logs.
Isn't there anyone else who has this problem on amd64 fullinstall ?

mentalhemroids

All mine are working, but they are x86 updates. Wish I could confirm for you.

Nachtfalke

@ermal:

I included the copying of lib*zmq in the build so next snapshot will be there.

ermal fixed it for the x86 builds but there is an error in the amd64, too. Not sure if it is the same or another one.

Nachtfalke

Still no log on:
2.0-RC3 (amd64) built on Sun Jul 3 04:02:48 EDT 2011

jimp

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.

Nachtfalke

@jimp:

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.

jimp

There has not been a new snapshot since my last post.

AhnHEL

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?

jimp

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.

Nachtfalke

@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.

_igor_

Fresh install from July 05, no logs (amd64). :-(

chpalmer

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

jimp

And yet my amd64 VM that I just updated still has logs and works fine. Seems i386 is broken now though, investigating…

Cino

@chpalmer:

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

Notanial

hm…
gdb -c core
gdb>bt

but

gdb: Command not found. :-\

jimp

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.

jimp

Should be OK in the next new snap.