扩展失败后,克隆重新启动.如何发现错误 [英] Plone restart after buildout fails. How to find the error

查看:123
本文介绍了扩展失败后,克隆重新启动.如何发现错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

最近,我一直在尝试通过buildout.cfg的eggs部分添加有用的插件,运行buildout并重新启动zeocluster plonectl restart来自定义Plone. 我已经以这种方式成功安装了几个插件. 但是有些阻止了Plone的工作.例如,尝试添加plone.app.ldap: buildout可以正常工作,并且服务器的重新启动最初也可以,但是在浏览器中访问Plone时,它不会加载,并且plonectl status告诉我我的两个客户端已断开与zeoserver的连接.事件日志讲述的是同一故事,但除此之外,我看不到是哪个错误导致了问题.当我删除插件时,一切恢复正常.

lately I have been trying to customize my Plone by adding helpful addons via the eggs section of my buildout.cfg, running buildout and restarting the zeocluster plonectl restart. I have succesfully installed several addons this way. But some stop Plone from working. For example trying to add plone.app.ldap: buildout works fine and also the restart of the server works initially, but when accessing Plone in the browser it doesn't load and plonectl status tells me my two clients have lost connection to the zeoserver. The events log tells the same story, but other than that I do not see which error caused the problem. When i remove the addon everything works fine again.

我处理插件的方式正确吗?我错过了什么?在哪里可以找到其他信息,使zeocluster崩溃?

Is the way I am handling my addons correct? Did I miss something? Where can I find additional information what crashes my zeocluster?

推荐答案

启动时会吞下一些问题.您可以通过使用bin/zeoclient fg在前台启动客户端来查看它们. 请参见 http://docs.plone.org/manage/troubleshooting/basic.html 注意:zeoclient脚本可以称为client,client1或instance或类似名称,具体取决于其在构建物中的命名方式.

Some problems are swallowed on startup. You can see them by starting your client on the foreground with bin/zeoclient fg. See http://docs.plone.org/manage/troubleshooting/basic.html Note: the zeoclient script may be called client, or client1 or instance or something like that, depending on how it is named in the buildout.

这可能会显示Python回溯.也许加载项缺少依赖项.向附件作者报告这将是一个问题.将丢失的依赖项添加到鸡蛋中会添加重新运行的构建,应该可以解决此问题.

This will probably show a Python traceback. Maybe the add-on is missing a dependency. That would be a problem to report to the add-on authors. Adding the missing dependency to the eggs add rerunning buildout should fix the problem.

这篇关于扩展失败后,克隆重新启动.如何发现错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆