how to get more verbose logging
hello, at trying to debug a problem that causes zope to crash, a more verbose logging would be very usefull. I already use the event.log, but up to now i had EVENT_LOG_SEVERITY at -100 (BLATHER), what worked quite well. now i raised the environment variable to -300, in the hope to get TRACE logging, as mentioned in the Zope 2.6 documentation. anyway, event.log still doesn't give logs lower than BLATHER. I'm not absolutely sure whether it should, but normally TRACE should already give some more information at starting the process, shouldn't it. even if i produce the problem that crashes zope, the lowest log is BLATHER, and i get no more verbose logging output. i tested this in zope 2.6.4 with python2.1 and python2.2, and both don't provide any new information. any suggestions? bye jonas
On Wed, Nov 10, 2004 at 05:43:06PM +0100, Jonas Meurer wrote:
hello,
at trying to debug a problem that causes zope to crash, a more verbose logging would be very usefull. I already use the event.log, but up to now i had EVENT_LOG_SEVERITY at -100 (BLATHER), what worked quite well.
now i raised the environment variable to -300, in the hope to get TRACE logging, as mentioned in the Zope 2.6 documentation.
anyway, event.log still doesn't give logs lower than BLATHER. I'm not absolutely sure whether it should, but normally TRACE should already give some more information at starting the process, shouldn't it.
even if i produce the problem that crashes zope, the lowest log is BLATHER, and i get no more verbose logging output.
i tested this in zope 2.6.4 with python2.1 and python2.2, and both don't provide any new information.
any suggestions?
You could try raising the logger level to "ALL" in the logger sections of instance/etc/zope.conf. You might also try turning on the trace logger. The trace logger section was commented out in etc/zope.conf by default in my instance. Dave -- Dave Kuhlman http://www.rexx.com/~dkuhlman
On 10/11/2004 Dave Kuhlman wrote:
You could try raising the logger level to "ALL" in the logger sections of instance/etc/zope.conf.
You might also try turning on the trace logger. The trace logger section was commented out in etc/zope.conf by default in my instance.
hello, i guess that you talk about features introduced in zope2.7, but zope2.6 has no zope.conf and AFAIK not even a trace logger. zope 2.6.4 supports only the event log (stupid log), with different severityies: -300 TRACE; -200 DEBUG; -100 BLATHER; 0 INFO; 100 PROBLEM ... i don't know whether zope accespts the severity keyworks in EVENT_LOG_SEVERITY, but i'll try EVENT_LOG_SEVERITY="TRACE" tomorrow. bye jonas
On Thu, Nov 11, 2004 at 12:28:59AM +0100, Jonas Meurer wrote:
i guess that you talk about features introduced in zope2.7, but zope2.6 has no zope.conf and AFAIK not even a trace logger.
It does. We used to call it the debug log, or the "big M" log. You turn it on with the -M command line flag for z2.py. -- Paul Winkler http://www.slinkp.com
On 10/11/2004 Paul Winkler wrote:
On Thu, Nov 11, 2004 at 12:28:59AM +0100, Jonas Meurer wrote:
i guess that you talk about features introduced in zope2.7, but zope2.6 has no zope.conf and AFAIK not even a trace logger.
It does. We used to call it the debug log, or the "big M" log. You turn it on with the -M command line flag for z2.py.
really? i thought that -M command line flag is for detailed log, which included quite more information than default Z2.log, but still not as much as event.log includes. am i wrong? bye jonas
On Sun, Nov 14, 2004 at 04:46:28AM +0100, Jonas Meurer wrote:
On 10/11/2004 Paul Winkler wrote:
On Thu, Nov 11, 2004 at 12:28:59AM +0100, Jonas Meurer wrote:
i guess that you talk about features introduced in zope2.7, but zope2.6 has no zope.conf and AFAIK not even a trace logger.
It does. We used to call it the debug log, or the "big M" log. You turn it on with the -M command line flag for z2.py.
really? i thought that -M command line flag is for detailed log, which included quite more information than default Z2.log, but still not as much as event.log includes.
That is exactly what the trace log is. The -M flag for zope 2.6 or lower turns on exactly the same log that is enabled by the <logger trace> section of zope.conf in 2.7 or higher. The format of this log is described in the docstring of lib/python/ZServer/DebugLogger.py. -- Paul Winkler http://www.slinkp.com
Hmmm. Zope 2.7.3 apparently requires that products install without error. ZSyncer 0.6 raises an exception when it does not find CMF installed which apparently kills the installation. Is there a good way to proceed without doing surgery on the code? If surgery is needed, what's the way to stay compatible with future releases.
On Sun, Nov 14, 2004 at 12:11:49PM -0800, Dennis Allison wrote:
Hmmm.
Zope 2.7.3 apparently requires that products install without error. ZSyncer 0.6 raises an exception when it does not find CMF installed which apparently kills the installation.
No, ZSyncer tries to import some CMF stuff and if it's not present, goes merrily on its way and does not import ZSyncerTool.py. 0.6 is fine without CMF installed. I am guessing that you had CMF installed but removed it. In that case, removing *pyc in your ZSyncer directory should fix the problem. Maybe I should add a note about this in README. -- Paul Winkler http://www.slinkp.com
participants (4)
-
Dave Kuhlman -
Dennis Allison -
Jonas Meurer -
Paul Winkler