I would like to pose the following problem to this mailing list to see if any of you have any suggestions you may offer. I am running samba on a RedHat 7.2 Athalon box with software RAID 0 dual IDE disks on an ext3 filesystem. I have several users in a large community of users that are always hitting the samba server. The machine has been consistently reliable with one exception. There is a particularly large MS Access Database (10Meg) that everyone likes to use. A problem has developed from certain Win 98 and Win95 computers where users get an error message saying that someone currently has a lock on the database, and that it cannot be opened. However, smbstatus, reports that the user is actually trying to establish a lock on a different file, not the database in question. To add to the strangeness, I have opened the database on a different computer, and then all of a sudden everyone else can now open it as well. In addition to that, I had the database open from a win 98 machine, and someone else (that had been experiencing problems) opened it up, but smbstatus reports that the 2nd individual had a second file open in addition to the database, and clearly there were no other files open on that computer, by that user. So, we have files opening and getting locked when they were not opened, and a database that only certain users can open, cause other computers are being told that it is already open, and locked by a different user. Can anyone tell me what the heck is going on here, and what is the answer to this apparent lunacy ??? Thanks, Ruben
Ruben Fagundo wrote:> > > I would like to pose the following problem to this mailing list to see > if any of you have any suggestions you may offer. > > I am running samba on a RedHat 7.2 Athalon box with software RAID 0 > dual IDE disks on an ext3 filesystem. > > I have several users in a large community of users that are always > hitting the samba server. The machine has been consistently reliable > with one exception. There is a particularly large MS Access Database > (10Meg) that everyone likes to use. A problem has developed from > certain Win 98 and Win95 computers where users get an error message > saying that someone currently has a lock on the database, and that it > cannot be opened. However, smbstatus, reports that the user is > actually trying to establish a lock on a different file, not the > database in question. To add to the strangeness, I have opened the > database on a different computer, and then all of a sudden everyone > else can now open it as well. In addition to that, I had the database > open from a win 98 machine, and someone else (that had been > experiencing problems) opened it up, but smbstatus reports that the > 2nd individual had a second file open in addition to the database, and > clearly there were no other files open on that computer, by that > user. So, we have files opening and getting locked when they were not > opened, and a database that only certain users can open, cause other > computers are being told that it is already open, and locked by a > different user.Sounds like oplock problems (possibly) Try turning off oplocks on the Samba server and see if the problem disappears. The Windows 9X line has a lot of known bugs with regard to oplocks, and file-based databases (such as Access) tend to find these problems more often than other types of file access. You can also look at the "veto oplocks" feature to disable oplocking only on .mdb files.>
Is it trying to place a lock on the .LDB file and failing?
Can you post your log file messages, if any?
They should be in /var/log/messages or /var/log/samba/log.{machine}
Thanks.
-----Original Message-----
From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]On
Behalf Of Bill Moran
Sent: Tuesday, March 05, 2002 9:15 PM
To: Ruben Fagundo
Cc: samba@lists.samba.org; tiuzzol@MIT.EDU
Subject: Re: [Samba] Strange Problem with Access
Ruben Fagundo wrote:
>
>
> I would like to pose the following problem to this mailing list to see
> if any of you have any suggestions you may offer.
>
> I am running samba on a RedHat 7.2 Athalon box with software RAID 0
> dual IDE disks on an ext3 filesystem.
>
> I have several users in a large community of users that are always
> hitting the samba server. The machine has been consistently reliable
> with one exception. There is a particularly large MS Access Database
> (10Meg) that everyone likes to use. A problem has developed from
> certain Win 98 and Win95 computers where users get an error message
> saying that someone currently has a lock on the database, and that it
> cannot be opened. However, smbstatus, reports that the user is
> actually trying to establish a lock on a different file, not the
> database in question. To add to the strangeness, I have opened the
> database on a different computer, and then all of a sudden everyone
> else can now open it as well. In addition to that, I had the database
> open from a win 98 machine, and someone else (that had been
> experiencing problems) opened it up, but smbstatus reports that the
> 2nd individual had a second file open in addition to the database, and
> clearly there were no other files open on that computer, by that
> user. So, we have files opening and getting locked when they were not
> opened, and a database that only certain users can open, cause other
> computers are being told that it is already open, and locked by a
> different user.
Sounds like oplock problems (possibly)
Try turning off oplocks on the Samba server and see if the problem
disappears.
The Windows 9X line has a lot of known bugs with regard to oplocks, and
file-based databases (such as Access) tend to find these problems more often
than other types of file access. You can also look at the "veto
oplocks" feature
to disable oplocking only on .mdb files.
>
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
I have set the veto oplocks = /*.mdb/ and I'll see what happens today. If this fails, I'll try to isolate a specific log file without the extra junk. I'll set the log level to 10 or so. It seems that there are some newsgroup articles of problems with oplocks, and MS Access. I would have never thought of this. Thanks for your input. Regards, Ruben
> >I set the following options up and I still seem to have the same >problem. Did I set the oplock setting correctly??? I get the following >error message, exactly from the win95 machines: > >"The Microsoft database engine stopped the process because you or another >user is attempting to change the same data at the same time." > >The pertinent setting in smb.conf are as follows: >==================================>[global] > >veto oplock files = /*.mdb/*.MDB/ > > [public] > locking = yes > oplocks = yes > veto oplock files = /*.dba/*.dbm/*.mdb/*.MDB/ > share modes = yes > strict locking = no > comment = Temporary file space > path = /home/apps/public > public = yes > writeable = yes > create mode = 0777 > directory mode = 0775
Access opens *.ldb file that does the user-level locking. These can get corrupted when an application exits ungracefully. A symptom of a corrupted *.ldb file is that Access reports the database is opened exclusively by another user. Check to see that no one is actually using the database with smbstatus and delete the *.ldb file. The database should open normally. -- Glenn Scherb Midwest Research Institute 425 Volker Boulevard Kansas City, Missouri 64110 gscherb@mriresearch.org http://www.mriresearch.org Phone: (816)753-7600 x1806 FAX: (816)753-5359 Page: (816)990-8513 pagegscherb@mriresearch.org -----Original Message----- From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org] On Behalf Of Bill Moran Sent: Wednesday, March 06, 2002 7:45 PM To: Ruben Fagundo Cc: sbawa@tabmaster.com; samba@lists.samba.org Subject: Re: [Samba] Strange Problem with Access Ruben Fagundo wrote:> >> >> I set the following options up and I still seem to have the same >> problem. Did I set the oplock setting correctly??? >It looks right, as best as I can tell.>> I get the following error message, exactly from the win95 machines: >> >> "The Microsoft database engine stopped the process because you or >> another user is attempting to change the same data at the same time.">Could it (possibly) be some other problem with the Access file itself? (just speculating)>> >> >> The pertinent setting in smb.conf are as follows: >> ==================================>> [global] >> >> veto oplock files = /*.mdb/*.MDB/ >> >> [public] >> locking = yes >> oplocks = yes >> veto oplock files = /*.dba/*.dbm/*.mdb/*.MDB/ >> share modes = yes >> strict locking = no >> comment = Temporary file space >> path = /home/apps/public >> public = yes >> writeable = yes >> create mode = 0777 >> directory mode = 0775 >Doesn't Access use some other sort of file? .mde or something? If you run "smbstatus" while Access is running, what kind of locks does it show on the files? Check that out to see if it's working, and if you've got all the apropriate file patterns. I would suggest two things (in order): 1. Try turning off oplocks altogether 2. Figure that I was wrong about the oplocks and look at other possibilities. How much would it take to install MySQL and put the Access database there? MySQL works great with Access through the MyODBC driver. (I know this is changing lanes without signalling, but I just thought I'd throw it out there.) -Bill -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
For the database experiencing problems, there was not ldb file found. I did find an ldb file for a completely different database, but not for the one that is causing me all this grief. I have added the /*.ldb/ to the veto oplock option to see what happens. I also downloaded 3.2.3a sources, and I'll be installing it over the weekend. I'll keep everyone informed of what I find. Thanks for the input, Ruben At 02:00 PM 3/8/02 -0600, Glenn Scherb wrote:>Access opens *.ldb file that does the user-level locking. These can get >corrupted when an application exits ungracefully. A symptom of a >corrupted *.ldb file is that Access reports the database is opened >exclusively by another user. Check to see that no one is actually using >the database with smbstatus and delete the *.ldb file. The database >should open normally. > >-- >Glenn Scherb >Midwest Research Institute >425 Volker Boulevard >Kansas City, Missouri 64110 >gscherb@mriresearch.org >http://www.mriresearch.org > >Phone: (816)753-7600 x1806 >FAX: (816)753-5359 >Page: (816)990-8513 >pagegscherb@mriresearch.org > > > >-----Original Message----- >From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org] >On Behalf Of Bill Moran >Sent: Wednesday, March 06, 2002 7:45 PM >To: Ruben Fagundo >Cc: sbawa@tabmaster.com; samba@lists.samba.org >Subject: Re: [Samba] Strange Problem with Access > > >Ruben Fagundo wrote: > > > > >> > >> I set the following options up and I still seem to have the same > >> problem. Did I set the oplock setting correctly??? > > > >It looks right, as best as I can tell. > > >> I get the following error message, exactly from the win95 machines: > >> > >> "The Microsoft database engine stopped the process because you or > >> another user is attempting to change the same data at the same time." > > > > >Could it (possibly) be some other problem with the Access file itself? >(just speculating) > > >> > >> > >> The pertinent setting in smb.conf are as follows: > >> ==================================> >> [global] > >> > >> veto oplock files = /*.mdb/*.MDB/ > >> > >> [public] > >> locking = yes > >> oplocks = yes > >> veto oplock files = /*.dba/*.dbm/*.mdb/*.MDB/ > >> share modes = yes > >> strict locking = no > >> comment = Temporary file space > >> path = /home/apps/public > >> public = yes > >> writeable = yes > >> create mode = 0777 > >> directory mode = 0775 > > > >Doesn't Access use some other sort of file? .mde or something? >If you run "smbstatus" while Access is running, what kind of locks >does it show on the files? Check that out to see if it's working, and >if >you've got all the apropriate file patterns. >I would suggest two things (in order): >1. Try turning off oplocks altogether >2. Figure that I was wrong about the oplocks and look at other >possibilities. > >How much would it take to install MySQL and put the Access database >there? >MySQL works great with Access through the MyODBC driver. (I know this is >changing lanes without signalling, but I just thought I'd throw it out >there.) > >-Bill > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba
I posed the following problem a few weeks ago, and finally, I've had time
to update the RPM for the latest samba Version 2.2.3a
I added the following line to [global]
veto oplock files = /*.mdb/*.MDB/*.ldb/
And the following line to the directory having problems.
[public]
locking = yes
oplocks = yes
veto oplock files = /*.mdb/*.MDB/*.ldb/
I am still having problems opening the Access database from certain
computers. All other systems are working perfectly fine. There is no
correlation to the version of Windows opening the database. If anyone has
any more suggestions, I would really love to hear them. The orginial
problem description is listed below. And a more detailed log file is
attached. The file experiencing problems is called
"AWC Supporters.mdb"
The irony of all this is that this was all working perfectly fine with
Redhat 5.2
================================================
I am running samba on a RedHat 7.2 Athalon box with software RAID 0 dual
IDE disks on an ext3 filesystem.
I have several users in a large community of users that are always hitting
the samba server. The machine has been consistently reliable with one
exception. There is a particularly large MS Access Database (10Meg) that
everyone likes to use. A problem has developed from certain Win 98 and
Win95 computers where users get an error message saying that someone
currently has a lock on the database, and that it cannot be
opened. However, smbstatus, reports that the user is actually trying to
establish a lock on a different file, not the database in question. To add
to the strangeness, I have opened the database on a different computer, and
then all of a sudden everyone else can now open it as well. In addition to
that, I had the database open from a win 98 machine, and someone else (that
had been experiencing problems) opened it up, but smbstatus reports that
the 2nd individual had a second file open in addition to the database, and
clearly there were no other files open on that computer, by that user. So,
we have files opening and getting locked when they were not opened, and a
database that only certain users can open, cause other computers are being
told that it is already open, and locked by a different user.
Can anyone tell me what the heck is going on here, and what is the answer
to this apparent lunacy ???
Thanks,
Ruben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: volunteer.log.old.gz
Type: application/octet-stream
Size: 1488 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/20020408/d8b617d3/volunteer.log.old.obj
-------------- next part --------------