Re: [Zope-dev] [Weakness] analysis of Zope startup problems
Dieter, Is this improved at all by Fred's latest zZLOG-removal checkins? If not, I will open a collector issue. - C On Fri, 2004-04-02 at 03:34, Dieter Maurer wrote: 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. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Weakness] analysis of Zope startup problems
Oops, nevermind, I see you already did add a collector issue. On Fri, 2004-04-02 at 03:34, Dieter Maurer wrote: 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. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Weakness] analysis of Zope startup problems
On Friday 30 April 2004 10:50 am, Chris McDonough wrote: Is this improved at all by Fred's latest zZLOG-removal checkins? If not, I will open a collector issue. None of my changes have been applied to Zope 2.7; they only exist on the Zope 2 HEAD. The removal of zLOG is only for the Zope 3 and ZODB distributions; there's no intention to remove it from Zope 2. On Fri, 2004-04-02 at 03:34, Dieter Maurer wrote: 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. It may be that some of the changes to Zope.Startup could be backported to improve the situation, but others are probably needed as well. I'll be glad to help out with this, but can't do this right now. -Fred -- Fred L. Drake, Jr. fred at zope.com PythonLabs at Zope Corporation ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [Weakness] analysis of Zope startup problems
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. -- Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
