non persistent logging after cleaning log files on disk
Bug #1401984 reported by
Sebastien Bacher
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rsyslog (Ubuntu) |
Fix Released
|
High
|
Martin Pitt |
Bug Description
Using current vivid with systemd init, I've cleaned the log on disk (*.log syslog dmesg) and rebooted my test box, since then it stopped logging to syslog.
journalctl has the log from the current boot but not from previous ones
the behaviour there is a bit confusing, I first though that I would get a fresh syslog on next boot and not an auto conversion to use journald, then the journal should keep record from previous boots as well...
Related branches
Changed in rsyslog (Ubuntu): | |
importance: | Undecided → High |
status: | In Progress → Fix Committed |
tags: | added: systemd-boot |
To post a comment you must log in.
Actually, this is not a systemd behavior but seems to be a syslog one.
1. rm /var/log/syslog
2. reboot
-> no log (under systemd or upstart)
3. touch /var/log/syslog
4. chmod syslog:adm /var/log/syslog
5. reboot
-> logs availables
The cause is that /var/log is 755 and root:syslog (I wonder why it's in syslog group as it's not 775?), and so can't recreate the file.
If I chmod syslog, indeed, /var/log/syslog is created, but with other rights, being syslog:syslog instead of syslog:adm.
So, it worths more discussion (retargetting to syslog), pinging Martin on this.