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.

Bug 1301916

Summary: Tracker bug -- 7.2.2 respin of rsyslog-docker
Product: Red Hat Enterprise Linux 7 Reporter: Eliska Slobodova <eslobodo>
Component: rsyslog-containerAssignee: Eliska Slobodova <eslobodo>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 7.2CC: ajia, dwalsh, mjenner, theinric
Target Milestone: rcKeywords: Tracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1316125 (view as bug list) Environment:
Last Closed: 2016-02-16 18:20:03 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 Eliska Slobodova 2016-01-26 11:37:31 UTC
Tracking the 7.2.2 respin of the rsyslog-docker image.

Comment 3 Alex Jia 2016-02-05 10:10:51 UTC
I gave a try on rhel7/rsyslog:latest(b98636a98907), the docker run w/ interactive mode will hang forever, and I can't get a useful debug information from docker logs, when tried to type ctrl+c several times, I got error like "rsyslogd: sd_journal_get_cursor() failed: 'Cannot assign requested address'", the test steps as follows:

1. run rsyslog container

# docker run -it registry.access.redhat.com/rhel7/rsyslog
Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.


NOTE: docker run command hang forever.

2. open a new terminal window to check logs of running container

# docker ps
CONTAINER ID        IMAGE                                      COMMAND             CREATED             STATUS              PORTS               NAMES
3c0e51163d36        registry.access.redhat.com/rhel7/rsyslog   "/bin/rsyslog.sh"   41 seconds ago      Up 40 seconds                           hungry_poitras

# docker logs 3c0e51163d36

NOTE: nothing is in here.

3. back to above terminal window of step 1 and type ctrl+c several times.

^C^C^C^Crsyslogd: sd_journal_get_cursor() failed: 'Cannot assign requested address'

Comment 8 errata-xmlrpc 2016-02-16 18:20:03 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/RHEA-2016-0237.html