Samba process hanging with 100% CPU load

[Noel Kelly]

I had this problem as well.  Very nasty as the smbds are unkillable ?

The best I can suggest is to try the 2.2.4pre version (or wait for the
official release) as it seems by the far the most stable since 2.2.2 was
released.  I have not had one of these unkillables for a while now.

Also I suspect a 2.4 kernel might be more adept at keeping these rogue
processes under control.

Noel

-----Original Message-----
From: Dr. Hansjoerg Maurer [mailto:hansjoerg.maurer at itsd.de]
Sent: 27 April 2002 09:57
To: samba-technical at samba.org
Subject: Samba process hanging with 100% CPU load


Hi,

I am running Samba 2.2.2 and from time to time smbd processes hang and
take 100% of CPU time (Redhat 6.2, Win2K Clients).


PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME COMMAND

16895 root      17   0   968   64    36 R       0 99.9  0.0 12768m smbd

smbstatus shows:
Samba version 2.2.2
Service      uid      gid      pid     machine
----------------------------------------------
E-Projekt    projekt  schinharl  1288   zeichner14 (192.168.1.14) Sat
Apr 27 09:13:05 2002
Projekt      projekt  schinharl  1443   zeichner7 (192.168.1.7) Sat Apr
27 10:00:05 2002
IPC$         ftp      ftp      16895   zeichner2 (192.168.1.2) Thu Apr
18 12:47:31 2002
A-Projekt    projekt  schinharl  1443   zeichner7 (192.168.1.7) Sat Apr
27 10:00:05 2002
rohr         rohr     schinharl  1443   zeichner7 (192.168.1.7) Sat Apr
27 09:59:38 2002
A-Projekt    projekt  schinharl  1443   zeichner7 (192.168.1.7) Sat Apr
27 10:35:24 2002
Projekt      projekt  schinharl  1288   zeichner14 (192.168.1.14) Sat
Apr 27 09:13:05 2002
lingott      lingott  schinharl  1288   zeichner14 (192.168.1.14) Sat
Apr 27 09:12:50 2002
A-Projekt    projekt  schinharl  1288   zeichner14 (192.168.1.14) Sat
Apr 27 09:13:05 2002
E-Projekt    projekt  schinharl  1443   zeichner7 (192.168.1.7) Sat Apr
27 10:00:05 2002
IPC$         rohr     schinharl  1443   zeichner7 (192.168.1.7) Sat Apr
27 10:05:31 2002
IPC$         ftp      ftp       1570   zeichner17 (192.168.1.17) Sat Apr
27 10:45:18 2002
IPC$         gast     schinharl 16895   zeichner2 (192.168.1.2) Thu Apr
18 11:17:22 2002


This identifies machine zeichner2 as the machine with the hanging
prozess.
[root at server fd]# tail -10 /var/log/samba/log.zeichner2
[2002/04/26 18:56:01, 0] rpc_server/srv_pipe.c:api_rpcTNP(1204)
  api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.
[2002/04/27 10:09:58, 0] rpc_server/srv_netlog.c:api_net_sam_logon(208)
  api_net_sam_logon: Failed to marshall NET_R_SAM_LOGON.
[2002/04/27 10:09:58, 0] rpc_server/srv_pipe.c:api_rpcTNP(1204)
  api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.
[2002/04/27 10:49:18, 0] rpc_server/srv_netlog.c:api_net_sam_logon(208)
  api_net_sam_logon: Failed to marshall NET_R_SAM_LOGON.
[2002/04/27 10:49:18, 0] rpc_server/srv_pipe.c:api_rpcTNP(1204)
  api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.

But I am not sure, if this has something to do with the hanging prozess.

[root at server fd]# ll /proc/16895/fd/
insgesamt 0
lrwx------    1 root     root           64 Apr 27 10:50 0 -> /dev/null
lrwx------    1 root     root           64 Apr 27 10:50 1 -> /dev/null
lrwx------    1 root     root           64 Apr 27 10:50 10 ->
/usr/local/samba/var/locks/connections.tdb
lrwx------    1 root     root           64 Apr 27 10:50 11 ->
/usr/local/samba/var/locks/brlock.tdb
lr-x------    1 root     root           64 Apr 27 10:50 12 ->
pipe:[1986057]
l-wx------    1 root     root           64 Apr 27 10:50 13 ->
pipe:[1986057]
lrwx------    1 root     root           64 Apr 27 10:50 14 ->
socket:[2464780]
lrwx------    1 root     root           64 Apr 27 10:50 15 ->
/usr/local/samba/var/locks/locking.tdb
lrwx------    1 root     root           64 Apr 27 10:50 16 ->
/usr/local/samba/var/locks/printing.tdb
lrwx------    1 root     root           64 Apr 27 10:50 17 ->
/usr/local/samba/var/locks/ntdrivers.tdb
lrwx------    1 root     root           64 Apr 27 10:50 18 ->
/usr/local/samba/var/locks/ntprinters.tdb
lrwx------    1 root     root           64 Apr 27 10:50 19 ->
/usr/local/samba/var/locks/ntforms.tdb
lrwx------    1 root     root           64 Apr 27 10:50 2 -> /dev/null
lrwx------    1 root     root           64 Apr 27 10:50 20 ->
/usr/local/samba/var/locks/share_info.tdb
l-wx------    1 root     root           64 Apr 27 10:50 21 -> /dev/null
lrwx------    1 root     root           64 Apr 27 10:50 22 ->
socket:[2464790]
lr-x------    1 root     root           64 Apr 27 10:50 23 ->
pipe:[2464782]
l-wx------    1 root     root           64 Apr 27 10:50 24 ->
pipe:[2464782]
l-wx------    1 root     root           64 Apr 27 10:50 26 ->
/var/log/samba/log.zeichner2
lr-x------    1 root     root           64 Apr 27 10:50 3 ->
/dev/urandom
lrwx------    1 root     root           64 Apr 27 10:50 4 ->
/usr/local/samba/private/secrets.tdb
lrwx------    1 root     root           64 Apr 27 10:50 5 ->
socket:[2464781]
l-wx------    1 root     root           64 Apr 27 10:50 6 ->
/usr/local/samba/var/locks/smbd.pid
lr-x------    1 root     root           64 Apr 27 10:50 7 ->
pipe:[1986045]
l-wx------    1 root     root           64 Apr 27 10:50 8 ->
pipe:[1986045]
lrwx------    1 root     root           64 Apr 27 10:50 9 ->
/usr/local/samba/var/locks/messages.tdb

What can be the reason for this behavior.
I have set the options
deadtime=180
keepalive = 3600

Thanks a lot

hansjörg