Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
# find /mnt/chroot/
/mnt/chroot/
/mnt/chroot/dev
/mnt/chroot/dev/log
/mnt/chroot/lib64
/mnt/chroot/lib64/libdl.so.2
/mnt/chroot/lib64/libc.so.6
/mnt/chroot/lib64/ld-linux-x86-64.so.2
/mnt/chroot/lib64/libtinfo.so.5
/mnt/chroot/lib64/libselinux.so.1
/mnt/chroot/lib64/libcap.so.2
/mnt/chroot/lib64/libacl.so.1
/mnt/chroot/lib64/libpcre.so.1
/mnt/chroot/lib64/liblzma.so.5
/mnt/chroot/lib64/libattr.so.1
/mnt/chroot/lib64/libpthread.so.0
/mnt/chroot/bin
/mnt/chroot/bin/bash
/mnt/chroot/bin/logger
/mnt/chroot/bin/ls
# grep /mnt/chroot/dev/log /etc/rsyslog.conf
input(type="imuxsock" HostName="chroot" Socket="/mnt/chroot/dev/log" CreatePath="on")
# systemctl restart rsyslog
# chroot /mnt/chroot/
bash-4.2# /bin/logger this is a chroot log test
bash-4.2# exit
# grep "this is a chroot log test" /var/log/messages
Jan 21 10:57:08 plautrba-rhel-7 logger: this is a chroot log test
I believe there should be "chroot" instead of "plautrba-rhel-7" in the log line.
Version-Release number of selected component (if applicable):
rsyslog-7.4.7-7.el7_0.x86_64
How reproducible:
always
Reproduced.
I've tried a variety of versions and the behavior is pretty inconsistent.
- rsyslog-5.8.10-10.el6_6
old syntax - works as expected
- rsyslog7-7.4.10-3.el6_6
old syntax - strange bug with mangled hostname
new syntax - works as expected
- rsyslog-7.4.7-6.el7.x86_64
old syntax - strange bug with mangled hostname
new syntax - doesn't change hostname
- rsyslog-7.4.10-3.fc20.x86_64
old syntax - doesn't change hostname
new syntax - works as expected
@QE:
I guess it'd be good to test both syntaxes. Here are the respective configurations:
--- 8< ---
module(load="imuxsock" syssock.use="on" syssock.name="/tmp/rs.sock.sys")
input(type="imuxsock" hostname="chroot" socket="/tmp/rs.sock.chroot")
--- 8< ---
$Modload imuxsock
$SystemLogSocketName /tmp/rs.sock.sys
$InputUnixListenSocketHostName chroot
$AddUnixListenSocket /tmp/rs.sock.chroot
--- 8< ---
setenforce 0
systemctl restart rsyslog
logger -du /tmp/rs.sock.chroot harharhar
grep harharhar /var/log/messages
- rsyslog-8.8.0-3.fc23.x86_64
old syntax - strange bug with mangled hostname
new syntax - works as expected
This version even crashes during shutdown with the old syntax.
We should fix this before it bites somebody.
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
Description of problem: # find /mnt/chroot/ /mnt/chroot/ /mnt/chroot/dev /mnt/chroot/dev/log /mnt/chroot/lib64 /mnt/chroot/lib64/libdl.so.2 /mnt/chroot/lib64/libc.so.6 /mnt/chroot/lib64/ld-linux-x86-64.so.2 /mnt/chroot/lib64/libtinfo.so.5 /mnt/chroot/lib64/libselinux.so.1 /mnt/chroot/lib64/libcap.so.2 /mnt/chroot/lib64/libacl.so.1 /mnt/chroot/lib64/libpcre.so.1 /mnt/chroot/lib64/liblzma.so.5 /mnt/chroot/lib64/libattr.so.1 /mnt/chroot/lib64/libpthread.so.0 /mnt/chroot/bin /mnt/chroot/bin/bash /mnt/chroot/bin/logger /mnt/chroot/bin/ls # grep /mnt/chroot/dev/log /etc/rsyslog.conf input(type="imuxsock" HostName="chroot" Socket="/mnt/chroot/dev/log" CreatePath="on") # systemctl restart rsyslog # chroot /mnt/chroot/ bash-4.2# /bin/logger this is a chroot log test bash-4.2# exit # grep "this is a chroot log test" /var/log/messages Jan 21 10:57:08 plautrba-rhel-7 logger: this is a chroot log test I believe there should be "chroot" instead of "plautrba-rhel-7" in the log line. Version-Release number of selected component (if applicable): rsyslog-7.4.7-7.el7_0.x86_64 How reproducible: always