克隆bin/instance启动和bin/instance重新启动有时会失败 [英] Plone bin/instance start and bin/instance restart fail sometimes

问题描述

有时候，Plone站点的bin/instance启动失败.症状

• 该网站已经运行了一段时间，没有任何维护

• 一个运行扩展:bin/buildout

• 有人尝试使用bin/instance start或bin/instance restart

重新启动站点

• 该站点无法启动.什么都没有记录到控制台.

• 但是，如果您先运行bin/instance fg，则站点确实会启动

这会影响Plone 3.x和Plone 4.x网站.

下面是该过程进行过程的示例.您可以看到，尽管提供了重新启动和启动，该站点并没有真正启动，但最终出现了fg:

*************** /PICKED VERSIONS ***************
xxx@yyy:/srv/plone/zzz$ bin/instance restart
.
daemon process restarted, pid=27819
xxx@yyy:/srv/plone/zzz$ bin/instance start

daemon process started, pid=27945
xxx@yyy:/srv/plone/zzz$ bin/instance status
daemon manager not running
xxx@yyy:/srv/plone/zzz$ bin/instance fg
2013-03-08 04:18:11 INFO ZServer HTTP server started at Fri Mar  8 04:18:11 2013
    Hostname: 0.0.0.0
    Port: xxxx

从日志文件看来，它已经达到了Zope的开始.尽管bin/instance状态或上游前端代理服务器都不同意.您会在日志中看到这一点.

 2013-03-08T04:19:21 INFO Zope Ready to handle requests

有什么想法可以进一步调试吗?

这可能是某种竞争状况/启动缓慢的问题吗?

可能是该进程在Ready to handle

之后无声地死掉了

其他人也观察到相同的行为吗?

解决方案

如果bin/buildout重建实例，那么它还将删除并重建parts/instance目录.

该目录包含一些导致bin/instance restart 失败的项目；用于重新启动的守护进程本身不再完成.

您需要使用bin/instance stop停止实例和的守护进程，然后是bin/instance start(这将创建一个新的新守护进程).

Sometimes it looks like bin/instance start fails for a Plone site. Symptoms

• The site has been running for a while without maintenance

• One runs buildout: bin/buildout

• One tries to restart the site using bin/instance start or bin/instance restart

• The site doesn't start. Nothing is logged to console.

• However, if you run bin/instance fg first the site does start

This affects both Plone 3.x and Plone 4.x sites.

Below is a sample how the process goes. You can see that the site doesn't really start despite of giving restart and start, but finally comes up with fg:

*************** /PICKED VERSIONS ***************
xxx@yyy:/srv/plone/zzz$ bin/instance restart
.
daemon process restarted, pid=27819
xxx@yyy:/srv/plone/zzz$ bin/instance start

daemon process started, pid=27945
xxx@yyy:/srv/plone/zzz$ bin/instance status
daemon manager not running
xxx@yyy:/srv/plone/zzz$ bin/instance fg
2013-03-08 04:18:11 INFO ZServer HTTP server started at Fri Mar  8 04:18:11 2013
    Hostname: 0.0.0.0
    Port: xxxx

From log file it looks like it has reached the Zope start. Though both bin/instance status or upstream front end proxy server disagree. You see this in the logs.

 2013-03-08T04:19:21 INFO Zope Ready to handle requests

Any ideas how to debug this further?

Could it be some sort of race condition / slow start up issue?

Could it be that the process silently dies after Ready to handle

Have other people obeserved the same behavior?

解决方案

If bin/buildout rebuilds the instance, then it'll also remove and re-build the parts/instance directory.

It's that directory that holds a few items that make a bin/instance restart fail; the daemon process that manages the restart is itself no longer complete.

You need to use bin/instance stop to stop the instance and the daemonizing process, followed by a bin/instance start (which creates a fresh new daemon process).

这篇关于克隆bin/instance启动和bin/instance重新启动有时会失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！