Re: Problems whem upgrading from 4.3.5 to 4.3.6

Eggert Ehmke <[email protected]> writes:

> Am Donnerstag, 18. Juni 2015, 08:06:11 schrieb Steve McMahon:
>> On Wed, Jun 17, 2015 at 2:46 PM, Eggert Ehmke <[email protected]>
>> 
>> wrote:
>> > Yes, what's more: when started via
>> > bin/instance fg
>> > it runs fine, no restarts.
>> 
>> A nearly sure sign that your problem is with permissions and ownerships.
>> When running in "fg" there is no need to write our a pid file. Check your
>> ownership and permissions in ./var. The daemon process must be able to
>> write out its pid and log files.
>
> All directories in var have
> drwxrws--- 4 plone_daemon plone_group
> All files have
> -rw-r--r-- 1 plone_daemon plone_group
>
> Beside of thus, the pid file is written, even when running in fg. Also the log 
> file instance log is written, but gives no clue other then what stated in the 
> first post.

Nevertheless, your observations indicate some problem with the
"zdaemon <-> zope" communication.

When I remember right, the "zdaemon" sends a "SIGTERM" to the controlled
"zope" process when it does not receive a startup answer within some
time limit and then tries to start the "zope" process again.
I had to increase this timeout in a case where opening a large
number of large ZODB storages took too much time - as the "zope" process
did not complete its startup sufficiently fast.

When I remember right, "zdaemon" allows to specify a logfile of its
own. You may try this to get information about "zdaemon"s observations
about the "zope" process.


--
Dieter



------------------------------------------------------------------------------