Hello,
after an update from Samba 2.2.12 to 3.0.22 and running the daemons 2-3
days my Samba Server freeze the whole Server.
First the clients get connection problems, timing out to access the shares
and then some minutes later the whole Server freeze, i can't even logon on
the console. Only a cold reset is possible.
I convert all files from latin-1 to a UTF-8 and then from UTF-8 to
ISO-8859-1 (german filenames) with conmv.
It works in ADS mode and kerberos is working fine, also i get the list of
Domain user and groups.
The System ist a Debian 3.1 with ext3 filesystem.
The files lay on a ReiserFS 3.6 with standard journal. Its a RAID 5 System
with a Mylex Controller (DAC960)
The old installation Suse 8.1 with Samba 2.2.12 works without any problems.
In the main smbd.log there are no error messages.
All error message in the log files are from clients:
Client example No. 1
[2006/04/25 12:58:50, 0] smbd/oplock.c:oplock_timeout_handler(366)
Oplock break failed for file asmallernote/note.ini -- replying anyway
[2006/04/25 12:58:50, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:58:50, 0] smbd/oplock.c:remove_oplock(189)
remove_oplock: failed to lock share entry for file asmallernote/note.ini
[2006/04/25 12:58:50, 0]
libsmb/smb_signing.c:srv_check_incoming_message(782)
srv_check_incoming_message: BAD SIG: seq 567 wanted SMB signature of
[2006/04/25 12:58:50, 0]
libsmb/smb_signing.c:srv_check_incoming_message(786)
srv_check_incoming_message: BAD SIG: seq 567 got SMB signature of
[2006/04/25 12:58:50, 0]
libsmb/smb_signing.c:srv_check_incoming_message(798)
srv_check_incoming_message: out of seq. seq num 566 matches. We were
expecting seq 567
[2006/04/25 12:58:50, 0] libsmb/smb_signing.c:signing_good(240)
signing_good: BAD SIG: seq 567
[2006/04/25 12:58:50, 0] lib/util_sock.c:receive_smb(737)
receive_smb: SMB Signature verification failed on incoming packet!
[2006/04/25 12:58:50, 2] smbd/server.c:exit_server(614)
Closing connections
[2006/04/25 12:58:50, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:58:50, 0] smbd/close.c:close_normal_file(204)
close_file: Could not get share mode lock for file
[2006/04/25 12:58:50, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:58:50, 0] smbd/close.c:close_normal_file(204)
close_file: Could not get share mode lock for file
[2006/04/25 12:58:50, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:58:50, 0] smbd/close.c:close_normal_file(204)
close_file: Could not get share mode lock for file
CLient example No. 2
[2006/04/25 12:04:02, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:04:02, 0] smbd/close.c:close_normal_file(204)
close_file: Could not get share mode lock for file
[2006/04/25 12:04:02, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:04:02, 0] smbd/close.c:close_normal_file(204)
The logfile wb-Domainname has sometimes this error messages
[2006/04/25 13:17:46, 2]
libsmb/cliconnect.c:cli_session_setup_kerberos(533)
Doing kerberos session setup
[2006/04/25 13:17:47, 0] lib/util_sid.c:string_to_sid(285)
string_to_sid: Sid S-0-0 is not in a valid format.
[2006/04/25 13:17:47, 0] lib/util_sid.c:string_to_sid(285)
string_to_sid: Sid S-0-0 is not in a valid format.
This is my samba configuration:
# Date: 2006/04/18 10:21:56
[global]
unix charset = ISO8859-1
display charset = ISO8859-1
workgroup = DOMAINNAME
realm = DOMAINNAME.LOCAL
server string = %h server (Samba %v)
security = ADS
update encrypted = Yes
client schannel = No
server schannel = No
allow trusted domains = No
password server = erpel, ente
use kerberos keytab = Yes
log level = 2
syslog = 0
smb ports = 445
log file = /var/log/samba/log.%m
max log size = 1000
server signing = auto
socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY
SO_SNDBUF=65535 SO_RCVBUF=65535
ldap admin dn = cn=Administrator,cn=Users,dc=domain-name,dc=local
ldap delete dn = Yes
ldap idmap suffix = cn=idmap
ldap suffix = dc=domainname,dc=local
ldap ssl = no
panic action = /usr/share/samba/panic-action %d
idmap backend = ad
idmap uid = 10000-20000
idmap gid = 10000-20000
winbind use default domain = Yes
winbind nested groups = Yes
winbind nss info = sfu
blocking locks = No
follow symlinks = no
max xmit = 65535
nt acl support = No
[homes]
comment = Home Directories
read only = No
create mask = 0700
directory mask = 0700
browseable = No
vfs objects = recycle
recycle: repository = _Papierkorb_
recycle: keeptree = Yes
recycle: exclude = *.tmp, *.temp, *.log, *.ldb
recycle: exclude_dir = tmp
recycle:versions = Yes
[Postkasten]
comment = Postkaesten
path = /work4/postkasten
force group = Dom?nen-Benutzer
read only = No
force create mode = 0777
force directory mode = 0777
guest ok = Yes
block size = 10240
vfs objects = recycle
recycle: repository = _Papierkorb_
recycle: keeptree = Yes
recycle: exclude = *.tmp, *.temp, *.log, *.ldb
recycle: exclude_dir = tmp
recycle:versions = Yes
# /etc/nsswitch.conf
#
passwd: files winbind
group: files winbind
shadow: compat
hosts: files dns winbind
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
Any ideas how i can find the failure and fix it?
I guess it has something to do with ReiserFS but i am not sure.
Thanks in advance
--
Thorsten Hamester
Systemadministrator
APE GmbH
Plauener Str. 163-165 Haus 13
D 13053 Berlin
Tel.: +49 30 986011-59
Fax: +49 30 98697885
E-Mail: thorsten_hamester@ape-berlin.de
Web: http://www.ape-berlin.de
Hello,
after an update from Samba 2.2.12 to 3.0.22 and running the daemons 2-3
days my Samba Server freeze the whole Server.
First the clients get connection problems, timing out to access the shares
and then some minutes later the whole Server freeze, i can't even logon on
the console. Only a cold reset is possible.
I convert all files from latin-1 to a UTF-8 and then from UTF-8 to
ISO-8859-1 (german filenames) with conmv.
It works in ADS mode and kerberos is working fine, also i get the list of
Domain user and groups.
The System ist a Debian 3.1 with ext3 filesystem.
The files lay on a ReiserFS 3.6 with standard journal. Its a RAID 5 System
with a Mylex Controller (DAC960)
The old installation Suse 8.1 with Samba 2.2.12 works without any problems.
In the main smbd.log there are no error messages.
All error message in the log files are from clients:
Client example No. 1
[2006/04/25 12:58:50, 0] smbd/oplock.c:oplock_timeout_handler(366)
Oplock break failed for file asmallernote/note.ini -- replying anyway
[2006/04/25 12:58:50, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:58:50, 0] smbd/oplock.c:remove_oplock(189)
remove_oplock: failed to lock share entry for file
asmallernote/note.ini
[2006/04/25 12:58:50, 0]
libsmb/smb_signing.c:srv_check_incoming_message(782)
srv_check_incoming_message: BAD SIG: seq 567 wanted SMB signature of
[2006/04/25 12:58:50, 0]
libsmb/smb_signing.c:srv_check_incoming_message(786)
srv_check_incoming_message: BAD SIG: seq 567 got SMB signature of
[2006/04/25 12:58:50, 0]
libsmb/smb_signing.c:srv_check_incoming_message(798)
srv_check_incoming_message: out of seq. seq num 566 matches. We were
expecting seq 567
[2006/04/25 12:58:50, 0] libsmb/smb_signing.c:signing_good(240)
signing_good: BAD SIG: seq 567
[2006/04/25 12:58:50, 0] lib/util_sock.c:receive_smb(737)
receive_smb: SMB Signature verification failed on incoming packet!
[2006/04/25 12:58:50, 2] smbd/server.c:exit_server(614)
Closing connections
[2006/04/25 12:58:50, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:58:50, 0] smbd/close.c:close_normal_file(204)
close_file: Could not get share mode lock for file
[2006/04/25 12:58:50, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:58:50, 0] smbd/close.c:close_normal_file(204)
close_file: Could not get share mode lock for file
[2006/04/25 12:58:50, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:58:50, 0] smbd/close.c:close_normal_file(204)
close_file: Could not get share mode lock for file
CLient example No. 2
[2006/04/25 12:04:02, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:04:02, 0] smbd/close.c:close_normal_file(204)
close_file: Could not get share mode lock for file
[2006/04/25 12:04:02, 0] tdb/tdbutil.c:tdb_log(772)
tdb(/var/run/samba/locking.tdb): tdb_lock failed on list 365 ltype=1
(Resource deadlock avoided)
[2006/04/25 12:04:02, 0] smbd/close.c:close_normal_file(204)
The logfile wb-Domainname has sometimes this error messages
[2006/04/25 13:17:46, 2]
libsmb/cliconnect.c:cli_session_setup_kerberos(533)
Doing kerberos session setup
[2006/04/25 13:17:47, 0] lib/util_sid.c:string_to_sid(285)
string_to_sid: Sid S-0-0 is not in a valid format.
[2006/04/25 13:17:47, 0] lib/util_sid.c:string_to_sid(285)
string_to_sid: Sid S-0-0 is not in a valid format.
This is my samba configuration:
# Date: 2006/04/18 10:21:56
[global]
unix charset = ISO8859-1
display charset = ISO8859-1
workgroup = DOMAINNAME
realm = DOMAINNAME.LOCAL
server string = %h server (Samba %v)
security = ADS
update encrypted = Yes
client schannel = No
server schannel = No
allow trusted domains = No
password server = erpel, ente
use kerberos keytab = Yes
log level = 2
syslog = 0
smb ports = 445
log file = /var/log/samba/log.%m
max log size = 1000
server signing = auto
socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY
SO_SNDBUF=65535 SO_RCVBUF=65535
ldap admin dn = cn=Administrator,cn=Users,dc=domain-name,dc=local
ldap delete dn = Yes
ldap idmap suffix = cn=idmap
ldap suffix = dc=domainname,dc=local
ldap ssl = no
panic action = /usr/share/samba/panic-action %d
idmap backend = ad
idmap uid = 10000-20000
idmap gid = 10000-20000
winbind use default domain = Yes
winbind nested groups = Yes
winbind nss info = sfu
blocking locks = No
follow symlinks = no
max xmit = 65535
nt acl support = No
[homes]
comment = Home Directories
read only = No
create mask = 0700
directory mask = 0700
browseable = No
vfs objects = recycle
recycle: repository = _Papierkorb_
recycle: keeptree = Yes
recycle: exclude = *.tmp, *.temp, *.log, *.ldb
recycle: exclude_dir = tmp
recycle:versions = Yes
[Postkasten]
comment = Postkaesten
path = /work4/postkasten
force group = Dom?nen-Benutzer
read only = No
force create mode = 0777
force directory mode = 0777
guest ok = Yes
block size = 10240
vfs objects = recycle
recycle: repository = _Papierkorb_
recycle: keeptree = Yes
recycle: exclude = *.tmp, *.temp, *.log, *.ldb
recycle: exclude_dir = tmp
recycle:versions = Yes
# /etc/nsswitch.conf
#
passwd: files winbind
group: files winbind
shadow: compat
hosts: files dns winbind
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
Any ideas how i can find the failure and fix it?
I guess it has something to do with ReiserFS but i am not sure.
Thanks in advance
--
Thorsten Hamester
Systemadministrator
Web: http://www.ape-berlin.de