Samba on RH Enterprise Linux 3.0
Neha Patel
npatel at nevi-soft.com
Mon Jul 25 00:34:53 GMT 2005
Hi,
We have a client running RH ES 3.0 with Samba 3.0 to access/share
documents between windows 98 and XP users. They have been running on
this configuration for 2 months and have recently started seeing locking
problems when accessing word documents. Inspecting the logs following
errors seem to show up over and over again:
Jul 21 16:08:48 YLES30 smbd[16828]: oplock_break: client failure in
oplock bre
ak in file S Drive From NT/Correspondence Templates/Renewals/GBP
Nautical to War
ta Renewal Quote 2005.doc
Jul 21 16:57:33 YLES30 smbd[16824]: [2005/07/21 16:57:33, 0]
lib/fault.c:fault_r
eport(36)
Jul 21 16:57:33 YLES30 smbd[16824]:
==========================================
=====================
Jul 21 16:57:33 YLES30 smbd[16824]: [2005/07/21 16:57:33, 0]
lib/fault.c:fault_r
eport(37)
Jul 21 16:57:33 YLES30 smbd[16824]: INTERNAL ERROR: Signal 11 in pid
16824 (3.
0.0-14.3E)
Jul 21 16:57:33 YLES30 smbd[16824]: Please read the appendix Bugs of
the Samba
HOWTO collection
Jul 21 16:57:33 YLES30 smbd[16824]: [2005/07/21 16:57:33, 0]
lib/fault.c:fault_r
eport(39)
Jul 21 16:57:33 YLES30 smbd[16824]:
==========================================
=====================
Jul 21 16:57:33 YLES30 smbd[16824]: [2005/07/21 16:57:33, 0]
lib/util.c:smb_pani
c(1422)
Jul 21 16:57:33 YLES30 smbd[16824]: PANIC: internal error
Jul 21 16:57:33 YLES30 smbd[16824]: [2005/07/21 16:57:33, 0]
lib/util.c:smb_pani
c(1429)
Jul 21 16:57:33 YLES30 smbd[16824]: BACKTRACE: 18 stack frames:
Jul 21 16:57:33 YLES30 smbd[16824]: #0 smbd(smb_panic+0x11c)
[0x81bbedc]
Jul 21 16:57:33 YLES30 smbd[16824]: #1 smbd [0x81aa652]
Jul 21 16:57:33 YLES30 smbd[16824]: #2 /lib/tls/libc.so.6
[0xb725ebe8]
Jul 21 16:57:33 YLES30 smbd[16824]: #3 /lib/tls/libc.so.6
[0xb72a867a]
Jul 21 16:57:33 YLES30 smbd[16824]: #4
/lib/tls/libc.so.6(__libc_realloc+0x10
6) [0xb72a70b6]
Jul 21 16:57:33 YLES30 smbd[16824]: #5 smbd(Realloc+0x80) [0x81bb050]
Jul 21 16:57:33 YLES30 smbd[16824]: #6 smbd(OpenDir+0x321)
[0x8085c41]
Jul 21 16:57:33 YLES30 smbd[16824]: #7 smbd [0x8084914]
Jul 21 16:57:33 YLES30 smbd[16824]: #8 smbd(dptr_create+0x22)
[0x8084a62]
Jul 21 16:57:33 YLES30 smbd[16824]: #9 smbd [0x80abc05]
Jul 21 16:57:33 YLES30 smbd[16824]: #10 smbd(reply_trans2+0x69c)
[0x80b3e4c]
Jul 21 16:57:33 YLES30 smbd[16824]: #11 smbd [0x80c7286]
Jul 21 16:57:33 YLES30 smbd[16824]: #12 smbd [0x80c7459]
Jul 21 16:57:33 YLES30 smbd[16824]: #13 smbd(process_smb+0x8f)
[0x80c766f]
Jul 21 16:57:33 YLES30 smbd[16824]: #14 smbd(smbd_process+0x167)
[0x80c82a7]
Jul 21 16:57:33 YLES30 smbd[16824]: #15 smbd(main+0x4bf) [0x822407f]
Jul 21 16:57:33 YLES30 smbd[16824]: #16
/lib/tls/libc.so.6(__libc_start_main+
Jul 21 16:57:33 YLES30 smbd[16824]: #17 smbd(ldap_msgfree+0x69)
[0x8076ba1]
Jul 21 16:57:33 YLES30 smbd[16938]: [2005/07/21 16:57:33, 0]
lib/util_sock.c:get
_socket_addr(919)
Jul 21 16:57:33 YLES30 smbd[16938]: getpeername failed. Error was
Transport en
dpoint is not connected
Jul 21 16:57:33 YLES30 smbd[16938]: write_socket_data: write failure.
Error =
Connection reset by peer
Jul 21 16:57:33 YLES30 smbd[16938]: [2005/07/21 16:57:33, 0]
lib/util_sock.c:wri
te_socket(413)
Jul 21 16:57:33 YLES30 smbd[16938]: write_socket: Error writing 4
bytes to soc
ket 5: ERRNO = Connection reset by peer
Jul 21 16:57:33 YLES30 smbd[16938]: [2005/07/21 16:57:33, 0]
lib/util_sock.c:sen
d_smb(585)
Jul 21 16:57:33 YLES30 smbd[16938]: Error writing 4 bytes to client.
-1. (Conn
ection reset by peer)
Jul 21 16:58:49 YLES30 smbd[16939]: [2005/07/21 16:58:49, 0]
smbd/oplock.c:oploc
k_break(807)
Jul 21 16:58:49 YLES30 smbd[16939]: oplock_break: receive_smb timed
out after
30 seconds.
Jul 21 16:58:49 YLES30 smbd[16939]: oplock_break failed for file S
Drive From
NT/Correspondence Templates/Renewals/GBP Warta Renewal Quote 2005 -
Broker.doc (
dev = 806, inode = 1201347, file_id = 4).
Jul 21 16:58:49 YLES30 smbd[16939]: [2005/07/21 16:58:49, 0]
smbd/oplock.c:oploc
k_break(879)
Jul 21 16:58:49 YLES30 smbd[16939]: oplock_break: client failure in
oplock bre
ak in file S Drive From NT/Correspondence Templates/Renewals/GBP Warta
Renewal Q
uote 2005 - Broker.doc
Jul 21 17:28:39 YLES30 smbd[16301]: [2005/07/21 17:28:39, 0]
lib/util_sock.c:rea
d_socket_data(342)
Jul 21 17:28:39 YLES30 smbd[16301]: read_socket_data: recv failure for
4. Erro
r = No route to host
The samba configuration is:
sh-2.05b$ testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[netlogon]"
Processing section "[printers]"
Global parameter printcap name found in service section!
Processing section "[pr2]"
Global parameter printcap name found in service section!
No path in service pr2 - using /tmp
Processing section "[root directory]"
Processing section "[khurst]"
Processing section "[lauren]"
Processing section "[wayne]"
Processing section "[/-1]"
Processing section "[users]"
Processing section "[vtapes]"
Loaded services file OK.
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
workgroup = YACHTLINE
server string = samba server
security = SHARE
password server = None
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
hosts allow = 192.168.0.
[homes]
comment = Home Directories
path = /u/users
read only = No
create mask = 0666
directory mask = 0777
guest ok = Yes
[netlogon]
comment = Network Logon Service
path = /u/users
read only = No
force create mode = 0666
directory mask = 0777
guest ok = Yes
share modes = No
[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0777
printable = Yes
print command = lp -d %p -o raw %s -r
lpq command = lpstat -o %p
lprm command = cancel %p-%j
browseable = No
[pr2]
path = /tmp
guest ok = Yes
printable = Yes
printing = sysv
print command = lp -o raw %s
I have searched the web and found the same problem has already been
reported. The solution suggested is to upgrade to later version of Samba
but its not very clear as to which later version of samba will solve
this problem.
Can you please advise a compatible version with RHES 3.0 that will
resolve this problem?
Thanks and regards
Neha.
More information about the samba-technical
mailing list