Manuel Vazquez Acosta wrote at 2008-4-7 15:21 -0400:
Dieter Maurer wrote:
That is very strange:
"zopectl debug" uses almost exactly the same startup sequence as "zopectl fg" (at least until after the configuration). Thus, if your Zope starts at all, "zopectl debug" should start. ... zopectl fg starts. Would need to see the starting sequence?
Really funny.... Unfortunately, this means that is will be quite difficult to find the cause of your problem. One approach would be to emulate in a pure Python interpreter what "zopectl debug" would do for us. You may try: bin/zopectl shell # will create a new shell process with the correct environment <your_zope_python> from Zope2.Startup.run import configure configure('etc/zope.conf') # this is likely to raise the exception you have earlier reported from pdb import pm pm() # analyse the exception context -- Dieter