Syslog service in pfSense v2.8.1 often stop itself
-
i am facing the same issue.
Any fix expept from watchdog and rules? -
@AlexanderK At least with Watchdog you'll get informed when it happens. That will give you something to work with to try tracking it down in the logs. That said, mine stopped again a few days ago, coincidentally at 00:15 again (marked XXXX). Perhaps it is some timing issue in syslogd that works only 95% of the time? There re plenty of instances of syslogd exiting and successfully restarting a second later, but sometimes it doesn't without a kick in the pants. In any case, I'll stick with watchdog for the present, won't hurt. Just adding to the conversation, not a big issue for me.
XXXX Oct 14 00:15:02 syslogd kernel boot file is /boot/kernel/kernel Oct 8 02:45:53 syslogd sendto: Connection refused Oct 8 02:45:53 syslogd kernel boot file is /boot/kernel/kernel Oct 8 02:45:52 syslogd exiting on signal 15 Oct 8 02:45:22 syslogd sendto: Connection refused Oct 8 02:45:22 syslogd kernel boot file is /boot/kernel/kernel Oct 8 02:44:27 syslogd exiting on signal 15 Oct 8 02:44:21 syslogd sendto: Connection refused XXXX Oct 3 00:15:02 syslogd kernel boot file is /boot/kernel/kernel Sep 30 17:09:30 syslogd sendto: Connection refused -
If it's actually external you can add the work-around stateless floating rules to prevent the connection refused message.
-
@stephenw10 If directed at me, it's not external. It's a second HDD internal to the FW, mounted as a directory on the system SSD. Not complaining.
-
No sorry that was at the previous poster. The workaround rule won't work for traffic to syslog-ng locally.

-
Stopped again this AM at 00:15, random interval. Maybe something to do with daily log rotation, GZipping the log, dunno. Just info, not an issue for me anyway.
6 Matched General Log Entries. (Maximum 500) Oct 23 00:15:02 php-cgi 95349 notify_monitor.php: Message sent to provels Oct 23 00:15:02 syslogd kernel boot file is /boot/kernel/kernel Oct 14 00:15:03 php-cgi 10330 notify_monitor.php: Message sent to provels Oct 14 00:15:02 syslogd kernel boot file is /boot/kernel/kernel Oct 3 00:15:03 php-cgi 55524 notify_monitor.php: Message sent to provels Oct 3 00:15:02 syslogd kernel boot file is /boot/kernel/kernelThe top of today's default.log.
Oct 23 00:00:00 fw syslog-ng[13248]: Configuration reload request received, reloading configuration; Oct 23 00:00:00 fw syslog-ng[13248]: Configuration reload finished; Oct 23 00:10:00 fw syslog-ng[13248]: Log statistics; processed='destination(_DEFAULT)=183', dropped='global(internal_source)=0', processed='global(internal_source)=183', queued='global(internal_source)=0', processed='global(msg_clones)=0', processed='source(_DEFAULT)=183', processed='src.internal(_DEFAULT#0)=183', processed='global(sdata_updates)=0', stamp='src.internal(_DEFAULT#0)=1761195600', queued='global(scratch_buffers_count)=0', processed='global(payload_reallocs)=178', processed='center(queued)=183', processed='center(received)=183', queued='global(scratch_buffers_bytes)=0' Oct 23 00:15:02 localhost syslogd: restart Oct 23 00:15:02 localhost syslogd: kernel boot file is /boot/kernel/kernel Oct 23 00:15:02 localhost php-cgi[95349]: notify_monitor.php: Message sent to provels -
Hi
We use Graylog as remote syslog. If server with Graylog has outage, e.g. is restarted due to updates, syslogd is stopped in pfSense 2.8.1. We did not have this issue in v2.8.0.
Aldomoro
-
Yes, that's the bug discussed here. The workaround rules will prevent it. https://redmine.pfsense.org/issues/16362#note-5
-
@aldomoro Possibly the best use of Service Watchdog. Maybe the only one! :)
-
Hi,
Same problem here:
"Nov 2 22:00:02 pfsense syslogd: sendto: Connection refused" (system.log)
PfSense CE 2.8.1, remote logging enabled.
Anothers instances 2.8 running OK.
Workaround: whatchdog
Thanks.
Geovane