Plone on linux keeps dying

[M Singh]

Weird problem.

I developed a website using the latest version of plone, on mac osx.

Now, to give my team a chance to give me feedback, I deployed it on our linux server.

The problem :

me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl start
instance: . . daemon process started, pid=8854
me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
instance: program running; pid=8857
me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
instance: program running; pid=8860
me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
instance: program running; pid=8864
me@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.

/usr/local/Plone/zinstance/var/log/

is empty.

me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl debug
instance: Starting debugger (the name "app" is bound to the top-level Zope object)
2009-08-03 23:25:25 WARNING PlacelessTranslationService Error while compiling /usr/local/Plone/Zope-2.10.7-final-py2.4/lib/python/zope/app/locales/zh_CN/LC_MESSAGES/zope.po

>>> logtail
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
NameError: name 'logtail' is not defined
>>>

The same happens whether I install plone as a user, or as root.

Unsurprisingly, I cannot browse to http://server:8080/manage.

Apache is configured to listen to port 8080 as well.

[cewing]

M Singh wrote:

me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl start
instance: . . daemon process started, pid=8854
me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
instance: program running; pid=8857
me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
instance: program running; pid=8860
me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
instance: program running; pid=8864
me@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

[barrypage]

Some javascript/style in this post has been disabled (why?)

I had that myself the other day. I had started a Plone instance as root user (sudo) through an init.d startup script, then it failed to restart again at the Data.fs.lock file was owned by root. I changed permissions on everything in the filesystem folder, and then was able to start the cluster again.

 

Regards,
Barry Page
021 438 695

Community websites online at greenhithe.org.nz, albanynz.com and paremoremo.com. Find out more at locallywired.com.

---

From: cewing <[hidden email]>
To: [hidden email]
Sent: Wednesday, 5 August, 2009 3:32:10 AM
Subject: Re: [Setup] Plone on linux keeps dying



M Singh wrote:

>
> me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl start
> instance: . . daemon process started, pid=8854
> me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
> instance: program running; pid=8857
> me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
> instance: program running; pid=8860
> me@server:~$ sudo /usr/local/Plone/zinstance/bin/plonectl status
> instance: program running; pid=8864
> me@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.

_______________________________________________
Setup mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/setup

_______________________________________________
Setup mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/setup