Bug 2074318

Summary:	rsyslog starts before the network service during boot
Product:	Red Hat Enterprise Linux 9	Reporter:	Dalibor Pospíšil <dapospis>
Component:	rsyslog	Assignee:	Attila Lakatos <alakatos>
Status:	CLOSED ERRATA	QA Contact:	Dalibor Pospíšil <dapospis>
Severity:	low	Docs Contact:
Priority:	low
Version:	9.0	CC:	dapospis, jb2592, jfaison, rsroka
Target Milestone:	rc	Keywords:	AutoVerified, Patch, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rsyslog-8.2102.0-115.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1401456	Environment:
Last Closed:	2023-11-07 08:33:06 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 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