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

[Vedran Furač]

On 04.09.2014 23:38, Michael Biebl wrote:
> Am 04.09.2014 23:07, schrieb Vedran Furač:
> 
> Well, something or someone stopped the rsyslog service on Sep  4
> 22:38:09. So it's obvious you don't get anymore updates to
> /var/log/syslog. Now we need to find out, why rsyslog.service (and
> syslog.socket) was stopped.

Oh, that's just last log line before the reboot, here are few more messages:

# tail /var/log/syslog

Sep  4 22:38:04 hostname avahi-daemon[3218]: Leaving mDNS multicast
group on interface eth0.IPv4 with address 192.168.1.4.
Sep  4 22:38:04 hostname avahi-daemon[3218]: avahi-daemon 0.6.31 exiting.
Sep  4 22:38:04 hostname xinetd[3994]: Exiting...
Sep  4 22:38:05 hostname bitlbee[3341]: SIGTERM received, cleaning up
process.
Sep  4 22:38:05 hostname smartd[3776]: smartd received signal 15: Terminated
Sep  4 22:38:05 hostname smartd[3776]: Device: /dev/sda [SAT], state
written to
/var/lib/smartmontools/smartd.WDC_WD7500AZRX_00A8LB0-WD_WMC1U2448778.ata.state
Sep  4 22:38:05 hostname smartd[3776]: Device: /dev/sdb [SAT], state
written to
/var/lib/smartmontools/smartd.SAMSUNG_HD753LJ-S13UJDWS800167.ata.state
Sep  4 22:38:05 hostname smartd[3776]: smartd is exiting (exit status 0)
Sep  4 22:38:06 hostname acpid: exiting
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.

So apparently rsyslog wasn't started on boot. I assumed this is
intentional since journal would take its job.

> Can you please reboot, add "systemd.log_level=debug" to the kernel
> command line, and then attach the output of "journalctl -alb" to the bug
> report

I would need to sanitize the (pretty long) output, would this be helpful?

# journalctl -alb|grep -i syslog

Ruj 05 00:33:07 hostname systemd[1]: Failed to load configuration for
syslog.target: No such file or directory
Ruj 05 00:33:07 hostname systemd[1]: Failed to load configuration for
syslog.service: No such file or directory
Ruj 05 00:33:07 hostname systemd[1]: Installed new job
rsyslog.service/start as 86
Ruj 05 00:33:07 hostname systemd[1]: Installed new job
syslog.socket/start as 87
Ruj 05 00:33:07 hostname systemd[1]: Starting Journal Socket (/dev/log).
Ruj 05 00:33:07 hostname systemd[1]: systemd-journald-dev-log.socket
changed dead -> listening
Ruj 05 00:33:07 hostname systemd[1]: Job
systemd-journald-dev-log.socket/start finished, result=done
Ruj 05 00:33:07 hostname systemd[1]: Listening on Journal Socket (/dev/log).
Ruj 05 00:33:07 hostname systemd[1]: Starting Syslog Socket.
Ruj 05 00:33:07 hostname systemd[1]: Socket service syslog.service not
loaded, refusing.
Ruj 05 00:33:07 hostname systemd[1]: Job syslog.socket/start finished,
result=failed
Ruj 05 00:33:07 hostname systemd[1]: Failed to listen on Syslog Socket.
Ruj 05 00:33:07 hostname systemd[1]: Job rsyslog.service/start finished,
result=dependency
Ruj 05 00:33:07 hostname systemd[1]: Dependency failed for System
Logging Service.
Ruj 05 00:33:07 hostname systemd[1]: Starting LVM2 metadata daemon
socket.Ruj 05 00:38:03 hostname systemd[1]: Got message type=method_call
sender=n/a destination=org.freedesktop.systemd1
object=/org/freedesktop/systemd1/unit/syslog_2esocket
interface=org.freedesktop.DBus.Properties member=GetAll cookie=1
reply_cookie=0 error=n/a

There's nothing listening on port 514 (both tcp and udp) in case you ask
that.

Regards,
Vedran