Bug#760426: [systemd] Logs gone after moving to systemd

Vedran Furač vedran.furac at gmail.com
Thu Sep 4 22:07:34 BST 2014


Hey, thanks for quick reply!

On 04.09.2014 02:18, Michael Biebl wrote:
> Am 04.09.2014 um 02:07 schrieb Vedran Furač:
>> Package: systemd
>> Severity: important
>>
>> By documentation I mean:
>>
>> - Package description (mentions that it replaces sysvinit only)
>> - README.Debian
>> - wiki.debian.org (systemd page)
>> - debconf message
>>
>> Such a huge change must be announced using bold and uppercase and be
>> documented properly. Debian usually warns through debconf for far more
>> trivial things.
> 
> Which version of rsyslog do you have installed?
> Which version of systemd do you use?
> What's the output of
> systemctl status syslog.socket rsyslog.service
> systemctl is-enabled rsyslog.service
> 
> Installing systemd is not supposed to break any existing installed
> syslog. Rsyslog works great under systemd (even better then under sysvinit).

Here it is, without systemd-sysv:

# logger -t TEST 1234
# tail -1 /var/log/syslog
Sep  4 22:36:10 hostname TEST: 1234


# dpkg -l|grep systemd
ii  libpam-systemd:amd64
214-1                                 amd64        system and service
manager - PAM module
ii  libsystemd-daemon0:amd64               214-1
         amd64        systemd utility library (deprecated)
ii  libsystemd-id128-0:amd64               214-1
         amd64        systemd 128 bit ID utility library (deprecated)
ii  libsystemd-journal0:amd64              214-1
         amd64        systemd journal utility library (deprecated)
ii  libsystemd-login0:amd64                214-1
         amd64        systemd login utility library (deprecated)
ii  libsystemd0:amd64                      214-1
         amd64        systemd utility library
ii  systemd                                214-1
         amd64        system and service manager
ii  systemd-shim                           7-2exp1
         amd64        shim for systemd

# apt-get install systemd-sysv=214-1
# reboot

Now with systed-sysv:

# logger -t TEST 1234
# tail -1 /var/log/syslog
Sep  4 22:38:09 hostname rsyslogd: [origin software="rsyslogd"
swVersion="8.4.0" x-pid="2886" x-info="http://www.rsyslog.com"] exiting
on signal 15.

# journalctl --system|tail -1
Ruj 04 22:40:13 rigel TEST[2957]: 1234

# systemctl status syslog.socket rsyslog.service

● syslog.socket - Syslog Socket
   Loaded: loaded (/lib/systemd/system/syslog.socket; static)
   Active: inactive (dead)
     Docs: man:systemd.special(7)
           http://www.freedesktop.org/wiki/Software/systemd/syslog
   Listen: /run/systemd/journal/syslog (Datagram)

● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
   Active: inactive (dead)
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/

# systemctl is-enabled rsyslog.service
enabled


As you can see expected behavior is changed, and even worse, that's done
silently, without any warning and no explanation in documentation. It
also breaks unrelated packages like logcheck, etc (thus likely a RC bug).

Regards,
Vedran




More information about the Pkg-systemd-maintainers mailing list