Nuxeo mailing list archives
[Nuxeo-tickets] Re: [Nuxeo Repository] #1857: After a wild machine
shutdown NXLucene doesn't restart at the next machine reboot
Nuxeo Repository
trac at nuxeo.com
Fri Apr 25 21:03:56 CEST 2008
#1857: After a wild machine shutdown NXLucene doesn't restart at the next machine
reboot
----------------------+-----------------------------------------------------
Reporter: madarche | Owner: madarche
Type: defect | Status: new
Priority: P1 | Milestone: CPS 3.4.7
Component: Lucene | Version: TRUNK
Severity: normal | Resolution:
Keywords: |
----------------------+-----------------------------------------------------
Comment (by rspivak):
I should have elaborated. I did testing on my local instance and I didn't
meet any troubles with starting NXLucene even after manual kill -9. Stale
PID file was removed on next nxlucened startup automatically by twisted
sever.
Earlier I met some issues with starting up after abrupt stop of nxlucene
when /tmp folder contained cpslucene's lock file, but it happened only
when nxlucene was in process of indexing catalog and was abruptly stopped.
After that I had to remove stale lock file manually for proper nxlucene
startup.
Currently I'm using NXLucene trunk and Twisted-2.2.0.
Can you check, please, your version of twistd server. You should be able
to find out that in file {{{__init__.py}}} in your python's twisted
directory under site-packages/twisted.
In my case twistd.py file in site-packages/twisted/scripts/twistd.py
contains text:
{{{ log.msg('Removing stale pidfile %s' % pidfile, isError=True) }}}
And related part of the code actually removes stale pid file and allows to
start nxlucene correctly.
--
Ticket URL: <https://svn.nuxeo.org/trac/pub/ticket/1857#comment:5>
Nuxeo Repository <http://www.cps-project.org/>
Nuxeo Repository
This list archive provided by Nuxeo, the
leaders of open source ECM.
Check out the Nuxeo 5 open source,
standards-based ECM project.