SMBD flooding syslog

QSx · 11. Januar 2017

Since i've installed omv 3, syslog is getting filled with stuff like this:

Code

Jan 11 20:00:02 nas smbd[1359]: [2017/01/11 20:00:02.559621,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:00:02 nas smbd[1359]:   Could not find child 6092 -- ignoring
Jan 11 20:01:02 nas smbd[1359]: [2017/01/11 20:01:02.621665,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:01:02 nas smbd[1359]:   Could not find child 6173 -- ignoring
Jan 11 20:02:02 nas smbd[1359]: [2017/01/11 20:02:02.683707,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:02:02 nas smbd[1359]:   Could not find child 6196 -- ignoring
Jan 11 20:03:02 nas smbd[1359]: [2017/01/11 20:03:02.084900,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:03:02 nas smbd[1359]:   Could not find child 6224 -- ignoring
Jan 11 20:03:02 nas smbd[1359]: [2017/01/11 20:03:02.686376,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:03:02 nas smbd[1359]:   Could not find child 6225 -- ignoring
Jan 11 20:04:02 nas smbd[1359]: [2017/01/11 20:04:02.709164,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:04:02 nas smbd[1359]:   Could not find child 6248 -- ignoring
Jan 11 20:05:02 nas smbd[1359]: [2017/01/11 20:05:02.730358,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:05:02 nas smbd[1359]:   Could not find child 6271 -- ignoring
Jan 11 20:06:02 nas smbd[1359]: [2017/01/11 20:06:02.780870,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:06:02 nas smbd[1359]:   Could not find child 6350 -- ignoring
Jan 11 20:07:02 nas smbd[1359]: [2017/01/11 20:07:02.800635,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:07:02 nas smbd[1359]:   Could not find child 6447 -- ignoring
Jan 11 20:08:02 nas smbd[1359]: [2017/01/11 20:08:02.862710,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:08:02 nas smbd[1359]:   Could not find child 6468 -- ignoring
Jan 11 20:09:02 nas smbd[1359]: [2017/01/11 20:09:02.910446,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:09:02 nas smbd[1359]:   Could not find child 6532 -- ignoring
Jan 11 20:10:02 nas smbd[1359]: [2017/01/11 20:10:02.972534,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:10:02 nas smbd[1359]:   Could not find child 6567 -- ignoring
Jan 11 20:11:03 nas smbd[1359]: [2017/01/11 20:11:03.005280,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:11:03 nas smbd[1359]:   Could not find child 6590 -- ignoring
Jan 11 20:12:03 nas smbd[1359]: [2017/01/11 20:12:03.066438,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:12:03 nas smbd[1359]:   Could not find child 6612 -- ignoring
Jan 11 20:13:03 nas smbd[1359]: [2017/01/11 20:13:03.114413,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:13:03 nas smbd[1359]:   Could not find child 6633 -- ignoring
Jan 11 20:14:03 nas smbd[1359]: [2017/01/11 20:14:03.176464,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:14:03 nas smbd[1359]:   Could not find child 6655 -- ignoring
Jan 11 20:15:03 nas smbd[1359]: [2017/01/11 20:15:03.235504,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:15:03 nas smbd[1359]:   Could not find child 6801 -- ignoring
Jan 11 20:16:03 nas smbd[1359]: [2017/01/11 20:16:03.297543,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:16:03 nas smbd[1359]:   Could not find child 6838 -- ignoring
Jan 11 20:17:03 nas smbd[1359]: [2017/01/11 20:17:03.304861,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:17:03 nas smbd[1359]:   Could not find child 6862 -- ignoring
Jan 11 20:18:02 nas smbd[1359]: [2017/01/11 20:18:02.145522,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:18:02 nas smbd[1359]:   Could not find child 7196 -- ignoring
Jan 11 20:18:03 nas smbd[1359]: [2017/01/11 20:18:03.307547,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:18:03 nas smbd[1359]:   Could not find child 7197 -- ignoring
Jan 11 20:19:03 nas smbd[1359]: [2017/01/11 20:19:03.369653,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:19:03 nas smbd[1359]:   Could not find child 7597 -- ignoring
Jan 11 20:20:03 nas smbd[1359]: [2017/01/11 20:20:03.429615,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:20:03 nas smbd[1359]:   Could not find child 8038 -- ignoring
Jan 11 20:21:03 nas smbd[1359]: [2017/01/11 20:21:03.449980,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:21:03 nas smbd[1359]:   Could not find child 8140 -- ignoring
Jan 11 20:22:03 nas smbd[1359]: [2017/01/11 20:22:03.511835,  2] ../source3/smbd/server.c:443(remove_child_pid)
Jan 11 20:22:03 nas smbd[1359]:   Could not find child 8164 -- ignoring

Alles anzeigen

Two lines per minute - it's nothing horrible but makes looking for other stuff more difficult...

Is this normal behavior or ?

Edit:

I've found this https://bugzilla.samba.org/show_bug.cgi?id=8269

It appears to be very old bug? But it's supposed to be fixed since 2011something...

Anyone?

QSx · 15. Januar 2017

Anybody?

ryecoaaron · 15. Januar 2017

Not sure what is causing it. I haven't seen that before and I couldn't find anything that would fix it.

Burkart · 7. Januar 2018

I saw the same behavior in OMV 3.0.95.

Solution: In the Web GUI under Services -> SMB/CIFS -> Settings -> Advanced settings, set Log level to "Normal" (previously it was "Full").

Going by Andreas Schneider's comments at https://bugzilla.redhat.com/show_bug.cgi?id=1417440, the message is only shown for higher log levels and so can only be muted by setting a lower log level. He also mentions that the workaround of setting "printcap cache time = 0" doesn't work for Samba 4.4 since the printcap cache time is fixed to 60 seconds. I can confirm that for Samba 4.2 used in OMV: Adding "printcap cache time = 0" to Advanced settings -> Extra options doesn't remove the syslog spam.

OnlyHardOfficial · 31. März 2021

Zitat von Burkart

I saw the same behavior in OMV 3.0.95.

Solution: In the Web GUI under Services -> SMB/CIFS -> Settings -> Advanced settings, set Log level to "Normal" (previously it was "Full").

Going by Andreas Schneider's comments at https://bugzilla.redhat.com/show_bug.cgi?id=1417440, the message is only shown for higher log levels and so can only be muted by setting a lower log level. He also mentions that the workaround of setting "printcap cache time = 0" doesn't work for Samba 4.4 since the printcap cache time is fixed to 60 seconds. I can confirm that for Samba 4.2 used in OMV: Adding "printcap cache time = 0" to Advanced settings -> Extra options doesn't remove the syslog spam.

Thanks mate! Exatly, its true!!

SMBD flooding syslog

Jetzt mitmachen!

Tags