Panko dispatcher and publisher should not setup oslo_log again
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Panko |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
There seems to be a bug w.r.t. logging when configuring panko dispatcher at Ceilometer. When Ceilometer collector loads the Panko database dispatcher, the Panko database dispatcher calls the below API
conf = service.
As part of this, the following call is made:
log.setup(conf, 'panko')
This probably causes the logger to switch to /var/log/panko. I had to touch ceilometer-
When ceilometer-
2017-02-20 04:40:06.589 19410 DEBUG cotyledon.
2017-02-20 04:40:06.590 19410 DEBUG cotyledon.
2017-02-20 04:40:06.594 19419 DEBUG ceilometer.
2017-02-20 04:40:06.597 19419 DEBUG ceilometer.
Then the rest of the logging switches over to /var/log/
[root panko]# head -10 ceilometer-
2017-02-20 04:40:06.751 19419 DEBUG panko.storage [-] looking for 'mysql' driver in panko.storage get_connection /usr/lib/
2017-02-20 04:40:06.866 19419 DEBUG cotyledon.
2017-02-20 04:40:06.866 19419 DEBUG cotyledon.
2017-02-20 04:40:06.866 19419 DEBUG cotyledon.
no longer affects: | ceilometer |
It seems that until I create the log file /var/log/ panko/ceilomete r-collector. log, the collector process does not write to database about events. So this not only affect writing logs to log file, but affects the functionality of putting events to database as well.