[Daisy] Problem starting the Daisy Repository Server
Paul Focke
paul at outerthought.org
Fri Jul 13 01:06:42 CDT 2007
On Thu, 2007-07-12 at 19:45 +0100, Jean Meyer wrote:
> Hi all,
>
> I have installed Daisy on my laptop. It works well, I can go on
> http://localhost:8888/. I have installed the Windows services to start
> and stop the Daisy Repository Server and the Daisy Wiki. They all work
> well. Then I have restarted my computer and I have tried to start the
> repository server without success.
>
> As explained on
> http://cocoondev.org/daisydocs-2_0/admin/service/329-cd.html I tried
> this command:
>
> C:\>cd C:\daisydata\service
> C:\daisydata\service>daisy-repository-server-service.bat
>
> I got this message:
>
> wrapper | --> Wrapper Started as Console
> wrapper | Launching a JVM...
> jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
> jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights
> Reserved.
> jvm 1 |
> jvm 1 | ---- exception report
> ----------------------------------------------------------
> jvm 1 | Exception: org.apache.avalon.merlin.KernelException
> jvm 1 | Message: Kernel startup failure.
> jvm 1 | ---- cause
> ---------------------------------------------------------------------
> jvm 1 | Exception: org.apache.avalon.merlin.KernelException
> jvm 1 | Message: Cannot deploy application.
> jvm 1 | ---- cause
> ---------------------------------------------------------------------
> jvm 1 | Exception: org.apache.avalon.activation.LifecycleException
> jvm 1 | Message: Unable to create a new component instance in
> appliance [/daisy/repository/fullTextIndex] due to a component
> deployment failure.
> jvm 1 | ---- cause
> ---------------------------------------------------------------------
> jvm 1 | Exception: java.io.IOException
> jvm 1 | Message: Lock obtain timed out:
> SimpleFSLock at C:\daisydata\indexstore\write.lock
> jvm 1 | ---- stack trace
> ---------------------------------------------------------------
> jvm 1 | java.io.IOException: Lock obtain timed out:
> SimpleFSLock at C:\daisydata\indexstore\write.lock
> jvm 1 | org.apache.lucene.store.Lock.obtain(Lock.java:69)
> jvm 1 |
> org.apache.lucene.index.IndexWriter.init(IndexWriter.java:367)
> jvm 1 |
> org.apache.lucene.index.IndexWriter.init(IndexWriter.java:352)
> jvm 1 |
> org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:314)
> jvm 1 |
> org.outerj.daisy.ftindex.FullTextIndexImpl.constructIndexWriter(FullTextIndexImpl.java:307)
> jvm 1 |
> org.outerj.daisy.ftindex.FullTextIndexImpl.updateWriter(FullTextIndexImpl.java:303)
> jvm 1 |
> org.outerj.daisy.ftindex.FullTextIndexImpl.initialize(FullTextIndexImpl.java:109)
> jvm 1 |
> org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
> jvm 1 |
> org.apache.avalon.activation.impl.DefaultComponentFactory.incarnation(DefaultComponentFactory.java:402)
> jvm 1 |
> org.apache.avalon.activation.impl.DefaultComponentFactory.incarnate(DefaultComponentFactory.java:130)
> jvm 1 |
> org.apache.avalon.activation.impl.SingletonLifestyleManager.refreshReference(SingletonLifestyleManager.java:144)
> jvm 1 |
> org.apache.avalon.activation.impl.SingletonLifestyleManager.commission(SingletonLifestyleManager.java:60)
> jvm 1 |
> org.apache.avalon.activation.impl.DefaultAppliance.commission(DefaultAppliance.java:94)
> jvm 1 |
> org.apache.avalon.activation.impl.DefaultRuntime.commission(DefaultRuntime.java:86)
> jvm 1 |
> org.apache.avalon.composition.model.impl.DefaultSystemContext.commission(DefaultSystemContext.java:362)
> jvm 1 |
> org.apache.avalon.composition.model.impl.DefaultDeploymentModel.commission(DefaultDeploymentModel.java:122)
> jvm 1 |
> org.apache.avalon.composition.model.impl.Commissioner.run(Commissioner.java:185)
> jvm 1 | java.lang.Thread.run(Thread.java:619)
> jvm 1 |
> --------------------------------------------------------------------------------
> jvm 1 |
> wrapper | <-- Wrapper Stopped
>
>
> Does anybody know a solution for this problem ?
Have a look here for information on the write.lock
http://cocoondev.org/kb/443-cd.html
This occurs when the repository hasn't been shut down cleanly. In the
next daisy release this won't produce an exception but will release the
lock and show a warning instead.
Paul
More information about the daisy
mailing list