BlueBream

"Developer mode is enabled" warning is displayed two times at startup

Bug #549331 reported by Baiju Muthukadan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BlueBream
Fix Committed
Medium
Ilshad Khabibullin

Bug Description

While running BlueBream this warning is repeated:

2010-03-27 09:37:58,625 WARNING [root] Developer mode is enabled: this is a security risk and should NOT be enabled on production servers. Developer mode can usually be turned off by setting the `devmode` option to `off` or by removing it from the instance configuration file completely.
------
2010-03-27T09:37:58 WARNING root Developer mode is enabled: this is a security risk and should NOT be enabled on production servers. Developer mode can usually be turned off by setting the `devmode` option to `off` or by removing it from the instance configuration file completely.

Revision history for this message
Baiju Muthukadan (baijum) wrote :

Send mail to list:
https://mail.zope.org/pipermail/bluebream/2010-March/000185.html

Changed in bluebream:
status: New → Confirmed
Baiju Muthukadan (baijum)
Changed in bluebream:
importance: Undecided → Medium
Ilshad Khabibullin (astoon)
Changed in bluebream:
assignee: nobody → Ilshad Khabibullin (astoon)
Revision history for this message
Ilshad Khabibullin (astoon) wrote :

First warning ("... WARNING [root] Developer ...") goes to STDERR, from handler, which defined by paste.script and described in debug.ini file, section [handler_console].

Second warning ("... WARNING root Developer ...") goes to STDOUT, from handler, defined in ZConfig and described in zope.conf, section `logfile` with path STDOUT.

If we need access.log using WSGI for debug, then we can't remove loggers and handlers from debug.ini.

Unfortunately, we can't remove `root` logger from debug.ini also, because first key should be `root` (as defined in standard python module logger.config). I.e. we perforce to keep `root` handler in debug.ini

And we need to keep that logger definition in zope.conf, obviously.

To avoid double logging, I increased logging level for first handler (in debug.ini) from NOTSET to ERROR.

Changed in bluebream:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.