Am 05.09.2014 00:52, schrieb Vedran Furač: > So apparently rsyslog wasn't started on boot. I assumed this is > intentional since journal would take its job.
Nope, this is not intentional. rsyslog should run just fine alongside the journal. > >> 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. Apparently your syslog socket unit fails to start. Why is not clear yet. As said, please provide a complete debug log for the boot. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
