[Daisy] Problem starting the Daisy Repository Server
Jean Meyer
jean.meyer2 at mail.dcu.ie
Fri Jul 13 11:39:43 CDT 2007
Thank you Paul. As explained on http://cocoondev.org/kb/443-cd.html I
removed the write.lock file. Then it worked well. In the article it said
that the cause can be:
2. Daisy didn't shut down cleanly the last time it was stopped
Actually before restarting my computer I made sure I had stopped the
daisy wiki then the repo by using the two .bat .
Then I restarted my laptop. So I guess Daisy did shut down cleanly.
When my computer turned on again it started automatically the repo and
the wiki.
I figured that out by using the .bat to stop the wiki just after the
restart and it worked with *no *error message saying:
"the Daisy CMS WIKI Web Application has not started".
It was the same when I stopped the repo right after the wiki.
So I guess Windows starts automatically the two services when
restarting, and this nearly at the same time so the repo does not have
time to start properly before the wiki.
Once both are stopped and restarted again with enough time between the
repo start and the wiki start then it works well again without having to
delete the write.lock file.
Is there a way to prevent the automatic start of MySQL and the windows
services when turning on my computer ?
regards,
Jean
Paul Focke a écrit :
> 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
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/site/services/daisy/daisysupport.html
> mail to: daisy at lists.cocoondev.org
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
More information about the daisy
mailing list