Bug 1184410

Summary: rsyslog fails to create path for socket
Product: Red Hat Enterprise Linux 7 Reporter: Jakub Jelen <jjelen>
Component: rsyslogAssignee: Tomas Heinrich <theinric>
Status: CLOSED ERRATA QA Contact: Marek Marusic <mmarusic>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: mmarusic, pvrabec
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 14:30:16 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 Jakub Jelen 2015-01-21 10:21:10 UTC 
Description of problem:
rsyslog fails to create parent directory for new socket defined in config when there is specified CreatePath="on".

Version-Release number of selected component (if applicable):
rsyslog-7.4.7-7.el7_0.x86_64

How reproducible:
deterministic

Steps to Reproduce:
1. Insert new config line into /etc/rsyslog.conf
input(type="imuxsock" HostName="user" Socket="/dev/my/log" CreatePath="on")
2. systemctl restart rsyslog
3. ls /dev/my/log

Actual results:
the path is not created
/dev/my/log: No such file or directory

Expected results:
the socket with path is created.
srw-rw-rw-. 1 root root 0 Jan 21 11:18 /dev/my/log

Additional info:
When running rsyslogd from commandline with -dn, there is error about creation this socket
Works fine with RHEL6 version of rsyslog7
Comment 2 Tomas Heinrich 2015-04-11 21:59:33 UTC 
Reproduced. Should be easy to backport from the el6 version.
Comment 6 errata-xmlrpc 2015-11-19 14:30:16 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2173.html