[KinoSearch] Couldn't get lock

Jesse Erlbaum jesse at erlbaum.net
Mon Jun 18 07:12:51 PDT 2007


Hi All --
 
We've been rolling out a Kinosearch-based site search engine, and
periodically get the following error:
 
    Couldn't get lock using
'/tmp/kinosearch_lockdir/kinosearch-677654d74548827b32ec1abc555b92a7-com
mit.lock' at /path/to/lib/i686-linux/KinoSearch/Store/Lock.pm line 28
 
When I look in /tmp I see nothing.  The directory "kinosearch_lockdir"
does not exist.  What's going on here?  Is there a way to set the lock
directory?  Is there a way to tell Kino to create the directory if it is
missing?
 
This error causes the Search engine to periodically crash with an
Internal Server Error.
 
FYI, I don't know if it is important, but we build the index on one
machine and the front-end search runs on another.  (The index directory
is NFS mounted, and UNIX user ids are in sync.  The "/tmp" directory is
*not* shared between machines.)
 
Thanks,
 
-Jesse-
 
 
Jesse Erlbaum
The Erlbaum Group, LLC
817 Broadway, 10th floor
New York, NY 10003
212-684-6161 (office)
917-647-3059 (mobile)
212-684-6226 (fax)
jesse at erlbaum.net <blocked::mailto:jesse at erlbaum.net> 
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.rectangular.com/pipermail/kinosearch/attachments/20070618/b9287fd8/attachment.htm


More information about the kinosearch mailing list