Clusterd in Latest trunk (rev3484) is logging to both clusterd.log and pserv.log
Bug #1413778 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Unassigned | ||
Bug Description
In the rev3484, MAAS Cluster Controller is logging to both pserv.log and clusterd.log. This is because
1: pserv.yaml, in packaging, is still specifying the logfile where to log
2. upstart job is now telling the daemon where to log.
The above causes that clusterd outputs to both pserv.yaml and clusterd.log.
Related branches
lp:~andreserl/maas/packaging_fix_clusterd_logging
- Gavin Panella (community): Approve
- Andres Rodriguez (community): Approve
-
Diff: 81 lines (+20/-16)4 files modifieddebian/changelog (+1/-1)
debian/maas-cluster-controller.preinst (+6/-0)
debian/patches/01-fix-database-settings.patch (+9/-3)
debian/patches/02-pserv-config.patch (+4/-12)
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
Revision history for this message
| Gavin Panella (allenap) wrote | #2 |
| Changed in maas: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Gavin Panella (allenap) wrote | #3 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
If we disable the logging in pserv.yaml, it will still try to log. I think we either remove that option entirely from pserv.yaml or we either do not tell the upstart job where to log.