[Samba] Errors found: Abacus Law lock failure

[Jeff Green]

>> >I'm attempting to install Abacus Law (v13) under Samba and Linux. Install
>> >completes, and I get as far as a single user successfully logged in, but
>> >the 2nd user is nothing but trouble. Samba logs show nothing unusual to my
>> >semi-trained eye, but locking code or timing is a likely suspect. Technical
>> >support is of no help as they haven't tested (and therefore don't support)
>> >the application under Samba and/or Linux.
>> >
>> >Though I have it installed and working on one very similar network,
>> >duplicating everything to the smallest detail possible hasn't provided a
>> >working configuration. I've also tried two other versions (2.0.8 and 2.2.12
>> >in addition to the current Debian/Woody version 2.2.3a-6)
>> >
>> >  I'm looking for someone else who has this application running that would
>> >be willing to collaborate on configuration and technical support issues.
>> >Failing this, Linux must convert over to a supported NOS as this is a
>> >critical application.
>
>(Bob Crandell:)
>Add or change these lines to read:
>oplocks = no
>level2 oplocks = no
>kernel oplocks = no
>
>All multi user programs seem to need this at some level.

>(Jeff Green)
>I appreciate the pointers. The server is running a 2.2 kernel, and my 
>reading of pertinent messages led me to believe "kernel oplocks" is a 2.4 
>kernel feature only. I added it to the global section (the others were 
>already there), but there is no difference.
>
>The matching share on a working system is as follows (and has been 
>duplicated here):
>
>[data]
>         comment = Databases
>         path = /samba/data
>         force group = samba
>         read only = No
>         browsable = yes
>         oplocks = no
>         kernel oplocks = no
>         guest ok = no
>         create mask = 0660
>         directory mask = 02770
>         valid users = @samba
>
>Any other thoughts (or specific experience with this application)?

Debugging a bit more today pointed out the error, which repeats continually 
(changing only the transaction#) until the application is shut down from 
the task manager. This is a shared database application hanging ("not 
responding") when reading and/or creating index files. Samba version 
2.2.3a-6 on Linux/Debian Woody with kernel 2.2.16. Server platforms are a 
P75 (testing) and a PIII 1.2GHZ (production), with tested client OS Windows 
95, 98SE, ME, and XP Home.

(debug level 3 output):

[2002/07/12 10:37:28, 3] smbd/process.c:process_smb(860)
   Transaction 6437 of length 65
[2002/07/12 10:37:28, 3] smbd/process.c:switch_message(667)
   switch message SMBlockingX (pid 6934)
[2002/07/12 10:37:28, 3] lib/util.c:fcntl_lock(1287)
   fcntl_lock: fcntl lock gave errno 75 (Value too large for defined data type)
[2002/07/12 10:37:28, 3] lib/util.c:fcntl_lock(1309)
   fcntl_lock: lock failed at offset 4294904391 count 1 op 13 type 1 (Value 
too large for defined data type)
[2002/07/12 10:37:28, 3] smbd/error.c:error_packet(91)
   error string = Value too large for defined data type
[2002/07/12 10:37:28, 3] smbd/error.c:error_packet(120)
   error packet at smbd/reply.c(4516) cmd=36 (SMBlockingX) eclass=1 ecode=33
[2002/07/12 10:37:28, 3] smbd/process.c:process_smb(860)
   Transaction 6438 of length 65
....

Locking failures as I suspected. Not exactly sure what's happening here 
with the data types as I'm a very read of C structures. Suggestions? I'd 
far rather this were a version upgrade issue than a need to move the server 
to a new NOS.

(By the way, it's absolutely wonderful to be able to get this kind of output)

Jeff


Jeffrey B. Green		Personal Computer Consultant - Las Vegas, Nevada
http://jbgreen.com		Networking Las Vegas Since 1986