Activity log for bug #1227081

Date Who What changed Old value New value Message
2013-09-18 11:49:50 Raphaël Badin bug added bug
2013-09-18 12:16:01 Raphaël Badin maas: assignee Raphaël Badin (rvb)
2013-09-18 12:16:04 Raphaël Badin maas: status Triaged In Progress
2013-09-18 12:33:13 Raphaël Badin branch linked lp:~rvb/maas/unify-loggers
2013-09-18 13:49:42 Raphaël Badin maas: status In Progress Fix Committed
2013-09-18 14:47:39 Raphaël Badin maas: milestone 13.10
2013-09-18 23:42:59 Julian Edwards description Using the daily package (1.4+bzr1589+dfsg-0+1619+200~ppa0~ubuntu13.10.1) I stumbled across this error message "No handlers could be found for logger "maasserver"" repeated over and over in /var/log/apache2/error.log. Whilst contrib/maas_local_settings.py defines the handlers for the logger named 'maas', src/maasserver/__init__.py initializes the logger object with logging.getLogger(__name__) and thus __name__ will be 'maasserver'. Running "bzr grep getLogger | grep maas" shows that we're using both 'maas' and 'maaserver' when trying to get a logger using getLogger(). I suggest we unify that as we are probably loosing some of the logged information. Using the daily package (1.4+bzr1589+dfsg-0+1619+200~ppa0~ubuntu13.10.1) I stumbled across this error message "No handlers could be found for logger "maasserver"" repeated over and over in /var/log/apache2/error.log. Whilst contrib/maas_local_settings.py defines the handlers for the logger named 'maas', src/maasserver/__init__.py initializes the logger object with logging.getLogger(__name__) and thus __name__ will be 'maasserver'. Running "bzr grep getLogger | grep maas" shows that we're using both 'maas' and 'maaserver' when trying to get a logger using getLogger(). I suggest we unify that as we are probably losing some of the logged information.
2013-10-17 23:55:19 Julian Edwards maas: status Fix Committed Fix Released