My suspicion is syslog-ng is writing the messages slightly differently and skynet is choking on it when it does its hourly save.
This looks a little different up to the colon:
Than this:
EDIT: Nope, this isn't it. Syslog-ng is holding the files open, nothing to do with skynet.
This looks a little different up to the colon:
Code:
Oct 26 14:34:44 Skynet: [#] 130264 IPs (+0) -- 40232 Ranges Banned (+0) || 49 Inbound -- 0 Outbound Connections Blocked! [save] [8s]
Code:
Oct 28 18:05:00 RT-AC87R syslog-ng[1452]: Log statistics; processed='destination(d_logrotate)=138', processed='destination(d_syslogng)=82'
EDIT: Nope, this isn't it. Syslog-ng is holding the files open, nothing to do with skynet.
Last edited: