Hello,

We have a relatively new installation of vibe that worked for a few days but now when we access vibe we see the following error:

Error
(kablink) Could not open index writer

Looking at the tomcat log it appears to be a problem with the lucene lock file:

Aug 22, 2012 5:51:11 PM org.apache.catalina.core.ApplicationContext log
SEVERE: Exception while dispatching incoming RPC call
Throwable occurred: com.google.gwt.user.server.rpc.UnexpectedException : Service method 'public abstract org.kablink.teaming.gwt.client.rpc.shared.VibeRpcR esponse org.kablink.teaming.gwt.client.service.GwtRpcServi ce.executeCommand(org.kablink.teaming.gwt.client.u til.HttpRequestInfo,org.kablink.teaming.gwt.client .rpc.shared.VibeRpcCmd) throws org.kablink.teaming.gwt.client.GwtTeamingException ' threw an unexpected exception: org.kablink.teaming.lucene.LuceneException: (kablink) Could not open index writer / org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/var/opt/novell/teaming...ink/write.lock

...

Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/var/opt/novell/teaming...ink/write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:85)
at org.apache.lucene.index.IndexWriter.init(IndexWrit er.java:1545)
at org.apache.lucene.index.IndexWriter.<init>(IndexWr iter.java:1074)
at org.kablink.teaming.lucene.LuceneProvider.openInde xWriter(LuceneProvider.java:195)
at org.kablink.teaming.lucene.LuceneProvider.openInde xingResource(LuceneProvider.java:338)
... 77 more

Stopping vibe, deleting "write.lock" and restarting vibe doesn't fix the issue. google finds lot of hits for this error when running lucene and solr but vibe doesn't use solr to my knowlege and none of the fixes I found were applicable to a vibe install. Has anyone else encountered this problem?

TIA

Keith.