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 2074318 - rsyslog starts before the network service during boot
Summary: rsyslog starts before the network service during boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rsyslog
Version: 9.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Attila Lakatos
QA Contact: Dalibor Pospíšil
URL:
Whiteboard:
: 2170487 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-12 01:03 UTC by Dalibor Pospíšil
Modified: 2023-11-07 09:49 UTC (History)
4 users (show)

Fixed In Version: rsyslog-8.2102.0-115.el9
Doc Type: No Doc Update
Doc Text:
Clone Of: 1401456
Environment:
Last Closed: 2023-11-07 08:33:06 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-118617 0 None None None 2022-04-12 01:10:35 UTC
Red Hat Issue Tracker SECENGSP-4493 0 None None None 2022-04-12 01:10:38 UTC
Red Hat Product Errata RHBA-2023:6444 0 None None None 2023-11-07 08:33:22 UTC

Description Dalibor Pospíšil 2022-04-12 01:03:14 UTC 
+++ This bug was initially created as a clone of Bug #1401456 +++

Description of problem:
When the server boots, rsyslog can't resolve an FQDN used in the config to forwared messages to.

Version-Release number of selected component (if applicable):
rsyslog-8.2102.0-101.el9

How reproducible:
always

Steps to Reproduce:
1. Add config file in rsyslog.d to forward messages to a remote server (TCP or UDP, doesn't matter). Use the remote server FQDN. For example: "*.info        @remote.server.com"
2. Restart rsyslog service. Test if messages are forwarded. This should be OK.
3. Reboot the server. Test if messages are forwarded. This fails because during boot, when rsyslog config was read, it could not yet resolve the FQDN.
4. Restart rsyslog service. Forwarding will now work again, since it could resolve the FQDN.

Actual results:
FQDN used in rsyslog configuration can't be resolved during boot.

Expected results:
FQDN used in rsyslog configuration should be resolved during boot.

Additional info:
This will depend on the startup order of rsyslog in systemd environment (network not yet available).
I opened a ticket for RH support. They advised to use the IP address. This works indeed. But, this could not always be possible though (eg. FQDN pointing to redundant IP's). And having to use the IP is nowhere mentioned in man pages or rsyslog documentation as a requirement (use of fqdn is also shown in examples).
I think this worked before in RHEL7 (but not 100% sure - could depend on when the service started before).
This works in RHEL6, because not dependant on systemd.
Maybe the rsyslog unit should depend on network to solve this?
Comment 1 Attila Lakatos 2022-09-01 13:52:07 UTC 
The solution is to make rsyslog.service have explicit dependencies and ordering on both network.target and network-online.target.
We are missing the following lines from the service file:
  Wants=network.target network-online.target
  After=network.target network-online.target
Comment 2 Dalibor Pospíšil 2023-03-22 15:41:31 UTC 
*** Bug 2170487 has been marked as a duplicate of this bug. ***
Comment 16 errata-xmlrpc 2023-11-07 08:33:06 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 (rsyslog bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:6444
Note You need to log in before you can comment on or make changes to this bug.