Your message dated Fri, 20 Mar 2015 03:40:50 +0100
with message-id <[email protected]>
and subject line Re: Bug#774904: systemd: Some systems (upgrades?) fail to put
journal into syslog
has caused the Debian Bug report #774904,
regarding systemd: Some systems (upgrades?) fail to put journal into syslog
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
774904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774904
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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).
Regards,
Daniel
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-58
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-4
ii libc6 2.19-13
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-4
ii libgcrypt20 1.6.2-4+b1
ii libkmod2 18-3
ii liblzma5 5.1.1alpha+20120614-2+b3
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-8
ii mount 2.25.2-4
ii sysv-rc 2.88dsf-58
ii udev 215-8
ii util-linux 2.25.2-4
Versions of packages systemd recommends:
ii dbus 1.8.12-3
ii libpam-systemd 215-8
Versions of packages systemd suggests:
pn systemd-ui <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 01.02.2015 um 09:03 schrieb Daniel Dickinson:
> 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.
>
Ok, so no systemd issue, maybe some intermittent issues with rsyslog
using older versions of dh-systemd.
I've just ran a couple of test dist-upgrades from wheezy to jessie, and
rsyslog was always correctly enabled on upgrades.
Therefor closing the bug report.
Michael
--
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
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
