Syslog-NG "system messages" weirdness

[Ripshod]

Since midnight (logrotate) all logging has stopped with the following messages in "System Messages"

Sep  2 00:23:08 ripshod kernel: htb: htb qdisc 13: is non-work-conserving?
Sep  2 00:29:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 00:59:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 01:29:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 01:59:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 02:29:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 02:59:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 03:29:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 03:59:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 04:29:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 04:59:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 05:29:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 05:59:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 06:29:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
Sep  2 06:59:01 ripshod kernel: [tdts_shell_ioctl_stat:256] Recv ioctl req with op 2

The logs weren't going to my syslog server either. A quick restart of entware brought everything back to normal but any pointers would be gratefully received. I can't afford to have errors on my perfect system that never has errors.

 

[L&LD]

Pointer: Nothing is perfect.

Reboots are a fix (sometimes).

 

[elorimer]

Like a rug it is important to have an error, in order to let the evil spirits out.

Speaking of evil spirts, is this Trend Micro? https://www.snbforums.com/threads/r...fro-from-log-deleting-skynet-logs-also.69801/