On Wed, Mar 22, 2017 at 02:27:26AM +0100, Michael Biebl wrote:
> That should be a symlink, not a real file.
> lrwxrwxrwx 1 root root 35 Jul 26 2016
> /etc/systemd/system/syslog.service -> /lib/systemd/system/rsyslog.service
After fixing this, I can't reproduce the problem.
> that's also how
Am 22.03.2017 um 01:52 schrieb Nathan Dorfman:
> On Wed, Mar 22, 2017 at 12:50:01AM +0100, Michael Biebl wrote:
>> Please attach a complete journal log from the boot (journalctl -alb as root)
>
> Done, but might not be helpful. I've (cleanly) rebooted since then,
> and now it's two *different*
On Wed, Mar 22, 2017 at 12:50:01AM +0100, Michael Biebl wrote:
> Please attach a complete journal log from the boot (journalctl -alb as root)
Done, but might not be helpful. I've (cleanly) rebooted since then,
and now it's two *different* units that are failed. It looks like I've
somehow ended up
Am 21.03.2017 um 22:37 schrieb Nathan Dorfman:
> Package: rsyslog
> Version: 8.24.0-1
> Severity: minor
>
> Dear Maintainer,
>
> I noticed some 'FAILED' lines scroll by quickly at boot; upon investigation:
Please attach a complete journal log from the boot (journalctl -alb as root)
--
Why is
Might as well also note that the running rsyslogd instance appears to be
logging correctly:
root@stretch:/home/test# ls -lart /var/log/*.log
-rw-r--r-- 1 root root3043 Mar 19 17:09 /var/log/fontconfig.log
-rw-r--r-- 1 root root 61574 Mar 21 15:53 /var/log/alternatives.log
-rw-r--r-- 1 root
Oops, I forgot to include these lines:
test@stretch:~$ ps -fp `cat /var/run/rsyslogd.pid`
UIDPID PPID C STIME TTY TIME CMD
root 438 1 0 16:48 ?00:00:00 /usr/sbin/rsyslogd -n
test@stretch:~$
I also just noticed that this PID isn't the same as the one in the
Package: rsyslog
Version: 8.24.0-1
Severity: minor
Dear Maintainer,
I noticed some 'FAILED' lines scroll by quickly at boot; upon investigation:
root@stretch:/home/test# systemctl status | head -2
● stretch
State: degraded
root@stretch:/home/test# systemctl list-units --state=failed
UNIT
7 matches
Mail list logo
