What are these samba errors about?

opensuse v11.3 linux 2.6.34.7-0.7-desktop x86_64

These message have started appearing the system logs </var/log/messages and /var/log/warn> since Mar 2, 2011. They seem to occur about every 13 minutes (780 seconds). What could it mean? Is it serious?

Mar  9 20:15:50 sma-station14l smbd[3711]: [2011/03/09 20:15:50.196387,  0] smbd/server.c:281(remove_child_pid)
Mar  9 20:15:50 sma-station14l smbd[3711]:   Could not find child 10046 -- ignoring
Mar  9 20:28:50 sma-station14l smbd[3711]: [2011/03/09 20:28:50.885876,  0] smbd/server.c:281(remove_child_pid)
Mar  9 20:28:50 sma-station14l smbd[3711]:   Could not find child 10326 -- ignoring

i have seen those warnings also, but only because i updated to samba 3.5.8 which is available in the opensuse network:/ repo. There was a fix for the FD_SET vunerability which is described here:

Samba - Security Announcement Archive

i have not discovered the reason/fix for these warnings, but samba is functioning normally as it appears to the end user.

this may not describe your situation unless you have updated from that repo also, or perhaps from the Tumbleweed repo, as far as i know the regular update repos have not been updated with this fix yet.

perhaps one of the network gurus about will venture a suggestion.

On Thu March 10 2011 01:36 am, j xavier wrote:

>
> i have seen those warnings also, but only because i updated to samba
> 3.5.8 which is available in the opensuse network:/ repo. There was a fix
> for the FD_SET vunerability which is described here:
>
> ‘Samba - Security Announcement Archive’
> (http://samba.org/samba/security/CVE-2011-0719.html)
>
> i have not discovered the reason/fix for these warnings, but samba is
> functioning normally as it appears to the end user.
>
> this may not describe your situation unless you have updated from that
> repo also, or perhaps from the Tumbleweed repo, as far as i know the
> regular update repos have not been updated with this fix yet.
>
> perhaps one of the network gurus about will venture a suggestion.
>
Jimoe666 & j xavier;

We were experiencing these errors on a Opensuse 11.2 member server with Samba
3.5.6 from the Opensuse 11.2 repos. The errors have stopped since upgrading
to 3.5.8 from the same repos.

We also have an Opensuse 10.2 PDC with binaries from Sernet
(ftp://ftp.sernet.de/) This machine has never had this problem with either
Samba 3.5.6 or 3.5.8.

Note, however, Sernet packages the Samba files differently than OpenSuse so
that you must remove the OpenSuse package before installing the Sernet
binaries. As long as your version of OpenSuse is supported I would suggest
you continue using the OpenSuse binaries.


P. V.
“We’re all in this together, I’m pulling for you.” Red Green

thanks for your comments, venzkep

i’m also working with a 11.2 machine that “was” using the current updated version from the regular update repo which i believe is 3.5.3, then updated to packages in the network:/samba repo to address the recent vulnerabilities mentioned.

the upgrade to 3.5.8 started these msgs, which i took at first blush as a periodic scan/cleanup of the current samba threads generating non-crucial events for troubleshooting evaluation. I haven’t had the time to dig into further, but it looks like i should if you are not getting the same.

thanks again :slight_smile:

On Fri March 11 2011 10:36 pm, j xavier wrote:

>
> thanks for your comments, venzkep
>
> i’m also working with a 11.2 machine that “was” using the current
> updated version from the regular update repo which i believe is 3.5.3,
> then updated to packages in the network:/samba repo to address the
> recent vulnerabilities mentioned.
>
> the upgrade to 3.5.8 started these msgs, which i took at first blush as
> a periodic scan/cleanup of the current samba threads generating
> non-crucial events for troubleshooting evaluation. I haven’t had the
> time to dig into further, but it looks like i should if you are not
> getting the same.
>
> thanks again :slight_smile:
>
>
j xavier;

We also updated the cifs-mount package to version 3.5.8. I can not see why
that would make a difference, but if you have not updated this package it is
worth a shot.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

the cif-mount package was updated to 3.5.8 at the same time also, but a wise thing to check.

i’ll post back to this thread when i track down the culprit.

thanks :slight_smile:

These harmless messages are emitted by the parent smbd SIGCHLD handler
on printcap cache update, see:
https://bugzilla.novell.com/show_bug.cgi?id=666460

A fix is now upstream that increases the level at which these messages
are logged.

Cheers, David

thanks for the update, dmdiss… i switched packages to the “maintained” repo and resolved it.

i would advise strongly that this update be pushed thru the regular update repo for everyone.