We have been using SAMBA for file/print servers and domain controllers
in Windows networks for several years. At one site, we have
intermittent problems in which the connection to the SAMBA server
appears to die: i.e., no one can connect to the share, and the Windows
clients (Terminal Servers and workstations) apparently keep re-trying to
connect which ultimately locks up those clients.
They have about 20 or so users, mostly doing MS Office stuff, opening
one very large MS Access database (around 400 Mb) and using a lot of
Outlook PST files - some over 1 Gb each. All of this data, as well as
their roaming profiles, is stored in the 'base' share listed in
smb.conf.
We have noticed in many cases, but not all, that there is an error in
/var/log/messages indicating that the samba process had an error and
apparently the process exits. I've included a sample from
/var/log/messages. In this case, we are using (2) Windows 2000 Terminal
Servers, as well as one XP workstation. The OS on the SAMBA server is:
Mandrake (Linux version 2.6.3-7mdk-p3-smp-64GB
(nplanel@n3.mandrakesoft.com) (gcc version 3.3.2 (Mandrake Linux 10.0
3.3.2-6mdk)) #1 SMP Wed Mar 17 15:34:39 CET 2004), and the SAMBA version
is: 3.0.2a. We also had the same problem using Fedora (Linux version
2.6.9-1.667smp (bhcompile@dolly.build.redhat.com) (gcc version 3.4.2
20041017 (Red Hat 3.4.2-6.fc3)) #1 SMP Tue Nov 2 15:09:11 EST 2004) with
SAMBA 3.0.8pre1-0.pre1.3.
Here is a copy of our smb.conf:
#=============================== Global Settings
========================[global]
create mask=777
force create mode=777
directory mask=777
add user script = /usr/sbin/addnewuser.sh %u
#addsharecommand = /usr/sbin/smbexecutechangeshare.sh
#deletesharecommand = /usr/sbin/smbexecutechangeshare.sh
workgroup = NP
netbios name = NETPUB_LINUX06
server string = NETPUB Linux File Server 06
local master = no
domain master = no
preferred master = no
log level = 3
log file = /var/log/samba/log.%m
max log size = 500
security = domain
password server = *
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no
#profile acls = yes
remote announce = 192.168.0.255
#wins server = 192.168.0.253
username level = 100
password level = 100
interfaces = eth2 192.168.0.1 lo
smb ports = 139
oplocks = no
level2 oplocks = no
#============================ Share Definitions
=============================#[homes]
# path = /home/
# comment = Home Directories
# browseable = yes
# public = yes
# writable = yes
[public]
path = /public
browseable = yes
public = yes
writable = yes
read only = no
guest OK = yes
profile acls = yes
[base]
path = /base
browseable = yes
public = yes
writable = yes
read only = no
guest OK = yes
profile acls = yes
csc policy = disable
oplocks = no
level2 oplocks = no
[usershare]
path = /base/USERS/%u
browseable = yes
public = yes
writable = yes
read only = no
guest OK = yes
profile acls = yes
;This next setting stands for /client-side caching policy/, and
specifies how
; clients capable of offline caching will cache the files in the
; share. The valid values are: manual, documents, programs, disable.
; These values correspond to those used on Windows servers.
; For example, shares containing roaming profiles can have offline
; caching disabled using *csc policy = disable*.
; Default: //csc policy/ = manual /
; Example: //csc policy/ = programs /
csc policy = disable
Here is a sample of /var/log/messages from just before one of the
'disconnect times':
May 24 10:57:54 localhost smbd[1723]: [2006/05/24 10:57:54, 0]
libsmb/clitrans.c:cli_receive_trans(190)
May 24 10:57:54 localhost smbd[1723]: Expected SMBtrans response, got
command 0x00
May 24 10:57:54 localhost smbd[1723]: [2006/05/24 10:57:54, 0]
rpc_client/cli_pipe.c:cli_nt_session_open(1454)
May 24 10:57:54 localhost smbd[1723]: cli_nt_session_open: pipe hnd
state failed. Error was SUCCESS - 0
May 24 10:58:39 localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/fault.c:fault_report(36)
May 24 10:58:39 localhost smbd[1723]:
==============================================================May 24 10:58:39
localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/fault.c:fault_report(37)
May 24 10:58:39 localhost smbd[1723]: INTERNAL ERROR: Signal 11 in pid
1723 (3.0.2a)
May 24 10:58:39 localhost smbd[1723]: Please read the appendix Bugs of
the Samba HOWTO collection
May 24 10:58:39 localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/fault.c:fault_report(39)
May 24 10:58:39 localhost smbd[1723]:
==============================================================May 24 10:58:39
localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/util.c:smb_panic(1400)
May 24 10:58:39 localhost smbd[1723]: PANIC: internal error
May 24 10:58:39 localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/util.c:smb_panic(1408)
May 24 10:58:39 localhost smbd[1723]: BACKTRACE: 4 stack frames:
May 24 10:58:39 localhost smbd[1723]: #0 smbd(smb_panic+0x1ab)
[0x81bc238]
May 24 10:58:39 localhost smbd[1723]: #1 smbd [0x81aacfd]
May 24 10:58:39 localhost smbd[1723]: #2 smbd [0x81aad72]
May 24 10:58:39 localhost smbd[1723]: #3 /lib/tls/libc.so.6 [0x40306718]
May 24 10:58:39 localhost smbd[1723]:
May 24 10:58:39 localhost smbd[7879]: [2006/05/24 10:58:39, 0]
auth/auth_domain.c:domain_client_validate(204)
May 24 10:58:39 localhost smbd[7879]: domain_client_validate: unable
to validate password for user kcr in domain NP
to Domain controller \\NETPUB_LINUX09. Error was NT_STATUS_WRONG_PASSWORD.
May 24 10:58:39 localhost smbd[7879]: [2006/05/24 10:58:39, 0]
auth/auth_domain.c:domain_client_validate(204)
May 24 10:58:39 localhost smbd[7879]: domain_client_validate: unable
to validate password for user spl in domain NP
to Domain controller \\NETPUB_LINUX09. Error was NT_STATUS_WRONG_PASSWORD.
May 24 10:58:39 localhost smbd[7879]: [2006/05/24 10:58:39, 0]
auth/auth_domain.c:domain_client_validate(204)
May 24 10:58:39 localhost smbd[7879]: domain_client_validate: unable
to validate password for user mcr in domain NP
to Domain controller \\NETPUB_LINUX09. Error was NT_STATUS_WRONG_PASSWORD.
**************
Thanks in advance for your help
Tom Ronayne
AIRO Tech OMD, Inc.
tom@airotech.com
(I may have posted this twice because I didn't understand the addressing
- sorry in advance if that is the case. . . .)
We have been using SAMBA for file/print servers and domain controllers
in Windows networks for several years. At one site, we have
intermittent problems in which the connection to the SAMBA server
appears to die: i.e., no one can connect to the share, and the Windows
clients (Terminal Servers and workstations) apparently keep re-trying to
connect which ultimately locks up those clients.
They have about 20 or so users, mostly doing MS Office stuff, opening
one very large MS Access database (around 400 Mb) and using a lot of
Outlook PST files - some over 1 Gb each. All of this data, as well as
their roaming profiles, is stored in the 'base' share listed in
smb.conf.
We have noticed in many cases, but not all, that there is an error in
/var/log/messages indicating that the samba process had an error and
apparently the process exits. I've included a sample from
/var/log/messages. In this case, we are using (2) Windows 2000 Terminal
Servers, as well as one XP workstation. The OS on the SAMBA server is:
Mandrake (Linux version 2.6.3-7mdk-p3-smp-64GB
(nplanel@n3.mandrakesoft.com) (gcc version 3.3.2 (Mandrake Linux 10.0
3.3.2-6mdk)) #1 SMP Wed Mar 17 15:34:39 CET 2004), and the SAMBA version
is: 3.0.2a. We also had the same problem using Fedora (Linux version
2.6.9-1.667smp (bhcompile@dolly.build.redhat.com) (gcc version 3.4.2
20041017 (Red Hat 3.4.2-6.fc3)) #1 SMP Tue Nov 2 15:09:11 EST 2004) with
SAMBA 3.0.8pre1-0.pre1.3.
Here is a copy of our smb.conf:
#=============================== Global Settings
========================[global]
create mask=777
force create mode=777
directory mask=777
add user script = /usr/sbin/addnewuser.sh %u
#addsharecommand = /usr/sbin/smbexecutechangeshare.sh
#deletesharecommand = /usr/sbin/smbexecutechangeshare.sh
workgroup = NP
netbios name = NETPUB_LINUX06
server string = NETPUB Linux File Server 06
local master = no
domain master = no
preferred master = no
log level = 3
log file = /var/log/samba/log.%m
max log size = 500
security = domain
password server = *
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no
#profile acls = yes
remote announce = 192.168.0.255
#wins server = 192.168.0.253
username level = 100
password level = 100
interfaces = eth2 192.168.0.1 lo
smb ports = 139
oplocks = no
level2 oplocks = no
#============================ Share Definitions
=============================#[homes]
# path = /home/
# comment = Home Directories
# browseable = yes
# public = yes
# writable = yes
[public]
path = /public
browseable = yes
public = yes
writable = yes
read only = no
guest OK = yes
profile acls = yes
[base]
path = /base
browseable = yes
public = yes
writable = yes
read only = no
guest OK = yes
profile acls = yes
csc policy = disable
oplocks = no
level2 oplocks = no
[usershare]
path = /base/USERS/%u
browseable = yes
public = yes
writable = yes
read only = no
guest OK = yes
profile acls = yes
;This next setting stands for /client-side caching policy/, and
specifies how
; clients capable of offline caching will cache the files in the
; share. The valid values are: manual, documents, programs, disable.
; These values correspond to those used on Windows servers.
; For example, shares containing roaming profiles can have offline
; caching disabled using *csc policy = disable*.
; Default: //csc policy/ = manual /
; Example: //csc policy/ = programs /
csc policy = disable
Here is a sample of /var/log/messages from just before one of the
'disconnect times':
May 24 10:57:54 localhost smbd[1723]: [2006/05/24 10:57:54, 0]
libsmb/clitrans.c:cli_receive_trans(190)
May 24 10:57:54 localhost smbd[1723]: Expected SMBtrans response, got
command 0x00
May 24 10:57:54 localhost smbd[1723]: [2006/05/24 10:57:54, 0]
rpc_client/cli_pipe.c:cli_nt_session_open(1454)
May 24 10:57:54 localhost smbd[1723]: cli_nt_session_open: pipe hnd
state failed. Error was SUCCESS - 0
May 24 10:58:39 localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/fault.c:fault_report(36)
May 24 10:58:39 localhost smbd[1723]:
==============================================================May 24 10:58:39
localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/fault.c:fault_report(37)
May 24 10:58:39 localhost smbd[1723]: INTERNAL ERROR: Signal 11 in pid
1723 (3.0.2a)
May 24 10:58:39 localhost smbd[1723]: Please read the appendix Bugs of
the Samba HOWTO collection
May 24 10:58:39 localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/fault.c:fault_report(39)
May 24 10:58:39 localhost smbd[1723]:
==============================================================May 24 10:58:39
localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/util.c:smb_panic(1400)
May 24 10:58:39 localhost smbd[1723]: PANIC: internal error
May 24 10:58:39 localhost smbd[1723]: [2006/05/24 10:58:39, 0]
lib/util.c:smb_panic(1408)
May 24 10:58:39 localhost smbd[1723]: BACKTRACE: 4 stack frames:
May 24 10:58:39 localhost smbd[1723]: #0 smbd(smb_panic+0x1ab)
[0x81bc238]
May 24 10:58:39 localhost smbd[1723]: #1 smbd [0x81aacfd]
May 24 10:58:39 localhost smbd[1723]: #2 smbd [0x81aad72]
May 24 10:58:39 localhost smbd[1723]: #3 /lib/tls/libc.so.6 [0x40306718]
May 24 10:58:39 localhost smbd[1723]:
May 24 10:58:39 localhost smbd[7879]: [2006/05/24 10:58:39, 0]
auth/auth_domain.c:domain_client_validate(204)
May 24 10:58:39 localhost smbd[7879]: domain_client_validate: unable
to validate password for user kcr in domain NP
to Domain controller \\NETPUB_LINUX09. Error was NT_STATUS_WRONG_PASSWORD.
May 24 10:58:39 localhost smbd[7879]: [2006/05/24 10:58:39, 0]
auth/auth_domain.c:domain_client_validate(204)
May 24 10:58:39 localhost smbd[7879]: domain_client_validate: unable
to validate password for user spl in domain NP
to Domain controller \\NETPUB_LINUX09. Error was NT_STATUS_WRONG_PASSWORD.
May 24 10:58:39 localhost smbd[7879]: [2006/05/24 10:58:39, 0]
auth/auth_domain.c:domain_client_validate(204)
May 24 10:58:39 localhost smbd[7879]: domain_client_validate: unable
to validate password for user mcr in domain NP
to Domain controller \\NETPUB_LINUX09. Error was NT_STATUS_WRONG_PASSWORD.
**************
Thanks in advance for your help
Tom Ronayne
AIRO Tech OMD, Inc.
tom@airotech.com
On Wed, May 24, 2006 at 02:50:34PM -0400, Tom Ronayne wrote:> We have been using SAMBA for file/print servers and domain controllers > in Windows networks for several years. At one site, we have > intermittent problems in which the connection to the SAMBA server > appears to die: i.e., no one can connect to the share, and the Windows > clients (Terminal Servers and workstations) apparently keep re-trying to > connect which ultimately locks up those clients. > > They have about 20 or so users, mostly doing MS Office stuff, opening > one very large MS Access database (around 400 Mb) and using a lot of > Outlook PST files - some over 1 Gb each. All of this data, as well as > their roaming profiles, is stored in the 'base' share listed in smb.conf. > > We have noticed in many cases, but not all, that there is an error in > /var/log/messages indicating that the samba process had an error and > apparently the process exits. I've included a sample from > /var/log/messages. In this case, we are using (2) Windows 2000 Terminal > Servers, as well as one XP workstation. The OS on the SAMBA server is: > Mandrake (Linux version 2.6.3-7mdk-p3-smp-64GB > (nplanel@n3.mandrakesoft.com) (gcc version 3.3.2 (Mandrake Linux 10.0 > 3.3.2-6mdk)) #1 SMP Wed Mar 17 15:34:39 CET 2004), and the SAMBA version > is: 3.0.2a. We also had the same problem using Fedora (Linux version > 2.6.9-1.667smp (bhcompile@dolly.build.redhat.com) (gcc version 3.4.2 > 20041017 (Red Hat 3.4.2-6.fc3)) #1 SMP Tue Nov 2 15:09:11 EST 2004) with > SAMBA 3.0.8pre1-0.pre1.3.These versions (3.0.2a and 3.0.8 - a *pre* release no less !) are rather old. Would it be possible to update them to the production 3.0.22 release to see if these problems have already been fixed ? Jeremy.