Bug 5154 - client sent 0/0 lock - please report this
client sent 0/0 lock - please report this
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: File Services
3.0.28
x86 Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-19 21:42 UTC by Trevor Cordes
Modified: 2007-12-19 21:42 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Trevor Cordes 2007-12-19 21:42:47 UTC
Just upgraded two boxes from FC5 to F8.  Right after the upgrade smb.log starts showing these errors and I now have reports of file-sharing based apps crashing frequently during the day.  Everything was stable and fine before the upgrade.

Box 1: samba-3.0.28-0.fc8
Box 2: samba-3.0.27a-0.fc8

Prior to the upgrade they were: samba-3.0.24-3.fc5 (free of problems)

I'm not sure if my app crashes are due to this 0/0 lock error, but it seems a good place to start.

I just noticed that these errors always directly follow lines showing "closed connection" from the same machines at both locations.  Both locations are running the same apps and the same setups.  In both cases the machines are somewhat unique in that they are the only boxes in each office running this special app module (a patient self-check-in function) (10-20 other machines run the normal app without error it would seem).  For years we've had intermittent issues with this app doing weird things and the devs never have been able to find it, but they use Windows servers for testing, not samba.  Perhaps it's been a glitch in samba all this time, but only recently was this debug check output made visible?

All boxes are XP Pro in the box 1 network (about 25 comps).  Box 2 network is a mix of XP Home & Pro (about 15 comps).  The app is MSDE/MDB based, pretty basic normal MS stuff.  It is all served off the samba server.

Some logs:

[2007/12/17 08:57:29, 1] smbd/service.c:close_cnum(1230)
  192.168.101.241 (192.168.101.241) closed connection to service shared
[2007/12/17 08:57:33, 1] smbd/service.c:make_connection_snum(1033)
  192.168.101.241 (192.168.101.241) connect to service shared initially as user samba (uid=300, gid=300) (pid 17434)
[2007/12/17 08:57:41, 0] locking/brlock.c:brl_lock(754)
  client sent 0/0 lock - please report this
[2007/12/17 08:57:43, 0] locking/brlock.c:brl_lock(754)
  client sent 0/0 lock - please report this
[2007/12/17 08:58:01, 1] smbd/service.c:make_connection_snum(1033)
  192.168.101.236 (192.168.101.236) connect to service tracker initially as user samba (uid=300, gid=300) (pid 26490)
[2007/12/17 08:58:12, 1] smbd/service.c:close_cnum(1230)
  192.168.101.236 (192.168.101.236) closed connection to service tracker
[2007/12/17 08:59:03, 1] smbd/service.c:make_connection_snum(1033)
  192.168.101.236 (192.168.101.236) connect to service tracker initially as user samba (uid=300, gid=300) (pid 26706)


[2007/12/17 10:26:35, 1] smbd/service.c:close_cnum(1230)
  192.168.100.246 (192.168.100.246) closed connection to service tracker
[2007/12/17 10:27:25, 1] smbd/service.c:make_connection_snum(1033)
  192.168.100.246 (192.168.100.246) connect to service tracker initially as user samba (uid=300, gid=300) (pid 30605)
[2007/12/17 10:27:30, 0] locking/brlock.c:brl_lock(754)
  client sent 0/0 lock - please report this
[2007/12/17 10:27:33, 0] locking/brlock.c:brl_lock(754)
  client sent 0/0 lock - please report this
[2007/12/17 10:27:36, 1] smbd/service.c:close_cnum(1230)
  192.168.100.246 (192.168.100.246) closed connection to service tracker
[2007/12/17 10:28:26, 1] smbd/service.c:make_connection_snum(1033)
  192.168.100.246 (192.168.100.246) connect to service tracker initially as user samba (uid=300, gid=300) (pid 31173)
[2007/12/17 10:28:38, 1] smbd/service.c:close_cnum(1230)
  192.168.100.246 (192.168.100.246) closed connection to service tracker