samba - Sep 2012 - Samba4 spawns many /usr/sbin/smbd --configfile

I have no idea why, occasionally one of my samba4 servers won't respond to
my RSAT tools on windows 7.  I check the server and when I do a   ps -aux  I see
many lines
just like the following:


root     28073  0.0  0.0   2132    52 ?        S    00:11   0:00 /bin/sleep
999999999
3000063  28176  0.0  0.4  87604  7144 ?        S    00:22   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     28217  0.0  0.4  86448  7044 ?        S    00:23   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     28220  0.0  0.0   2216    56 ?        S    00:24   0:00 sh -c
/bin/sleep 999999999
root     28221  0.0  0.0   2132    52 ?        S    00:24   0:00 /bin/sleep
999999999
3000049  28316  0.0  0.4  87604  7208 ?        S    00:33   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     28319  0.0  0.4  86448  7064 ?        S    00:34   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     28323  0.0  0.0   2216    56 ?        S    00:35   0:00 sh -c
/bin/sleep 999999999
3000090  29225  0.0  0.4  87604  6984 ?        S    02:01   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     29229  0.0  0.4  86448  6716 ?        S    02:02   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     29233  0.0  0.0   2216    52 ?        S    02:03   0:00 sh -c
/bin/sleep 999999999
root     29234  0.0  0.0   2132    56 ?        S    02:03   0:00 /bin/sleep
999999999
mysql    29449  0.0  2.3 319516 36740 ?        Ssl  02:20   0:06
/usr/sbin/mysqld
3000107  29980  0.0  0.4  87604  7096 ?        S    02:52   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     29985  0.0  0.4  86448  7024 ?        S    02:53   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     29988  0.0  0.0   2216    56 ?        S    02:54   0:00 sh -c
/bin/sleep 999999999
root     29989  0.0  0.0   2132    48 ?        S    02:54   0:00 /bin/sleep
999999999
3000064  30292  0.0  0.4  87604  7088 ?        S    03:21   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
3000110  30297  0.0  0.4  87540  7004 ?        S    03:22   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     30299  0.0  0.4  86448  7016 ?        S    03:23   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground
root     30303  0.0  0.4  86448  7040 ?        S    03:23   0:00 /usr/sbin/smbd
--configfile /var/lib/samba/private/smbd.tmp/fileserver.conf --foreground


I usually just reboot that server and it's all good again.

I'm using samba4 beta6 I believe on this machine.

Hi

On 26 September 2012 17:18, Caleb O'Connell
<caleb at privacyassociation.org> wrote:
> I have no idea why, occasionally one of my samba4 servers won't respond
to my RSAT tools on windows 7.  I check the server and when I do a   ps -aux  I
see many lines
> just like the following:
>
>
> root     28073  0.0  0.0   2132    52 ?        S    00:11   0:00 /bin/sleep
999999999
[...]

This indicates that Samba has crashed and has called "sleep 999999999"
as the panic action.

This is to allow you to attach a debugger to the parent process and
get a stack trace (assuming you compiled with ./configure.developer).

You should be able to do something like this:

Use "ps axl" to get the parent process ID (PPID) of one of the sleep
processes.  (e.g. 12345)

Then:

# gdb /usr/local/samba/sbin/samba
(gdb) attach 12345
(gdb) bt full

That might tell the Samba developers what caused the crash.
> I usually just reboot that server and it's all good again.
>
> I'm using samba4 beta6 I believe on this machine.
Run /usr/local/samba/sbin/samba --version to get the exact version.

-- 
Michael Wood <esiotrot at gmail.com>