innd: tradindexed: cannot lock index hash table: Resource temporarily unavailable

Russ Allbery rra at stanford.edu
Wed Jun 16 16:52:32 UTC 2004


James Wilde <james_wilde at glocalnet.com> writes:

> The whole of /news is an nfs mount.  Some groups are trad, some are
> cnfs.

This may be related to the problem that Alex discovered where locking
doesn't work if one is memory mapping the same file.  In general, we don't
recommend NFS-mounting the spool if you can possibly avoid it.

> I've tried moving the db directory to a local disk without success.
> Only innwatch starts.

Sounds like you didn't move it properly.  db wouldn't help anyway, though;
you need to move the spool/overview directory.

>> Note also that this error message is not fatal; innd will continue on
>> as normal even though it can't obtain a lock, on the grounds that the
>> chances of things going wrong are still somewhat remote.

> Believe me, it's fatal here!

Well, I'm sorry to contradict you, but INN simply does not contain any
code to do what you say that it's doing, so unless you've modified INN in
some way, I just don't see how this is possible.  Now, you may be getting
some *other* fatal error, and this is the one that's the noisiest in the
logs....

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.


More information about the inn-workers mailing list