[Samba] Sambaserver slows down, too many smbd processes
Holger Wesser
wesser at gmx.com
Thu Jun 30 15:11:31 GMT 2005
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sorry folks for asking again, but I don't know how to get the problem
solved.
My Samba server works fine, but after some days the server doesn't kill
old smbd processes, so a "ps aux" looks like that:
root 14032 0.0 0.0 6068 2056 ? Ss Jun25 0:06
/usr/sbin/nmbd -D
root 14034 0.0 0.1 10092 3280 ? Ss Jun25 0:00
/usr/sbin/smbd -D
root 14035 0.0 0.1 10092 3268 ? S Jun25 0:00
/usr/sbin/smbd -D
lp 15304 0.0 0.0 1804 676 ? Ss Jun26 0:00
/usr/sbin/lpd -s
root 16326 0.2 1.9 46056 39648 ? S Jun27 12:06
/usr/sbin/smbd -D
root 17754 0.0 0.2 10776 4672 ? S Jun29 0:01
/usr/sbin/smbd -D
root 18711 0.0 0.1 10412 3748 ? S 08:49 0:00
/usr/sbin/smbd -D
root 18740 0.0 0.2 10784 4556 ? S 09:20 0:14
/usr/sbin/smbd -D
root 18752 0.0 0.2 10664 4552 ? S 09:41 0:03
/usr/sbin/smbd -D
root 18758 0.0 0.2 10740 4456 ? S 09:48 0:00
/usr/sbin/smbd -D
user01 18761 0.0 0.2 10784 4592 ? S 09:50 0:02
/usr/sbin/smbd -D
root 18767 0.0 0.2 10596 4492 ? S 09:54 0:00
/usr/sbin/smbd -D
root 18798 0.0 0.1 10392 3552 ? S 10:52 0:00
/usr/sbin/smbd -D
root 18801 0.0 0.1 10392 3548 ? S 10:53 0:00
/usr/sbin/smbd -D
root 18802 0.0 0.1 10392 3548 ? S 10:54 0:00
/usr/sbin/smbd -D
root 18803 0.0 0.1 10392 3556 ? S 10:55 0:00
/usr/sbin/smbd -D
root 18815 0.0 0.1 10392 3552 ? S 10:58 0:00
/usr/sbin/smbd -D
root 18818 0.0 0.1 10392 3552 ? S 10:59 0:00
/usr/sbin/smbd -D
root 18827 0.0 0.2 10772 4624 ? S 11:03 0:02
/usr/sbin/smbd -D
root 18829 0.0 0.1 10392 3636 ? S 11:06 0:00
/usr/sbin/smbd -D
root 18842 0.0 0.2 10780 4436 ? S 11:23 0:00
/usr/sbin/smbd -D
root 18844 0.0 0.1 10524 3772 ? S 11:23 0:00
/usr/sbin/smbd -D
root 18851 0.0 0.1 10524 3764 ? S 11:44 0:00
/usr/sbin/smbd -D
root 18852 0.0 0.2 10816 4644 ? S 11:44 0:01
/usr/sbin/smbd -D
root 18854 0.0 0.1 10524 3756 ? S 11:48 0:00
/usr/sbin/smbd -D
root 18857 0.0 0.1 10524 3752 ? S 11:50 0:00
/usr/sbin/smbd -D
root 18860 0.0 0.1 10524 3768 ? S 11:53 0:00
/usr/sbin/smbd -D
root 18896 0.0 0.1 10532 3764 ? S 12:47 0:00
/usr/sbin/smbd -D
root 18897 0.0 0.2 10652 4212 ? S 12:47 0:00
/usr/sbin/smbd -D
root 18898 0.0 0.1 10532 3756 ? S 12:48 0:00
/usr/sbin/smbd -D
root 18900 0.0 0.1 10532 3760 ? S 12:50 0:00
/usr/sbin/smbd -D
root 18909 0.0 0.1 10540 3760 ? S 13:00 0:00
/usr/sbin/smbd -D
root 18923 0.0 0.1 10540 3760 ? S 13:23 0:00
/usr/sbin/smbd -D
root 18924 0.0 0.1 10540 3760 ? S 13:25 0:00
/usr/sbin/smbd -D
root 18932 0.0 0.1 10540 3760 ? S 13:41 0:00
/usr/sbin/smbd -D
root 18933 0.0 0.1 10540 3760 ? S 13:43 0:00
/usr/sbin/smbd -D
root 18935 0.0 0.1 10540 3760 ? S 13:45 0:00
/usr/sbin/smbd -D
root 18937 0.0 0.1 10548 3760 ? S 13:47 0:00
/usr/sbin/smbd -D
root 18938 0.0 0.1 10548 3756 ? S 13:49 0:00
/usr/sbin/smbd -D
root 18940 0.0 0.1 10548 3760 ? S 13:51 0:00
/usr/sbin/smbd -D
root 18967 0.0 0.1 10548 3760 ? S 14:35 0:00
/usr/sbin/smbd -D
root 18970 0.0 0.1 10548 3760 ? S 14:39 0:00
/usr/sbin/smbd -D
root 18971 0.0 0.1 10548 3756 ? S 14:41 0:00
/usr/sbin/smbd -D
root 18975 0.0 0.1 10556 3760 ? S 14:45 0:00
/usr/sbin/smbd -D
root 18977 0.0 0.1 10556 3764 ? S 14:50 0:00
/usr/sbin/smbd -D
root 18983 0.0 0.1 10556 3756 ? S 14:55 0:00
/usr/sbin/smbd -D
root 18985 0.0 0.1 10556 3756 ? S 14:57 0:00
/usr/sbin/smbd -D
root 18986 0.0 0.1 10564 3764 ? S 14:59 0:00
/usr/sbin/smbd -D
root 18992 0.0 0.1 10564 3764 ? S 15:02 0:00
/usr/sbin/smbd -D
root 18999 0.0 0.1 10548 3784 ? S 15:13 0:00
/usr/sbin/smbd -D
root 19009 0.0 0.2 10760 4356 ? S 15:28 0:00
/usr/sbin/smbd -D
root 19016 0.0 0.1 10440 3556 ? S 15:40 0:00
/usr/sbin/smbd -D
root 19017 0.0 0.1 10440 3556 ? S 15:41 0:00
/usr/sbin/smbd -D
root 19018 0.0 0.1 10440 3556 ? S 15:42 0:00
/usr/sbin/smbd -D
1122 19021 0.0 0.2 10696 4372 ? S 15:43 0:00
/usr/sbin/smbd -D
root 19022 0.0 0.1 10572 3772 ? S 15:46 0:00
/usr/sbin/smbd -D
root 19024 0.0 0.1 10816 3936 ? S 15:47 0:00
/usr/sbin/smbd -D
root 19034 0.0 0.1 10456 3552 ? S 15:57 0:00
/usr/sbin/smbd -D
root 19037 0.0 0.1 10456 3556 ? S 15:58 0:00
/usr/sbin/smbd -D
root 19044 0.0 0.1 10584 3872 ? S 16:00 0:00
/usr/sbin/smbd -D
root 19046 0.0 0.1 10456 3552 ? S 16:01 0:00
/usr/sbin/smbd -D
root 19047 0.0 0.1 10456 3772 ? S 16:03 0:00
/usr/sbin/smbd -D
root 19050 0.0 0.1 10456 3556 ? S 16:04 0:00
/usr/sbin/smbd -D
root 19051 0.0 0.1 10456 3564 ? S 16:05 0:00
/usr/sbin/smbd -D
root 19052 0.0 0.1 10456 3556 ? S 16:06 0:00
/usr/sbin/smbd -D
root 19054 0.0 0.1 10456 3560 ? S 16:07 0:00
/usr/sbin/smbd -D
root 19056 0.0 0.1 10456 3640 ? S 16:08 0:00
/usr/sbin/smbd -D
root 19059 0.0 0.1 10584 3852 ? S 16:13 0:00
/usr/sbin/smbd -D
root 19061 0.0 0.1 10456 3560 ? S 16:15 0:00
/usr/sbin/smbd -D
root 19062 0.0 0.1 10456 3768 ? S 16:16 0:00
/usr/sbin/smbd -D
root 19067 0.0 0.1 10456 3556 ? S 16:17 0:00
/usr/sbin/smbd -D
root 19068 0.0 0.1 10456 3552 ? S 16:18 0:00
/usr/sbin/smbd -D
root 19076 0.0 0.0 14604 1964 ? Ss 16:34 0:00 sshd:
root at pts/0
root 19079 0.0 0.0 2980 1576 pts/0 Ss 16:34 0:00 -bash
root 19197 0.0 0.0 2692 792 pts/0 R+ 16:53 0:00 ps aux
There are 59 "smbd". New user are not able to access the server. Only
"killall -9 smbd" helps in this case.
Any idea what's going wrong or where to check up?
Holger
Holger Wesser wrote:
> Hi folks,
>
> maybe my problem was discussed before, but I'm just too busy to browse
> the whole mailinglist at the moment.
>
> I'm running Samba 3.0.14a(sernet) on a Debian Sarge with LDAP-Backend.
> After some days, the users aren't able to load their profiles from the
> server. In fact, no datas can be transfered from/to the sambaserver.
>
> The cpu load is nearly 50 percent (it's a Pentium 3,0GHz, 2GB RAM with
> only 10 users). A "ps aux" shows about 30 smbd-processes. When I try to
> stop samba via "/etc/init.d/samba stop", this doesn't affect the
> processes. Only "killall -9 smbd" helps. After restarting smbd/nmbd
> everything works fine again.
>
> Following entries attract my attention:
>
> /var/log/syslog:
>
> Jun 16 09:14:59 bgst-ng smbd[28823]: [2005/06/16 09:14:59, 0]
> lib/util_sock.c:write_socket_data(430)
> Jun 16 09:14:59 bgst-ng smbd[28823]: write_socket_data: write failure.
> Error = Connection reset by peer
> Jun 16 09:14:59 bgst-ng smbd[28823]: [2005/06/16 09:14:59, 0]
> lib/util_sock.c:write_socket(455)
> Jun 16 09:14:59 bgst-ng smbd[28823]: write_socket: Error writing 4
> bytes to socket 5: ERRNO = Connection reset by peer
> Jun 16 09:14:59 bgst-ng smbd[28823]: [2005/06/16 09:14:59, 0]
> lib/util_sock.c:send_smb(647)
> Jun 16 09:14:59 bgst-ng smbd[28823]: Error writing 4 bytes to client.
> -1. (Connection reset by peer)
>
> /var/log/log.justamachine:
>
> [2005/06/16 12:31:43, 0] lib/util_sock.c:write_socket_data(430)
> write_socket_data: write failure. Error = Connection reset by peer
> [2005/06/16 12:31:43, 0] lib/util_sock.c:write_socket(455)
> write_socket: Error writing 4 bytes to socket 25: ERRNO = Connection
> reset by peer
> [2005/06/16 12:31:43, 0] lib/util_sock.c:send_smb(647)
> Error writing 4 bytes to client. -1. (Connection reset by peer)
>
> Maybe that's normal, maybe not.
>
> And maybe anyone out there had similar problems before and can help me.
>
> Thanks
> Holger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCxAujO0QDuZMdP0sRAlHfAJ92c+Lvrcdh3M9ELr+V+WKHkH1nwwCeIgw4
jt1q0UaU7YOza+jFIBeZ6BE=
=hsOS
-----END PGP SIGNATURE-----
More information about the samba
mailing list