Plone 4.3.x refusing to restart successfully after installation

[AshRaghav]

Hi,

I am not sure if anyone else had this issue but I have the following instance
Plone 4.3.3 (4308)
CMF 2.2.7
Zope 2.13.22
Python 2.7.6 (default, Jun 2 2016, 08:31:24) [GCC 4.8.4]
PIL 2.3.0 (Pillow)

And after installing rer.cookiecutter, the server is refusing to start. I had to manually pull plone.api, collective.jsconfiguration-0.1.1, collective.regjsonify-0.2.0 and decorator-4.2.1.

Buildout appeared to complete successfully but it didn't turnout to be successful with restarting though.

Can you please provide some input as what I might be doing wrong here? Thanks

[cekk]

What's the instance output? Can you paste here the error that you have?

[AshRaghav]

Hi, Sorry for the delay. I didn't get any error message unfortunately. It is just the Plone server will disconnect from ZODB repeatedly.

2018-05-24T23:07:50 INFO ZServer HTTP server started at Thu May 24 23:07:59 2018
	Hostname: localhost
	Port: xxxxx
------
2018-05-24T23:07:52 INFO Products.PloneFormGen gpg_subprocess initialized, using /usr/bin/gpg
------
2018-05-24T23:07:52 INFO ZEO.ClientStorage zeostorage ClientStorage (pid=xxxxx) created RW/normal for storage: '1'
------
2018-05-24T23:07:52 INFO ZEO.cache created temporary cache file '<fdopen>'
------
2018-05-24T23:07:52 INFO ZEO.ClientStorage zeostorage Testing connection <ManagedClientConnection ('127.0.0.1', xxxxx)>
------
2018-05-24T23:07:52 INFO ZEO.zrpc.Connection(C) (127.0.0.1:xxxxx) received handshake 'Z3101'
------
2018-05-24T23:07:52 INFO ZEO.ClientStorage zeostorage Server authentication protocol None
------
2018-05-24T23:07:52 INFO ZEO.ClientStorage zeostorage Connected to storage: ('localhost', xxxxx)
------
2018-05-24T23:07:52 INFO ZEO.ClientStorage zeostorage No verification necessary -- empty cache
------
2018-05-24T23:07:55 INFO ZEO.ClientStorage zeostorage Disconnected from storage: "('localhost', xxxxx)"

I am only unsure about decorator package as I am not sure if I got the right one.

Any help is appreciated.

[cekk]

Are you starting the instance manually or with supervisor? If you try to start the instance in foreground, you should see exactly where is the error:

./bin/instance fg