[ZCM] [ZC] 1285/ 3 Comment "[Weakness] analysis of Zope startup problems"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1285 Update (Comment) "[Weakness] analysis of Zope startup problems"
 Status Accepted, Zope/bug medium
To followup, visit:
  http://zope.org/Collectors/Zope/1285

==============================================================
= Comment - Entry #3 by ajung on May 12, 2004 10:57 am

Can we have a fix for this issue before 2.7.1 beta?
________________________________________
= Assign - Entry #2 by fdrake on Apr 30, 2004 11:14 am

 Status: Pending => Accepted

 Supporters added: fdrake

Assigned to myself since I've had my hand in startup logging recently.
________________________________________
= Request - Entry #1 by d.maurer on Apr 2, 2004 3:32 am

Zope 2.7 delays access to log files until Zope is properly set up.
This means: log files cannot be used to analyse startup problems.

The official advice to analyse startup problems is to start
Zope in the foreground and interpret the console log messages.

However, this does *NOT* work when Zope is not running in
debug mode. "Zope.Startup.ZopeStarter.setupStartupHandler"
expressly suppresses messages to "stderr" when Zope
is not running in debug mode.

Apparently, we do not have an easy way to analyse startup problems
for Zope in production mode.
In my view, this is really bad.


Please provide a way to control how startup messages should
be handled. The best place would be a file (at least for
all installations that do not start Zope as root and later
switch the effective user).

I suggest to always use the standard log file unless
told otherwise by an explicit configuration option.

==============================================================