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

[Eric Cooper]

> 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 permissions and target.

I can successfully do either "systemctl start rsyslog" or "systemctl start syslog"
once the system has booted.

BTW, it looks like the most recent upgrade to rsyslog was this:

    2013-09-17 18:07:54 upgrade rsyslog:amd64 7.4.3-1 7.4.4-1
    2013-09-17 18:07:54 status half-configured rsyslog:amd64 7.4.3-1
    2013-09-17 18:07:54 status unpacked rsyslog:amd64 7.4.3-1
    2013-09-17 18:07:55 status half-installed rsyslog:amd64 7.4.3-1
    2013-09-17 18:07:55 status half-installed rsyslog:amd64 7.4.3-1
    2013-09-17 18:07:55 status unpacked rsyslog:amd64 7.4.4-1
    2013-09-17 18:07:55 status unpacked rsyslog:amd64 7.4.4-1
    2013-09-17 18:09:12 configure rsyslog:amd64 7.4.4-1 <none>
    2013-09-17 18:09:12 status unpacked rsyslog:amd64 7.4.4-1
    2013-09-17 18:09:12 status unpacked rsyslog:amd64 7.4.4-1
    2013-09-17 18:09:13 status unpacked rsyslog:amd64 7.4.4-1
    2013-09-17 18:09:13 status unpacked rsyslog:amd64 7.4.4-1
    2013-09-17 18:09:13 status unpacked rsyslog:amd64 7.4.4-1
    2013-09-17 18:09:13 status unpacked rsyslog:amd64 7.4.4-1
    2013-09-17 18:09:13 status half-configured rsyslog:amd64 7.4.4-1
    2013-09-17 18:09:14 status installed rsyslog:amd64 7.4.4-1

-- 
Eric Cooper             e c c @ c m u . e d u