My plone site died today and I can't get it running again. I have located the following entries in my logs: In /var/log/messages: zopectl: Unlinking stale socket /var/lob/zope-2.7.2/main/var/zopectlsock; sleep 1 zopectl: . After each restart attempt: zopectl: daemon process started, pid=xxxx "14 seconds later" zopectl: daemon manager not running event.log: I'm getting ZODB conflict errors When the zopectlsock dies it leaves Z2.pid and Z2.lock but no corresponding process is running. I've checked around the web and can't find any solutions. Hopefully someone here can help? Thanks Michael -- Michael Williams Haywood County Schools Technology Director Instructional Technology http://www.haywood.k12.nc.us (828) 627-8314
Michael Williams wrote:
My plone site died today and I can't get it running again. I have located the following entries in my logs:
In /var/log/messages: zopectl: Unlinking stale socket /var/lob/zope-2.7.2/main/var/zopectlsock; sleep 1 zopectl: .
After each restart attempt:
zopectl: daemon process started, pid=xxxx "14 seconds later" zopectl: daemon manager not running
event.log:
I'm getting ZODB conflict errors
When the zopectlsock dies it leaves Z2.pid and Z2.lock but no corresponding process is running.
I've checked around the web and can't find any solutions. Hopefully someone here can help?
Thanks Michael
Are you sure Zope is not still running in the background? Try killall -9 python an then restart zope again Robert
Michael Williams wrote at 2005-1-26 20:32 -0500:
My plone site died today and I can't get it running again. I have located the following entries in my logs:
In /var/log/messages: zopectl: Unlinking stale socket /var/lob/zope-2.7.2/main/var/zopectlsock; sleep 1 zopectl: .
After each restart attempt:
zopectl: daemon process started, pid=xxxx "14 seconds later" zopectl: daemon manager not running
A typical startup problem. Due to a Zope bug (unfortunately not recognized by the maintainers), startup problems are very difficult to analyse. If your Zope run in debug mode (no "debug-mode off" in your configuration file), you can use "zopectl fg" to start it in the foreground. Then you should see why Zope cannot start on the screen. -- Dieter
On Thu, 2005-01-27 at 13:43, Dieter Maurer wrote:
Michael Williams wrote at 2005-1-26 20:32 -0500:
My plone site died today and I can't get it running again. I have located the following entries in my logs:
In /var/log/messages: zopectl: Unlinking stale socket /var/lob/zope-2.7.2/main/var/zopectlsock; sleep 1 zopectl: .
After each restart attempt:
zopectl: daemon process started, pid=xxxx "14 seconds later" zopectl: daemon manager not running
A typical startup problem.
Due to a Zope bug (unfortunately not recognized by the maintainers), startup problems are very difficult to analyse.
If your Zope run in debug mode (no "debug-mode off" in your configuration file), you can use "zopectl fg" to start it in the foreground. Then you should see why Zope cannot start on the screen.
bin/runzope does the same thing, FWIW. - C
participants (4)
-
Chris McDonough -
Dieter Maurer -
Michael Williams -
robert