Bug 1379638 - rsyslog does not start remote logging at boot
Summary: rsyslog does not start remote logging at boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rsyslog
Version: 24
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jiří Vymazal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-27 09:30 UTC by Alvin
Modified: 2018-05-29 21:17 UTC (History)
7 users (show)

Fixed In Version: rsyslog-8.25.0-2.fc24 rsyslog-8.25.0-2.fc25
Clone Of:
Environment:
Last Closed: 2017-03-13 23:50:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1263853 0 medium CLOSED rsyslog.service unit file should contain After=network.target 2023-03-24 13:37:29 UTC

Internal Links: 1263853 1401456

Description Alvin 2016-09-27 09:30:45 UTC
Description of problem:
Remote log server does not receive logs

Version-Release number of selected component (if applicable):
rsyslog 8.12.0, release 3.fc24

Steps to Reproduce:
1. Have rsyslog log to a remote host (*.* @loghost)
2. Reboot client

Actual results:
loghost will not receive logs after the client has booted

Additional info:
rsyslog is active after boot (systemctl status rsyslog.service)
restarting rsyslog.service will start remote logging and can be used as a workaround.

Comment 1 Jiří Vymazal 2017-01-17 14:07:40 UTC
verified with rsyslog-8.24.0 and remote logging after client reboot works

Comment 2 Fedora Update System 2017-03-02 13:22:20 UTC
rsyslog-8.25.0-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-d2d16edab7

Comment 3 Fedora Update System 2017-03-02 13:22:53 UTC
rsyslog-8.25.0-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-92e2b77ddc

Comment 4 Fedora Update System 2017-03-03 04:53:45 UTC
rsyslog-8.25.0-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-d2d16edab7

Comment 5 Fedora Update System 2017-03-03 05:24:23 UTC
rsyslog-8.25.0-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-92e2b77ddc

Comment 6 Fedora Update System 2017-03-13 23:50:42 UTC
rsyslog-8.25.0-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2017-03-13 23:54:53 UTC
rsyslog-8.25.0-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2017-03-14 02:21:12 UTC
rsyslog-8.25.0-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Karamjeet 2018-05-29 21:17:41 UTC
(In reply to Jiří Vymazal from comment #1)
> verified with rsyslog-8.24.0 and remote logging after client reboot works

I am seeing similar behavior to this in 8.35.0-2.el6

I am using imfile to read a logfile and omprog to send the log to a remote centralized log location.

After rebooting, the logs are not sent, but once the rsyslog service is restarted the logs resume sending immediately.


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