Ok, so MAAS install's an rsyslog config to forward messages from syslog
to /var/log/maas/maas.log. Today we noticed that maas.log was completely
empty, and on further checking, we noticed that syslog was completely
empty as well. The fun fact, however, is that MAAS has not changed its
syslog configuration in years, and we definitely don't believe this is
the problem. Also, this was working before just fine without any issues
before , and as such, we don't believe is a problem on rsyslog.
The interesting thing is that rsyslog hasn't really change much in the
past few months (iother that 2, no change rebuilds). Also, syslog logs
that should be on /var/log/syslog are on systemd's journal.
MAAS config on /etc/maas/rsyslog.d/99-maas:
# Log MAAS messages to their own file.
:syslogtag,contains,"maas" /var/log/maas/maas.log
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: maas (Ubuntu)
** Description changed:
- /var/log/syslog is empty and everything is under systemd's journal.
+ 130 roaksoax@unleashed:~/Desktop/project/packaging⟫ dpkg -l | grep rsyslog
+ ii rsyslog 8.16.0-1ubuntu3
amd64 reliable system and kernel logging daemon
+ ii rsyslog-gnutls 8.16.0-1ubuntu3
amd64 TLS protocol support for rsyslog
+
+ roaksoax@unleashed:~/Desktop/project/packaging⟫ sudo service rsyslog status
+ [sudo] password for roaksoax:
+ ● rsyslog.service - System Logging Service
+ Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor
preset: enabled)
+ Active: active (running) since Tue 2016-04-26 16:12:24 EDT; 1h 39min ago
+ Docs: man:rsyslogd(8)
+ http://www.rsyslog.com/doc/
+ Main PID: 26547 (rsyslogd)
+ Tasks: 5 (limit: 512)
+ Memory: 1.3M
+ CPU: 174ms
+ CGroup: /system.slice/rsyslog.service
+ └─26547 /usr/sbin/rsyslogd -n
+
+ Apr 26 16:12:24 unleashed systemd[1]: Starting System Logging Service...
+ Apr 26 16:12:24 unleashed systemd[1]: Started System Logging Service.
+
+ roaksoax@unleashed:~/Desktop/project/packaging⟫ sudo cat /var/log/syslog
+ roaksoax@unleashed:~/Desktop/project/packaging⟫
** Changed in: rsyslog (Ubuntu)
Importance: Undecided => Critical
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1575337
Title:
syslog.log is completely empty
Status in rsyslog package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
130 roaksoax@unleashed:~/Desktop/project/packaging⟫ dpkg -l | grep rsyslog
ii rsyslog 8.16.0-1ubuntu3
amd64 reliable system and kernel logging daemon
ii rsyslog-gnutls 8.16.0-1ubuntu3
amd64 TLS protocol support for rsyslog
roaksoax@unleashed:~/Desktop/project/packaging⟫ sudo service rsyslog status
[sudo] password for roaksoax:
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor
preset: enabled)
Active: active (running) since Tue 2016-04-26 16:12:24 EDT; 1h 39min ago
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Main PID: 26547 (rsyslogd)
Tasks: 5 (limit: 512)
Memory: 1.3M
CPU: 174ms
CGroup: /system.slice/rsyslog.service
└─26547 /usr/sbin/rsyslogd -n
Apr 26 16:12:24 unleashed systemd[1]: Starting System Logging Service...
Apr 26 16:12:24 unleashed systemd[1]: Started System Logging Service.
roaksoax@unleashed:~/Desktop/project/packaging⟫ sudo cat /var/log/syslog
roaksoax@unleashed:~/Desktop/project/packaging⟫
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1575337/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
