Locking db getting corrupt?
Ray Frush
frush at ftc.agilent.com
Thu Feb 20 15:25:44 GMT 2003
We've been seeing a re-curring problem on one of our Samba servers:
Samba 2.2.7 running on HP-UX 11.0.
After a week of running relatively quietly, we'll get a rash of errors
in smbd.log associated with a call from a user that their connection is
getting dropped.
" I_ve been dropped off twice in
the past couple of days. So far I_ve been able to
get back on -- once took a reboot of my pc, this
time it only took trying to reconnect several
times."
[2003/02/19 12:25:46, 3] smbd/oplock.c:(1211)
open_oplock_ipc: opening loopback UDP socket.
[2003/02/19 12:25:46, 3] lib/util_sock.c:(813)
bind succeeded on port 0
[2003/02/19 12:25:46, 3] smbd/oplock.c:(1241)
open_oplock ipc: pid = 18635, global_oplock_port = 60186
[2003/02/19 12:25:46, 3] smbd/process.c:(878)
Transaction 0 of length 72
[2003/02/19 12:25:46, 2] smbd/reply.c:(91)
netbios connect: name1=ICTEST1 name2=FCMC7196LL
[2003/02/19 12:25:46, 2] smbd/reply.c:(110)
netbios connect: local=ictest1 remote=fcmc7196ll
[2003/02/19 12:45:24, 0] locking/brlock.c:(235)
Failed to open byte range locking database
[2003/02/19 12:45:24, 0] locking/locking.c:(328)
ERROR: Failed to initialise locking database
[2003/02/19 12:45:24, 0] locking/brlock.c:(235)
Failed to open byte range locking database
[2003/02/19 12:45:24, 0] locking/locking.c:(328)
ERROR: Failed to initialise locking database
[2003/02/19 12:50:04, 3] smbd/oplock.c:(1211)
open_oplock_ipc: opening loopback UDP socket.
[2003/02/19 12:50:04, 3] lib/util_sock.c:(813)
bind succeeded on port 0
[2003/02/19 12:50:04, 3] smbd/oplock.c:(1241)
open_oplock ipc: pid = 18875, global_oplock_port = 60285
[2003/02/19 12:50:04, 3] smbd/process.c:(878)
Transaction 0 of length 72
[2003/02/19 12:50:04, 2] smbd/reply.c:(91)
netbios connect: name1=ICTEST1 name2=SJPCT2679-D
[2003/02/19 12:50:04, 2] smbd/reply.c:(110)
netbios connect: local=ictest1 remote=sjpct2679-d
The above pattern of messages repeats several times in the log, and then
disappears again. In past occurances, we've stopped Samba, deleted all
the locking databases, and restarted which cleared up more persistant
occurances of this issue, but I'd like to discover the root cause.
--
Ray Frush "Either you are part of the solution
T:970.288.6223 or part of the precipitate."
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
Agilent Technologies, Inc. | Information Technology | IT Engineer
More information about the samba-technical
mailing list