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:

Can not use logger or rsyslog logging frame work from with in a docker image. 

The following is suspected to be the issue: 

socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
connect(3, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ENOENT (No such file or directory)

Version-Release number of selected component (if applicable): 0.11 from RHEL 7 

How reproducible: VERY

Steps to Reproduce:
1. docker run -it --rm rhel /bin/bash
2. yum -y install rsyslog
3. /usr/sbin/rsyslogd
4. logger "this is a test"

Actual results:
No log message appear in /var/log/messages

Expected results:
"this is a test" should appear in the log

Additional info:

Did rsyslogd not create the device?

(In reply to Daniel Walsh from comment #2)
> Did rsyslogd not create the device?

Nope, and when I ran an strace on rsyslog I did not see it fail in crating the device / socket.

After playing around with this for a while, I realized that rsyslog no longer listens on /dev/log by default it talks to journald, but journald is not running in your container, so you need to figure out how to get rsyslog to listen on /dev/log again.

Rsyslog guys how do I configure rsyslog to turn off journald support and back on /dev/log support?

Michal Schmidt says

In /etc/rsyslog.conf remove $ModLoad imjournal, set $OmitLocalLogging
to off and make sure $ModLoad imuxsock is present.

(In reply to Daniel Walsh from comment #5)
> Michal Schmidt says
> 
> In /etc/rsyslog.conf remove $ModLoad imjournal, set $OmitLocalLogging
> to off and make sure $ModLoad imuxsock is present.

Also comment out:
$IMJournalStateFile imjournal.state

That should be about it.

This is a misconfiguration, not a bug.