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

[Daniel Dickinson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have confirmed that on both systems I still have that were upgraded
from wheezy that rsyslog has a system unit that does not get enabled.

I suspect the third also had the same issue (it had log issues) but I
had to revert it to jessie due to what looks like a major kernel
issues that eats data and what is probably different issues that
causes my scsi card to reset while doing backups.

Also there were some intermittent issues with amanda backup where perl
was failing to find modules that were definitely present.

It's not a hardware issue because with wheezy there are zero problems
on the same crypted raid array - only the root filesystem is different
(even the data lvm volumes are the same).

Since backups need to work I kept the rootfs for investigations, but
don't run jessie on the machine now.

Regards,

Daniel

On 2015-01-08 4:10 PM, Michael Biebl wrote:
> 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?
> 
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJUzd3VAAoJEIcvryNiYx3FtXAH/ifxS/T04W+Bpy653eGjwqYs
lDmUOImlSOcv8LMdbKXLrmdoE3ICTEOKwfBnO0I+ECUNjBdWvJCD2IyjC1h8EpFq
33mN4dW+5BWvYFTIiX/jbXyQ9NnNnwu3Fhkz02Jr41XitMk5VfnDSuw0nk8NdACk
XVO6997pjXrHOHSQLNkBBamLrqo3l2sCoBdAHGIKYXCRNZHcWMgssTlpSdDRM28F
4TV2z3PokxJayZ4AWwo7XAlyNvmG/4c25vPdgsEj4RswF6g8VRdpO2tPQAi45C3Y
3Tt/uGKP0tdBhuUavs3FMhAyvUJaV01j9OUJQvj0e+nrKwYpJ7qpnDGl2hxNaNk=
=VtMY
-----END PGP SIGNATURE-----