[Setup] Plone on linux keeps dying

cewing cewing at u.washington.edu
Tue Aug 4 15:32:10 UTC 2009



M Singh wrote:
> 
> me at server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl start
> instance: . . daemon process started, pid=8854
> me at server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
> instance: program running; pid=8857
> me at server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
> instance: program running; pid=8860
> me at server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
> instance: program running; pid=8864
> me at server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
> instance: daemon manager running; daemon process not running
> 
> Classic case of a process respawning until it finally gives up.
> 
I've seen this type of behavior on servers where I have failed to set
permissions on the file system correctly.  If plone/zope are running as a
particular user, that user needs to have read/write access to files like the
z2 log, the Data.fs file and so on.  If it hasn't got the correct
permissions, the process will respawn about nine or ten times and then just
give up and fail.  This sounds a lot like the trouble you're seeing here.  

I run buildout-based instances, and in my case, the plone/zope user needs to
have rw to the 'var' directory of the buildout.  Check this first.


M Singh wrote:
> 
> Apache is configured to listen to port 8080 as well.
> 
I may be wrong here, but if zope cannot open a port because something else
is already listening there, it will fail.  This usually gives an error
message, though, so it seems likely that your process isn't even getting as
far as attempting to open the port.

HTH

c
-- 
View this message in context: http://n2.nabble.com/Plone-on-linux-keeps-dying-tp3382805p3385258.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.



More information about the Setup mailing list