Description of problem: syslog-ng.service has: ... ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service ... systemd-kmsg-syslogd.service does not exist anymore since the systemd journal was introduced (in Fedora 17). Please remove the ExecStartPre line. Or, if you want to use the same unit file with pre-journal systemd versions, at the very least prefix the command with a dash, so that errors will be ignored. It is actually a bug that "systemctl stop" does not exit with a non-zero error code when operating on a non-existent unit. We're going to fix that bug in systemd and the fix would break your unit as it is now. Version-Release number of selected component (if applicable): syslog-ng-3.2.5-14.fc17.x86_64
syslog-ng-3.2.5-15.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/syslog-ng-3.2.5-15.fc17
Package syslog-ng-3.2.5-15.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing syslog-ng-3.2.5-15.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-9741/syslog-ng-3.2.5-15.fc17 then log in and leave karma (feedback).
Problem reported upstream. Ticket: https://bugzilla.balabit.com/show_bug.cgi?id=184 Upstream commit for syslog-ng 3.3.6: https://github.com/balabit/syslog-ng-3.3/commit/d2369ec9f7662ad002155aecdde8d0e31fd21106
syslog-ng-3.2.5-15.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
After trying this update, Xen boot up stops at "Starting Xendomains - start and stop guests on boot and shutdown..." which was the line before "systemd-kmsg-syslogd.service" line earlier.