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 1507151 - rsyslog8 service starts before the start of network service during boot
Summary: rsyslog8 service starts before the start of network service during boot
Keywords:
Status: CLOSED DUPLICATE of bug 1401456
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rsyslog
Version: 7.4
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Radovan Sroka
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-27 20:15 UTC by Akshay Jain
Modified: 2021-06-10 13:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-30 09:32:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Akshay Jain 2017-10-27 20:15:21 UTC
Description of problem:
rsyslog8 service starts before the start of network service during boot

Version-Release number of selected component (if applicable):
rsyslog-8.24.0-12.el7.x86_64

How reproducible:
Always.

Steps to Reproduce:

# systemd-analyze critical-chain rsyslog.service
rsyslog.service +322ms
└─basic.target @1.718s
  └─sockets.target @1.718s
    └─rpcbind.socket @1.717s
      └─sysinit.target @1.695s

# systemd-analyze critical-chain network.target
network.target @10.749s
└─network.service @10.180s +567ms
  └─NetworkManager.service @4.100s +235ms
    └─firewalld.service @2.011s +2.087s
      └─basic.target @1.718s


Actual results:

rsyslog8 service starts before the start of network service during boot

Expected results:

Rsyslog should start after network service is started


Additional info:

Earlier it was fixed in rsyslog7  version.

https://bugzilla.redhat.com/show_bug.cgi?id=1263853

Comment 2 Radovan Sroka 2017-10-30 09:32:42 UTC
Closing as duplicate of rhbz#1401456.

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


Note You need to log in before you can comment on or make changes to this bug.