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. On Wednesday, 19 November 2014, 21:37, intrigeri <intrig...@debian.org> wrote: > > >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 Timestamp: Tue 2014-11-18 20:24:05 AEDT >> Active Enter Timestamp: Tue 2014-11-18 20:24:05 AEDT >[...] >> -> ExecStart: >> Command Line: /usr/sbin/rsyslogd -n >> PID: 22083 >> Start Timestamp: Tue 2014-11-18 20:24:05 AEDT >> SysVStartPriority: 0 > >and: > >> -> Unit syslog.socket: >> Description: Syslog Socket >> Instance: n/a >> Unit Load State: loaded >> Unit Active State: active > >Did I misunderstand anything? > >If I'm correct, then please attach the same information, generated on >a system that actually has the problem you're describing. Thanks! > >Cheers, >-- >intrigeri > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
