Bug#774904: systemd: Some systems (upgrades?) fail to put journal into syslog

[Michael Biebl]

control: tags -1 moreinfo

Am 08.01.2015 um 22:00 schrieb Daniel Dickinson:
> Package: systemd
> Version: 215-8
> Severity: normal
> 
> As I mentioned in my previous bug report I've (at least temporarily) had
> to switch my system back to sysvinit because of issues with initscripts
> failing to start on some systems, however I still feel I ought to report
> the bugs I've found.
> 
> This second bug is that on system systems (upgrades) the journal fails
> to go to the syslog.  This seemed to have been resolved on the system where
> I originally observed it (and the bug on the topic closed), however it turns
> out that after a reboot the problem came back.
> 
> In particular deluged and cyrus-imapd had no logs even though the information
> was in journalctl. deluged actually logs to a non-syslog file but errors
> with starting deluge go to journal (because it's before deluge is actually
> started and the init system that is doing the logs).

Which syslog daemon is running on those systems, syslog-ng, rsyslog, ...?
Which version of that package is installed?
What is the output of "systemctl status syslog.socket syslog.service"?

If you run "logger foobar", does this end up in /var/log/syslog?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150108/11cc30b7/attachment-0002.sig>