[distcc] Locking Problem with distcc

[Martin Pool]

On 24 Mar 2004, Ralf Beckers <ralf.beckers at chipvision.com> wrote:
> Dear Martin,
> 
> On Wednesday 24 March 2004 00:24, Martin Pool wrote:
> > > > The following is a typical error message:
> > > > distcc[2620] (dcc_lock_host) ERROR: lock
> > > > /home/wolframl/.distcc/lock/cpu_localhost_0 failed: No locks available
> > > > distcc[2620] (dcc_lock_one) ERROR: failed to lock
> > > > Where do I have to look, to find the problem?
> > > What platform are you on, what version, etc etc.
> > Also, are you using NFS?
> > This error seems to mean that either locking is not working on the
> > DISTCC_DIR filesystem, or you have exhausted your system's lock
> > resources.
> 
> I am using NFS mounted home partitions.
> 
> distcc: distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2)
> compiler: gcc 3.3 (selfbuild, language support for c, c++, works when using 
> standalone)
> platform: suse linux 8.2, kde 3.1.1
> problems building an own program (same software versions work on non nfs 
> desktops, we are all using the same image as sw installation)
> 
> I checked the permissions on /home/wolframl/.distcc/lock/ and the user has the 
> correct rights for writing, ... but this partition is on nfs. What further 
> information do w need to localize this error?

Perhaps NFS lockd is either not running or broken?

Given recent problems it might be simplest to set DISTCC_DIR to
somewhere not on NFS.  tmpfs would be fine.

-- 
Martin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/distcc/attachments/20040324/a249ef1d/attachment.bin