syslog.log is completely empty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
130 roaksoax@
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@
[sudo] password for roaksoax:
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/
Active: active (running) since Tue 2016-04-26 16:12:24 EDT; 1h 39min ago
Docs: man:rsyslogd(8)
http://
Main PID: 26547 (rsyslogd)
Tasks: 5 (limit: 512)
Memory: 1.3M
CPU: 174ms
CGroup: /system.
└─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@
roaksoax@
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 29 lines (+7/-4)2 files modifieddebian/changelog (+1/-1)
debian/extras/20-maas.conf (+6/-3)
description: | updated |
no longer affects: | maas |
description: | updated |
summary: |
- [2.0a4] maas.log is empty + syslog.log is completely empty |
Changed in systemd (Ubuntu): | |
importance: | Undecided → Critical |
importance: | Critical → Undecided |
Changed in maas: | |
status: | New → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Can you please give some context here? /var/log/syslog is entirely rsyslog's domain, systemd has nothing to do with it. Maybe you don't have rsyslog installed? (which is perfectly plausible and doable, as you can enable the persistent journal). Is rsyslog.service running? /var/log/syslog is certainly getting logs on a standard vivid/wily/xenial system.