Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Syslogd: exiting on signal 15

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 4 Posters 11.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ?
      Guest
      last edited by

      Hi again!

      On a pfSense 2.1.5 nano-console 4g I noticed yesterday that no events were logged any more for some time and I did a reboot. Right after finishing reboot, the log showed

      Nov 20 20:34:41 syslogd: exiting on signal 15

      Just after starting:

      Nov 20 20:34:40 php: rc.bootup: Creating rrd update script
      Nov 20 20:34:39 php: rc.start_packages: Restarting/Starting all packages.
      Nov 20 20:34:39 php: rc.newwanip: ROUTING: setting default route to xxx.yyy.zzz.aaa
      Nov 20 20:34:39 php: rc.start_packages: Restarting/Starting all packages.
      Nov 20 20:34:36 php: rc.newwanip: rc.newwanip: on (IP address: xxx.yyy.zzz.bbb) (interface: WAN[wan]) (real interface: re1).
      Nov 20 20:34:36 php: rc.newwanip: rc.newwanip: Informational is starting re1.
      Nov 20 20:34:32 check_reload_status: Starting packages
      Nov 20 20:34:32 php: rc.newwanip: pfSense package system has detected an ip change -> 10.0.9.2 … Restarting packages.
      Nov 20 20:34:32 check_reload_status: Reloading filter
      Nov 20 20:34:32 php: rc.newwanip: rc.newwanip: on (IP address: 10.xxx.aaa.bbb) (interface: []) (real interface: ovpnc2).
      Nov 20 20:34:32 php: rc.newwanip: rc.newwanip: Informational is starting ovpnc2.
      Nov 20 20:34:31 check_reload_status: Starting packages
      Nov 20 20:34:31 php: rc.newwanip: pfSense package system has detected an ip change -> 10.0.8.2 ... Restarting packages.
      Nov 20 20:34:31 check_reload_status: Reloading filter
      Nov 20 20:34:31 php: rc.newwanip: rc.newwanip: on (IP address: 10.bbb.ccc.ddd) (interface: []) (real interface: ovpnc1).
      Nov 20 20:34:31 php: rc.newwanip: rc.newwanip: Informational is starting ovpnc1.
      Nov 20 20:34:30 check_reload_status: rc.newwanip starting re1
      Nov 20 20:34:28 check_reload_status: rc.newwanip starting ovpnc2
      Nov 20 20:34:28 kernel: ovpnc2: link state changed to UP
      Nov 20 20:34:27 check_reload_status: rc.newwanip starting ovpnc1
      ...

      And the box stopped logging anything, while snort apparently is doing fine (but not getting logged in the syslog)...

      I had a look, found nothing meaningfull, except that others have reported such stuff for BSD in the past.

      Any idea how to reslove this?

      Many thanx in advance

      chemlud

      PS: After a reboot I find the same syslogd exit 15 message in the log, but the logging CONTINUES as normal afterwards?!?! What's that?

      1 Reply Last reply Reply Quote 0
      • N
        nikolaii
        last edited by

        Hello,

        I have the same behavior on a 2.2 pfsense. After a reboot, the last message in the logs is :

        syslogd: exiting on signal 15
        

        And then no more logging.

        Is there a way to restart the syslog daemon without rebooting the whole firewall?

        Thanks.
        Nicolas

        Nicolas

        1 Reply Last reply Reply Quote 0
        • N
          nikolaii
          last edited by

          After some more research, I found this issue:

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

          I applied the patch, and also cleared the logs. Now logging is running fine again.

          Nicolas

          Nicolas

          1 Reply Last reply Reply Quote 0
          • T
            tgoetten
            last edited by

            i have a similar issue. no matter what i configure to send to a remote host, only ipv6 information are send to the remote machine :-(

            even though i installed the patch mentioned here, it does not work! the wiered thing is, that i don't have configured any IPv6 usage at all!

            any ideas?

            Thomas

            1 Reply Last reply Reply Quote 0
            • F
              firestorm99
              last edited by

              just as a note:
              Had the same issue on an Alix APU running 2.2.2. full build: Tried to solve it with the patch, but it is not applicable anymore!?

              As a temporary solution I started syslogd via ssh.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.