Bug 1508771

Summary:	rsyslog failed to start
Product:	[Fedora] Fedora	Reporter:	Claude Frantz <Claude.Frantz>
Component:	rsyslog	Assignee:	Radovan Sroka <rsroka>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	26	CC:	dkopecek, jlieskov, jvymazal, lkundrak, mah.darade, rsroka, tosykora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-02 08:30:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Claude Frantz 2017-11-02 08:23:55 UTC

Description of problem:
systemd is not able to start the service

Version-Release number of selected component (if applicable):
rsyslog-8.30.0-3.fc26.i686
rsyslog-mmjsonparse-8.30.0-3.fc26.i686

How reproducible:
always

Steps to Reproduce:
1. systemctl start rsyslog.service
2.
3.

Actual results:

-- Unit rsyslog.service has begun starting up.
Nov 02 07:52:03 defi systemd[1]: rsyslog.service: Main process exited, code=exited, status=127/n/a
Nov 02 07:52:03 defi systemd[1]: Failed to start System Logging Service.
-- Subject: Unit rsyslog.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit rsyslog.service has failed.


Expected results:
successful start

Additional info:
downgrading using dnf installs a version which is running well.

Comment 1 Radovan Sroka 2017-11-02 08:30:43 UTC


*** This bug has been marked as a duplicate of bug 1508359 ***