Zope has failed to restart after I attempted to upgrade CMF and Plone. How do I tell what has gone wrong? In zope.debug.log there is a msg:- ImportError: No module named 105 I guess that may have something to do with Plone 1.0.5 which no longer exists... -- John
John Poltorak wrote:
Zope has failed to restart after I attempted to upgrade CMF and Plone.
How do I tell what has gone wrong?
In zope.debug.log there is a msg:-
ImportError: No module named 105
I guess that may have something to do with Plone 1.0.5 which no longer exists...
Under Linux start Zope with with Debug set to on. This is done by adding -D to the set of parameters when Zope is started. Under Windows use the start.bat in Zopes home directory in a dos shell. Zope will then not detach itself from the Terminal from which it was started and you can see what error messages are issued. You probably do not have all products installed that need to be installed. Robert
John Poltorak wrote at 2004-2-29 16:42 +0000:
Zope has failed to restart after I attempted to upgrade CMF and Plone.
How do I tell what has gone wrong?
In zope.debug.log there is a msg:-
ImportError: No module named 105
I guess that may have something to do with Plone 1.0.5 which no longer exists...
Unlikely. "105" is no legal module name. I expect "zope.debug.log" is Zope's logfile. In this case, you should see a traceback below the "ImportError". It is essential. I think, I already told you: Tracebacks are *vital* for problem analysis! *ALWAYS* include them in your problem reports... -- Dieter
participants (3)
-
Dieter Maurer -
John Poltorak -
robert rottermann