Error in apache's log "No handlers could be found for logger "maasserver""

Bug #1227081 reported by Raphaël Badin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Raphaël Badin

Bug 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 losing some of the logged information.

Tags: log

Related branches

Revision history for this message
Gavin Panella (allenap) wrote :

We could also set up a handler for maasserver. The same handler as serves maas. Do you know where/how this is defined?

Revision history for this message
Raphaël Badin (rvb) wrote :

Yes, it's defined in contrib/maas_local_settings.py. We also use a logger named "metadataserver" in src/metadataserver/api.py.

I'm fixing this.

Changed in maas:
assignee: nobody → Raphaël Badin (rvb)
status: Triaged → In Progress
Raphaël Badin (rvb)
Changed in maas:
status: In Progress → Fix Committed
Raphaël Badin (rvb)
Changed in maas:
milestone: none → 13.10
description: updated
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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