[2.2] maas.log rotation is daily and stored for one week only
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
When looking for the root cause of a bug I found, I saw that only 7 days of MAAS logs are retained.
This makes it difficult to triage the root cause of issues that could have occurred longer ago than one week.
We should consider a less aggressive schedule, especially for `maas.log`. (Maybe it's fine if regiond and rackd logs are deleted more frequently, but we could still lose important information by being too aggressive here.)
It seems to me that, at a minimum, maas.log should rotate in a way more similar to dpkg.log:
# ls -la /var/log/dpkg.log*
-rw-r--r-- 1 root root 231389 Mar 28 10:37 /var/log/dpkg.log
-rw-r--r-- 1 root root 332437 Feb 28 03:50 /var/log/dpkg.log.1
-rw-r--r-- 1 root root 141406 Jun 1 2016 /var/log/
-rw-r--r-- 1 root root 22345 Jan 31 10:43 /var/log/
-rw-r--r-- 1 root root 22599 Dec 23 19:25 /var/log/
-rw-r--r-- 1 root root 29989 Dec 1 08:34 /var/log/
-rw-r--r-- 1 root root 3753 Oct 28 01:11 /var/log/
-rw-r--r-- 1 root root 15470 Sep 29 15:07 /var/log/
-rw-r--r-- 1 root root 32667 Aug 30 2016 /var/log/
-rw-r--r-- 1 root root 7422 Jul 29 2016 /var/log/
-rw-r--r-- 1 root root 23754 Jul 1 2016 /var/log/
If I look in dpkg.log, I can see that it contains multiple days worth of logging.
Related branches
- Mike Pontillo (community): Approve
-
Diff: 33 lines (+9/-3)2 files modifieddebian/changelog (+3/-1)
debian/maas-common.logrotate (+6/-2)
- MAAS Maintainers: Pending requested
-
Diff: 5409 lines (+4974/-0)86 files modifieddebian/changelog (+2448/-0)
debian/compat (+1/-0)
debian/control (+307/-0)
debian/copyright (+45/-0)
debian/extras/20-maas.conf (+40/-0)
debian/extras/99-maas-common-sudoers (+12/-0)
debian/extras/99-maas-region-sudoers (+7/-0)
debian/extras/99-maas-sudoers (+15/-0)
debian/extras/isc-dhcp-server.override (+1/-0)
debian/extras/maas (+13/-0)
debian/extras/maas-proxy-common.sh (+23/-0)
debian/extras/maas-rack (+85/-0)
debian/extras/maas-region (+65/-0)
debian/extras/maas_remote_syslog_compress (+2/-0)
debian/extras/squid3.override (+1/-0)
debian/maas-cli.install (+1/-0)
debian/maas-cli.links (+1/-0)
debian/maas-cli.lintian-overrides (+1/-0)
debian/maas-common.dirs (+3/-0)
debian/maas-common.install (+4/-0)
debian/maas-common.lintian-overrides (+1/-0)
debian/maas-common.logrotate (+13/-0)
debian/maas-common.maintscript (+2/-0)
debian/maas-common.postinst (+40/-0)
debian/maas-common.postrm (+21/-0)
debian/maas-common.templates (+54/-0)
debian/maas-dhcp.apparmor (+10/-0)
debian/maas-dhcp.dirs (+2/-0)
debian/maas-dhcp.install (+1/-0)
debian/maas-dhcp.maas-dhcpd.service (+28/-0)
debian/maas-dhcp.maas-dhcpd6.service (+28/-0)
debian/maas-dhcp.maintscript (+2/-0)
debian/maas-dhcp.postinst (+35/-0)
debian/maas-dhcp.postrm (+16/-0)
debian/maas-dhcp.preinst (+16/-0)
debian/maas-dns.dirs (+1/-0)
debian/maas-dns.postinst (+61/-0)
debian/maas-dns.postrm (+25/-0)
debian/maas-proxy.dirs (+2/-0)
debian/maas-proxy.install (+1/-0)
debian/maas-proxy.logrotate (+24/-0)
debian/maas-proxy.maas-proxy.service (+19/-0)
debian/maas-proxy.postinst (+28/-0)
debian/maas-proxy.postrm (+12/-0)
debian/maas-rack-controller.config (+36/-0)
debian/maas-rack-controller.dirs (+4/-0)
debian/maas-rack-controller.install (+13/-0)
debian/maas-rack-controller.links (+1/-0)
debian/maas-rack-controller.lintian-overrides (+1/-0)
debian/maas-rack-controller.logrotate (+15/-0)
debian/maas-rack-controller.maas-rackd.service (+28/-0)
debian/maas-rack-controller.maintscript (+9/-0)
debian/maas-rack-controller.postinst (+168/-0)
debian/maas-rack-controller.postrm (+50/-0)
debian/maas-rack-controller.preinst (+56/-0)
debian/maas-rack-controller.templates (+15/-0)
debian/maas-rack-udeb.postinst (+77/-0)
debian/maas-rack-udeb.templates (+34/-0)
debian/maas-region-api.apport (+72/-0)
debian/maas-region-api.install (+20/-0)
debian/maas-region-api.links (+8/-0)
debian/maas-region-api.lintian-overrides (+5/-0)
debian/maas-region-api.logrotate (+15/-0)
debian/maas-region-api.maas-regiond-worker@.service (+28/-0)
debian/maas-region-api.maas-regiond.service (+24/-0)
debian/maas-region-api.maintscript (+7/-0)
debian/maas-region-api.postinst (+82/-0)
debian/maas-region-api.postrm (+50/-0)
debian/maas-region-api.preinst (+38/-0)
debian/maas-region-api.prerm (+9/-0)
debian/maas-region-controller.config (+49/-0)
debian/maas-region-controller.postinst (+194/-0)
debian/maas-region-controller.postrm (+22/-0)
debian/maas-region-controller.prerm (+13/-0)
debian/maas-region-controller.templates (+38/-0)
debian/maas-region-udeb.postinst (+82/-0)
debian/maas-region-udeb.templates (+29/-0)
debian/maintscript (+2/-0)
debian/po/POTFILES.in (+1/-0)
debian/po/templates.pot (+69/-0)
debian/python3-django-maas.install (+2/-0)
debian/python3-maas-client.install (+2/-0)
debian/python3-maas-provisioningserver.install (+1/-0)
debian/rules (+84/-0)
debian/source/format (+1/-0)
debian/watch (+3/-0)
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| milestone: | none → next |
| Andres Rodriguez (andreserl) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Incomplete |
| importance: | Wishlist → Undecided |
| milestone: | next → 2.2.0 |
| summary: |
- [2.2] MAAS log rotation is too aggressive + [2.2] maas.log rotation is daily and stored for one week only |
| Changed in maas: | |
| importance: | Undecided → Medium |
| status: | Incomplete → Triaged |
| Mike Pontillo (mpontillo) wrote | #3 |
| Changed in maas: | |
| status: | Triaged → New |
| status: | New → Triaged |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Gavin Panella (allenap) wrote | #4 |
| Mike Pontillo (mpontillo) wrote | #5 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
I'm fine with that, the difference with dpkg logging vs MAAS logging is that MAAS logging is super verbose in comparison to dpkg's. This means MAAS has WAY more data.