We are running a Red Hat Linux 6 system with samba 3.6.23 installed, and
configured as a stand alone
server. A couple of users are either spawning excessive numbers of smbd,
or failing to kill them
off. A couple of us have spent several days trying to determine the
reason, but as of now have
not found the reason.
The top of the smb.conf is:
#======================= Global Settings
====================================
[global]
# workgroup = METRO
# interfaces=135.205.209.150/255.255.255.0 lo eth0
127.0.0.1/255.255.255.0 192.168.12.2/24 192.168.13.2/24
# bind interfaces only = Yes
# --------------------------- Logging Options -----------------------------
log file = /var/log/samba/samba.log
max log size = 500
# ----------------------- Standalone Server Options
------------------------
security = USER
passdb backend = tdbsam
admin users = jwb rheyer
server signing = auto
#----------------------------- Name Resolution
-------------------------------
# Windows Internet Name Serving Support Section:
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
#
# - WINS Support: Tells the NMBD component of Samba to enable it's WINS
Server
#
# - WINS Server: Tells the NMBD components of Samba to be a WINS Client
#
# - WINS Proxy: Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
#
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups.
#dns proxy = yes
#============================ Share Definitions
=============================
[homes]
comment = Home Directories
path = /eros10/home1/%u
admin users writable = yes
read only = no
follow symlinks = No
[USERS]
comment = USERS Directories
path = */cds/users/*%u
admin users read only = No
follow symlinks = No
followed by similar other share definitions.
Does anyone have any ideas on why the daemon is either spawning or failing
to get killed?
Thanks in advance
Jim Ballantine
On Tue, Aug 30, 2016 at 07:16:56AM -0400, Jim Ballantine via samba wrote:> We are running a Red Hat Linux 6 system with samba 3.6.23 installed, and > configured as a stand alone > server. A couple of users are either spawning excessive numbers of smbd, > or failing to kill them > off.What do you exactly mean by "failing to kill them off"? Kill -9 on the smbd fails? If that's the case, it is an issue below Samba, kernel or disk subsystem. Volker
---------- Forwarded message ----------
From: Jim Ballantine <j.ballantine at gmail.com>
Date: Tue, Aug 30, 2016 at 7:16 AM
Subject: spawning smbd's
To: samba at lists.samba.org
We are running a Red Hat Linux 6 system with samba 3.6.23 installed, and
configured as a stand alone
server. A couple of users are either spawning excessive numbers of smbd,
or failing to kill them
off. A couple of us have spent several days trying to determine the
reason, but as of now have
not found the reason.
The top of the smb.conf is:
#======================= Global Settings ====================================
[global]
# workgroup = METRO
# interfaces=135.205.209.150/255.255.255.0 lo eth0
127.0.0.1/255.255.255.0 192.168.12.2/24 192.168.13.2/24
# bind interfaces only = Yes
# --------------------------- Logging Options -----------------------------
log file = /var/log/samba/samba.log
max log size = 500
# ----------------------- Standalone Server Options
------------------------
security = USER
passdb backend = tdbsam
admin users = jwb rheyer
server signing = auto
#----------------------------- Name Resolution
-------------------------------
# Windows Internet Name Serving Support Section:
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
#
# - WINS Support: Tells the NMBD component of Samba to enable it's WINS
Server
#
# - WINS Server: Tells the NMBD components of Samba to be a WINS Client
#
# - WINS Proxy: Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
#
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups.
#dns proxy = yes
#============================ Share Definitions
=============================
[homes]
comment = Home Directories
path = /eros10/home1/%u
admin users writable = yes
read only = no
follow symlinks = No
[USERS]
comment = USERS Directories
path = */cds/users/*%u
admin users read only = No
follow symlinks = No
followed by similar other share definitions.
Does anyone have any ideas on why the daemon is either spawning or failing
to get killed?
Thanks in advance
Jim Ballantine
On Tue, Aug 30, 2016 at 10:39:04AM -0400, Jim Ballantine via samba wrote:> We are running a Red Hat Linux 6 system with samba 3.6.23 installed, and > configured as a stand alone > server. A couple of users are either spawning excessive numbers of smbd, > or failing to kill themIs this smbds in "D" state? If so, please contact RedHat. That's a kernel bug, or something below like a failed disk. Volker