SG1000 syslogd fails to run after update.



  • Updated the firewall a few minutes ago to 2.4.0.b.20170504.0202, and noticed that syslogd is not running after the update.  I have tried to start it, and it fails, so logged in via shell to take a peek, and when attempting to start by hand (using sh -x to watch), I see:

    
    + _doit='limits -C daemon /usr/sbin/syslogd -s '
    + _run_rc_doit 'limits -C daemon /usr/sbin/syslogd -s '
    + debug 'run_rc_command: doit: limits -C daemon /usr/sbin/syslogd -s '
    + eval 'limits -C daemon /usr/sbin/syslogd -s '
    + limits -C daemon /usr/sbin/syslogd -s
    syslogd: child pid 45550 exited on signal 11
    + _return=1
    
    

    Any ideas?


  • Rebel Alliance Developer Netgate

    What packages do you have installed on there? If you have haproxy or tinc, you may be hitting this:

    https://redmine.pfsense.org/issues/7256



  • Neither of the packages, but agree it sounds like the same issue.

    I have the following pagkages installed:

    AutoConfigBackup 1.47
    LADVD 1.22
    mtr-nox11 0.85.6_1
    nmap 1.4.4_1
    RRD_Summary 1.3.2_2
    Status_Traffic_Totals 1.2_1

    Outside that, just a basic setup with one OpenVPN..


  • Rebel Alliance Developer Netgate

    If you update to today's snapshot, is it any different? Neither of my SG-1000s were running a snap from yesterday, but they were fine from earlier in the week and fine on today's snapshot as well.

    The signal 11 error is a bit worrisome, usually that means it crashed because of invalid data or possibly a hardware issue (usually memory).

    If upgrading does not help, the next thing I would try would be to reset all log data to eliminate the possibility that one of the log files is corrupted badly enough to crash syslogd. That can be done from Status > System Logs, Settings tab, click the "Reset Log Files" button, and then confirm the action.



  • Updating to the current release did not fix the issue, but I then did as you instructed and reset the logs, and after that syslogd was working again.  So guessing it was log corruption, but that makes me wonder why, as the unit had not been powered down or reset out of the blue, so guessing this corruption happened as part of an update..


Log in to reply