https://bugzilla.novell.com/show_bug.cgi?id=791076 https://bugzilla.novell.com/show_bug.cgi?id=791076#c0 Summary: AY installation without reboot: syslog service in failed state Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: fehr@suse.com ReportedBy: joschibrauchle@gmx.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11 After performing an AY installation without a final reboot, the syslog service is in failed state: ---------- # rcsyslog status redirecting to systemctl syslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/syslog.service; enabled) Active: failed (Result: exit-code) since Fri, 23 Nov 2012 17:39:07 +0100; 40min ago Process: 15328 ExecStart=/sbin/rsyslogd -c 5 -f /etc/rsyslog.conf (code=exited, status=1/FAILURE) Process: 15326 ExecStartPre=/var/run/rsyslog/addsockets (code=exited, status=0/SUCCESS) Process: 15324 ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service (code=exited, status=0/SUCCESS) Main PID: 804 (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/syslog.service ---------- but actually syslog (or rsyslogd in my installation) is running: ---------- #ps auxf|grep syslog root 2027 0.0 0.0 316764 1508 ? Sl 17:05 0:00 /sbin/rsyslogd -c 5 -f /etc/rsyslog.conf ---------- Possibly, syslog is started in the second installation stage by Autoyast, but after installation finished, systemd does not know about this? Starting a second instance via systemd fails, as only one instance is allowed... Reproducible: Always Steps to Reproduce: 1. Install 12.2 via AY and no final reboot 2. systemctl status syslog 3. Actual Results: syslog service failed, but rsyslogd running Expected Results: syslog service should be OK -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.