I have a Plone instance that was working 'just fine' that now won't start. When I run "bin/plonectl start" the zeoserver line takes longer than normal, and claims then to start (but it doesn't really). The two clients start as normal. If I look at the open ports on my Ubuntu system ("sudo netstat -plntu") I can see that there is no open port for the zeoserver (8100) while the two clients are listening. A sample from the end of zeoserver.log:
2009-08-02T21:58:38 spawned process pid=7525
2009-08-02T21:58:38 (7525) created PID file '/home/locallywired/Plone/zeocluster/var/zeoserver/zeoserver.pid'
2009-08-02T21:58:38 (7525) opening storage '1' using FileStorage
2009-08-02T21:58:38 (7525) removed PID file
'/home/locallywired/Plone/zeocluster/var/zeoserver/zeoserver.pid'
2009-08-02T21:58:38 sleep 9 to avoid rapid restarts
2009-08-02T21:58:38 pid 7525: exit
status 1
2009-08-02T21:58:48 spawned process pid=7526
2009-08-02T21:58:48 (7526) created PID file '/home/locallywired/Plone/zeocluster/var/zeoserver/zeoserver.pid'
2009-08-02T21:58:48 (7526) opening storage '1' using FileStorage
2009-08-02T21:58:48 (7526) removed PID file '/home/locallywired/Plone/zeocluster/var/zeoserver/zeoserver.pid'
2009-08-02T21:58:48 restarting too frequently; quit
The other plone instance on the server starts and behaves OK.
I have:
- rerun buildout; run buildout -n
- Updated Plone to 3.3rc4 with buildout
- Rebooted a few times
- tried changing zeoserver's port
As far as I know I haven't changed anything, so I am mystified.
Any further debugging clues (or reason)?
Regards,
Barry
Page