Bug#731742: [Pkg-systemd-maintainers] Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

On Fri, 11 Dec 2015 16:26:12 +0100 Michael Biebl wrote: > On Thu, 6 Mar 2014 10:08:27 -0500 Eric Cooper wrote: > > On Thu, Mar 06, 2014 at 06:20:54AM +0100, Michael Biebl wrote: > > > Ah good, we are finally getting somewhere. Could you try to > > > compare the

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Before adding to this bug, I ran: systemctl enable rsyslog.service /etc/init.d/rsyslog start My understanding is that the workaround for this bug required me to run these commands. I'm not sure why the upgrade of systemd from 208-8 to 215-5+b1 on 7 October prevented syslog from starting.

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Control: tag -1 + moreinfo Hi, unfortunately, the attached files seem to be taken from a system that doesn't expose the bug: Jayen Ashar wrote (18 Nov 2014 09:54:02 GMT) : - Unit rsyslog.service: [...] Unit Load State: loaded Unit Active State: active Inactive Exit

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Hi Michael, Michael Biebl bi...@debian.org writes: Am 03.03.2014 23:02, schrieb Eric Cooper: == /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also == /etc/systemd/system/multi-user.target.wants/rsyslog.service /etc/systemd/system/syslog.service

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

On Sat, Mar 08, 2014 at 09:28:46PM +0100, Michael Stapelberg wrote: I think this bug is fixed with: http://anonscm.debian.org/gitweb/?p=collab-maint/init-system-helpers.git;a=commitdiff;h=3416d0c8bdaa1ecce0c23710d950be5e91162065 (which landed in i-s-h 1.8, whereas the dependency in rsyslog

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

On Thu, Mar 06, 2014 at 06:20:54AM +0100, Michael Biebl wrote: Ah good, we are finally getting somewhere. Could you try to compare the date of the /etc/systemd/system/syslog.service symlink with you dpkg.log. If you find a match, please also check, which version of i-s-h was installed then.

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: Bug#731742: Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 05.03.2014 17:06, schrieb Eric Cooper: n Wed, Mar 05, 2014 at 08:25:47AM +0100, Michael Biebl wrote: I guess we need a log with debug information enabled. Can you please boot and set the following kernel command line option systemd.log_level=debug and then attach the journalctl -b output

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: Bug#731742: Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Hm, this looks like the syslog.service symlink is missing. Do you have a symlink like this: ls -la /etc/systemd/system/syslog.service lrwxrwxrwx 1 root root 35 Sep 28 02:46 /etc/systemd/system/syslog.service - /lib/systemd/system/rsyslog.service Yes, that symlink is present, with the same

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 03.03.2014 23:02, schrieb Eric Cooper: - Unit rsyslog.service: Description: System Logging Service Instance: n/a Unit Load State: loaded Unit Active State: active Inactive Exit Timestamp: Mon 2014-03-03 16:41:25 EST Active Enter Timestamp: Mon

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 04.03.2014 03:10, schrieb Eric Cooper: On Mon, Mar 03, 2014 at 11:55:18PM +0100, Michael Biebl wrote: If you can reproduce the issue reliably, can you send us the output of systemctl status rsyslog.service syslog.socket and journalctl -b Yes, it happens every time I boot: $ sudo

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 03.03.2014 23:02, schrieb Eric Cooper: == /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also == /etc/systemd/system/multi-user.target.wants/rsyslog.service /etc/systemd/system/syslog.service /etc/systemd/system/multi-user.target.wants/rsyslog.service

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

On Wed, Mar 05, 2014 at 11:41:09PM +0100, Michael Biebl wrote: I don't see a WantedBy: multi-user.target, which you should have if the service is properly enabled. Could you paste the output again of ls -la /etc/systemd/system/syslog.service and

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 06.03.2014 01:34, schrieb Eric Cooper: On Wed, Mar 05, 2014 at 11:41:09PM +0100, Michael Biebl wrote: I don't see a WantedBy: multi-user.target, which you should have if the service is properly enabled. Could you paste the output again of ls -la /etc/systemd/system/syslog.service and

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Hi Eric, Am 04.03.2014 03:10, schrieb Eric Cooper: On Mon, Mar 03, 2014 at 11:55:18PM +0100, Michael Biebl wrote: If you can reproduce the issue reliably, can you send us the output of systemctl status rsyslog.service syslog.socket and journalctl -b Yes, it happens every time I boot: ..

Bug#731742: [Pkg-systemd-maintainers] Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 03.03.2014 23:02, schrieb Eric Cooper: Package: systemd Version: 204-7 Followup-For: Bug #731742 I want to confirm the same bug: installing systemd and systemd-sysv on my system causes my system to boot without any rsyslog service. rsyslog runs fine when started explicitly with

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 09.12.2013 10:44, schrieb Bart-Jan Vrielink: Package: systemd Version: 204-5 Severity: normal Dear Maintainer, When running under systemd, syslog.socket will not start. Because of this, rsyslog does not start via the init.d script. Rsyslogd works when invoked directly, and also

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

...@bugs.debian.org Subject: Re: Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start Am 09.12.2013 10:44, schrieb Bart-Jan Vrielink: Package: systemd Version: 204-5 Severity: normal Dear Maintainer, When running under systemd, syslog.socket will not start

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 09.12.2013 12:55, schrieb Bart-Jan Vrielink: Is rsyslog properly enabled? # sudo systemctl status rsyslog.service # ls -la /etc/systemd/system/syslog.service bartjan@fenchurch:~$ sudo systemctl status rsyslog.service [sudo] password for bartjan: rsyslog.service - System Logging Service

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Is rsyslog properly enabled? # sudo systemctl status rsyslog.service # ls -la /etc/systemd/system/syslog.service bartjan@fenchurch:~$ sudo systemctl status rsyslog.service [sudo] password for bartjan: rsyslog.service - System Logging Service Loaded: loaded