For some reason the latest update broke my logs



  • I'm not able to get any logs to show up in system logs.  Any idea when the next snapshot comes out?



  • Me too  :-\

    The snapshot is
    2.0-RC3 (i386) built on Tue Jun 28 14:28:07 EDT 2011

    -Raylund



  • True. This snapshot show blank log.



  • More information.  I find this on "/status.php#DMESG"

    Starting syslog…
    /libexec/ld-elf.so.1:
    Shared object "libczmq.so.0" not found, required by "syslogd"

    -Raylund



  • Same here: Shared object "libczmq.so.0" not found, required by "syslogd".



  • Yup, me too.

    Starting syslog…
    /libexec/ld-elf.so.1:
    Shared object "libczmq.so.0" not found, required by "syslogd"

    Bummer.



  • I dont see this on my amd64 box, but system logs are empty on my 386 nanobsd ALIX.



  • One thing I also noticed after this update was that my squid didn't reinstall after the update.  I manually installed it and all the settings were there and it started working.

    Also - problem still exists in Tue Jun 28 21:28:47 EDT 2011 snapshot.



  • I did encounter the same problem with syslogd on yesterdays snapshots for i386
    Obviously the libczmq.so.0 and libzmq.so.0 were missing.
    To fixit in my pf-jail machine I did:
    portsnap fetch extract
    cd /usr/ports/devel/czmq
    make
    after compile I simply copied those two libraries from czmq and zmq work folders to /usr/lib and started syslogd, and I'm back online with my logs.
    ldd /usr/sbin/syslogd
    /usr/sbin/syslogd:
    libutil.so.8 => /lib/libutil.so.8 (0x2809c000)
    libczmq.so.0 => /usr/lib/libczmq.so.0 (0x280ab000)
    libzmq.so.1 => /usr/lib/libzmq.so.1 (0x280b8000)
    libthr.so.3 => /lib/libthr.so.3 (0x280f2000)
    libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x28107000)
    libc.so.7 => /lib/libc.so.7 (0x281fb000)
    libm.so.5 => /lib/libm.so.5 (0x28315000)
    libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2832f000)
    I would likely post these two files becouse that is all you need, if someone would point me some ftp location.



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



  • happen to me to  ;)

    2.0-RC3 (i386)
    built on Tue Jun 28 21:28:47 EDT 2011



  • just updated to 2.0-RC3 (i386) built on Tue Jun 28 21:28:47 EDT 2011

    and still no logs



  • The changes wont show till the next build, later today.



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

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



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

    thanks!  :D



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


  • 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 ?



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



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



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


  • Rebel Alliance Developer Netgate

    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.



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


  • Rebel Alliance Developer Netgate

    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?


  • Rebel Alliance Developer Netgate

    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


  • Rebel Alliance Developer Netgate

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



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



  • hm…
    gdb -c core
    gdb>bt

    but

    gdb: Command not found. :-\


  • Rebel Alliance Developer Netgate

    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.


  • Rebel Alliance Developer Netgate

    Should be OK in the next new snap.



  • @jimp:

    Should be OK in the next new snap.

    thanks jimp!



  • For me logs are back.

    HEAD (amd64) built on Wed Jul 6 22:00:09 EDT 2011

    thx


Locked