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:
In RHEL 7.4 rsyslog-8.24.0-12.el7.x86_64 starts before network.target during boot, so if rsyslog is configured to send logs to remote server on boot it will log locally however remote login will not work and as a workaround you need to manually restart the rsyslog service

Version-Release number of selected component (if applicable):

RHEL 7.4, rsyslog-8.24.0-12.el7.x86_64 

How reproducible:
always


Steps to Reproduce:
1. edit rsyslog.conf to send logs to central rsyslog server.
2. on central rsyslog server make changes to accept TCP traffic
3. take reboot of client system
4. you will notice rsyslog logs locally however it fails to log to central log server.

rsyslog starts befor network.target this can be verified using below-
# systemd-analyze critical-chain rsyslog.service
## systemd-analyze plot > plot.svg     

Actual results:

rsyslog logs locally but not to central syslog server after boot

Expected results:

rsyslog should log locally as well as to central syslog server after boot


Additional info:

Closing as duplicate of rhbz#1401456.

*** This bug has been marked as a duplicate of bug 1401456 ***