rsyslog fails to start (Lubuntu 17.10)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rsyslog (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1)
Description: Ubuntu 17.10
Release: 17.10
2) 8.16.0-1ubuntu9
3) I'd like to see what happened in the system
4) syslog is empty, messages is obsolete, lastlog shows only pure console logins (it maybe unrelated)
root@user:~# systemctl status rsyslog
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Thu 2017-10-19 02:24:34 MSK; 1h 15min ago
Docs: man:rsyslogd(8)
http://
Process: 1858 ExecStart=
Main PID: 1858 (code=exited, status=1/FAILURE)
окт 19 02:24:33 user systemd[1]: rsyslog.service: Main process exited, code=exited, stat
окт 19 02:24:33 user systemd[1]: Failed to start System Logging Service.
окт 19 02:24:33 user systemd[1]: rsyslog.service: Unit entered failed state.
окт 19 02:24:33 user systemd[1]: rsyslog.service: Failed with result 'exit-code'.
окт 19 02:24:34 user systemd[1]: rsyslog.service: Service hold-off time over, scheduling
окт 19 02:24:34 user systemd[1]: Stopped System Logging Service.
окт 19 02:24:34 user systemd[1]: rsyslog.service: Start request repeated too quickly.
окт 19 02:24:34 user systemd[1]: Failed to start System Logging Service.
окт 19 02:24:34 user systemd[1]: rsyslog.service: Unit entered failed state.
окт 19 02:24:34 user systemd[1]: rsyslog.service: Failed with result 'exit-code'.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: rsyslog 8.16.0-1ubuntu9
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: LXDE
Date: Thu Oct 19 03:59:04 2017
InstallationDate: Installed on 2017-10-06 (12 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)
Since rsyslog does not work, I replace it to inetutils-syslogd, but it seems like inetutils-syslogd has some problems with apparmor, but aa-logprof gives me nothing and says all is ok.