2.1.4 Has stopped logging

  • Logging has suddenly quit on on my pfsense box.

    I've already restarted the box as well as syslogd.

    What is causing this to occur? Whats odd is that the Filter log still logs, its the rest of the logs that have stopped. I'd love to provide log output but they don't work!

    The only thing thats acting strange is that when trying to clog -f the system log i get

    clog: ERROR: could not write output (Bad address)

  • I rebooted the FW and now I'm getting

    /etc/rc.d/syslogd start
    Starting syslogd.
    syslogd: child pid 78120 exited on signal 11
    /etc/rc.d/syslogd: WARNING: failed to start syslogd

  • Banned

    Check your diskspace

  • Disks look fine:
    [2.1.4-RELEASE][root@945-1383.atlantic.net]/etc(71): df -h
    Filesystem                      Size    Used  Avail Capacity  Mounted on
    /dev/mirror/pfSenseMirrors1a    56G    619M    51G    1%    /
    devfs                          1.0k    1.0k      0B  100%    /dev
    /dev/md0                        3.6M    52k    3.3M    2%    /var/run
    devfs                          1.0k    1.0k      0B  100%    /var/dhcpd/dev

    I am however getting this error

    /etc(70): /usr/sbin/syslogd -s -C -d -v
    sending on inet and/or inet6 socket
    off & running….
    cfline(".                                                            %/var/log/routing.log", f, "radvd,routed,olsrd,zebra,ospfd,bgpd,miniupnpd", "")
    .*                                                            %/var/log/ntpd.log", f, "ntp,ntpd,ntpdate", "")
    .*                                                            %/var/log/ppp.log", f, "ppp", "")
    .*                                                            %/var/log/pptps.log", f, "pptps", "")
    .*                                                            %/var/log/poes.log", f, "poes", "")
    .*                                                            %/var/log/l2tps.log", f, "l2tps", "")
    .*                                                            %/var/log/ipsec.log", f, "racoon", "*")
    Segmentation fault

  • This keeps getting better, now the system logs are in binary?

    less system.log

    "system.log" may be a binary file.  See it anyway?

  • Well oddly enough I solved it by

    rm /var/log/*.log then restarting the fw

Log in to reply