[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk
This bug was fixed in the package rsyslog - 7.4.4-1ubuntu12 --- rsyslog (7.4.4-1ubuntu12) vivid; urgency=medium * Install debian/00rsyslog.conf tmpfiles.d snippet to ensure that the syslog group can write into /var/log/. (LP: #1401984) -- Martin PittTue, 16 Dec 2014 14:33:34 +0100 ** Changed in: rsyslog (Ubuntu) Status: Fix Committed => Fix Released -- 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/1401984 Title: non persistent logging after cleaning log files on disk Status in rsyslog package in Ubuntu: Fix Released 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1401984/+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
[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk
Note that the bug will still be present under upstart, but nothing new, for reference: http://irclogs.ubuntu.com/2014/12/16/%23ubuntu- desktop.html#t13:10 :) -- 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/1401984 Title: non persistent logging after cleaning log files on disk Status in rsyslog package in Ubuntu: Fix Committed 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1401984/+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
[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk
** Branch linked: lp:ubuntu/vivid-proposed/rsyslog -- 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/1401984 Title: non persistent logging after cleaning log files on disk Status in rsyslog package in Ubuntu: Fix Committed 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1401984/+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
[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk
** Changed in: rsyslog (Ubuntu) Importance: Undecided => High ** Changed in: rsyslog (Ubuntu) Status: In Progress => Fix Committed ** Tags added: systemd-boot -- 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/1401984 Title: non persistent logging after cleaning log files on disk Status in rsyslog package in Ubuntu: Fix Committed 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1401984/+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
[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk
Ah, our rsyslog has a delta, so let's stick a matching tmpfiles.d/ snippet into rsyslog. ** Package changed: systemd (Ubuntu) => rsyslog (Ubuntu) ** Changed in: rsyslog (Ubuntu) Status: New => In Progress ** Changed in: rsyslog (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- 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/1401984 Title: non persistent logging after cleaning log files on disk Status in rsyslog package in Ubuntu: In Progress 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1401984/+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
[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk
rsyslog's postinst seems fine. I have a gut feeling that this is due to /usr/lib/tmpfiles.d/var.conf changing it back to 0755, the permissions are wrong there. ** Package changed: rsyslog (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1401984 Title: non persistent logging after cleaning log files on disk Status in systemd package in Ubuntu: New 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1401984/+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
[Touch-packages] [Bug 1401984] Re: non persistent logging after cleaning log files on disk
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. ** Package changed: systemd (Ubuntu) => rsyslog (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1401984 Title: non persistent logging after cleaning log files on disk Status in systemd package in Ubuntu: New 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1401984/+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
