[Samba] Fwd: Samba 4.1.9 - Could not find child error
Volker Lendecke
Volker.Lendecke at SerNet.DE
Fri Jul 25 03:19:59 MDT 2014
On Thu, Jul 24, 2014 at 07:14:20AM -0700, Krishna Harathi wrote:
> Resending, this did not make it yesterday.
>
> Regards.
> Krishna Harathi
>
>
> ---------- Forwarded message ----------
> From: Krishna Harathi <kharathi at exablox.com>
> Date: Wed, Jul 23, 2014 at 2:00 PM
> Subject: Samba 4.1.9 - Could not find child error
> To: samba at lists.samba.org
>
>
> We are seeing this error in the logs every minute -
>
> [2014/07/23 16:40:59.829260, 2, pid=13355]
> ../source3/smbd/server.c:437(remove_child_pid)
>
> Could not find child 19021 -- ignoring
>
> I know there is an old bug/fix -
> https://bugzilla.samba.org/show_bug.cgi?id=8269
>
> smb.conf entries related to printer and printcap (disabled) -
>
> load printers = no
>
> printcap name = /dev/null
>
> printcap cache time = 0
>
> log level = 2
>
> We want the log level to be 2. I see that the code - in Samba 4.1.9
>
> if (child == NULL) {
>
> /* not all forked child processes are added to the children
> list */
>
> DEBUG(2, ("Could not find child %d -- ignoring\n",
> (int)pid));
>
> return;
>
> }
>
> Question - Given the log level we want, how can we prevent these errors in
> the log? Did I miss some parameter disabling printer/printcap completely?
> How do we stop forking these untracked processes?
Does "printing = bsd" help?
> Does Samba 4.1X continue to use source3 code base (as seen in the log
> entry)?
Yes, it does. Samba 4.1 and also 4.2 use the smbd file
server that has been around forever. It is in source3/.
We might rename the source directory at some point in the
future, but this is definitely not in our focus :-)
Volker
--
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de
More information about the samba
mailing list