syslog_ng is not running

[diskdiddler]

This one looks worrying.
Got this email tonight.

New alerts:
* syslog_ng is not running.


Current alerts:
* syslog_ng is not running.

I'm in the middle of a resilver for 2 of 6 disks (upgrading size)

A VM fell over on me.
(Console in the web UI):

Jul 13 17:41:01 truenas kernel: vnet0: promiscuous mode disabled
Jul 13 17:49:03 truenas kernel: vnet0: link state changed to DOWN

Jul 13 18:25:04 truenas syslog-ng[14254]: syslog-ng starting up; version='3.35.1'
Jul 13 18:25:04 truenas kernel: pid 1501 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped

dmesg:

vnet0: link state changed to DOWN
vnet0: promiscuous mode disabled
tap0: Ethernet address: 58:9c:fc:10:ff:b5
tap0: changing name to 'vnet0'
vnet0: promiscuous mode enabled
vnet0: link state changed to UP
Limiting closed port RST response from 1354 to 200 packets/sec
Limiting closed port RST response from 998 to 200 packets/sec
vnet0: promiscuous mode disabled
vnet0: link state changed to DOWN
pid 1501 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped)

Also this:

root@truenas[~]# syslog-ng
[2022-07-13T19:22:05.234728] Error binding socket; addr='AF_INET(127.0.0.1:1031)', error='Address already in use (48)'
[2022-07-13T19:22:05.234809] Error initializing message pipeline; plugin_name='udp', location='/usr/local/etc/syslog-ng.conf:13:7'

I'm not a hardcore guru, so I'm unsure how else to diagnose the issue. Reluctant to reboot based on that very last line though.
Never seen a core dump issue before in 7 years, so concerned.

 

[diskdiddler]

I've rebooted and she seems to be working ok but it's concerning, anyone else seen it?

 

[jsnas]

root@truenas[~]# syslog-ng
[2022-07-13T19:22:05.234728] Error binding socket; addr='AF_INET(127.0.0.1:1031)', error='Address already in use (48)'
[2022-07-13T19:22:05.234809] Error initializing message pipeline; plugin_name='udp', location='/usr/local/etc/syslog-ng.conf:13:7'

I hit the exact same message today (with same AF_INET=172.0.0.1:1031 and address=48). But I wasn't running anything at the time, and had just setup a brand new pool (no datasets yet). So not much that could go wrong. Has the issue ever repeated for you?

 

[Samuel Tai]

I get this occasionally when logs rotate. It's a cosmetic warning, no big deal.

 

[diskdiddler]

It does look like it hasn't become a major issue but after 8 years using it, it was concerning to see a new error.

System seems fine after all now though.