Bug 1509981
| Summary: | Upgrading from Fedora 25 to Fedora 26 leaves rsyslog or possibly other syslog service disabled | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | blah <nembard> |
| Component: | rsyslog | Assignee: | Jiří Vymazal <jvymazal> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 26 | CC: | dkopecek, jlieskov, jvymazal, lkundrak, mah.darade, rsroka |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rsyslog-8.35.0-2.fc26 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-26 22:11:30 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: | |||
My initial guess is that systemd was updated to include a 'syslog' target which starts one or another actual syslog implementations, and that the issue here is not that rsyslog is not wanted by a runlevel target, but that no runlevel target is wanting the syslog target, and additionally that the syslog target is not wanting the selected syslog implementation (rsyslog in this case). Unfortunately I have no other fc25 systems available to inspect or compare to. apologies for not setting a priority when submitting the bug, this is low priority, and is fixed (if noticed) by: $> systemctl enable rsyslog rsyslog-8.34.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-5a5737c203 rsyslog-8.34.0-1.fc26 has been pushed to the Fedora 26 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-2018-5a5737c203 This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. rsyslog-8.35.0-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-fdbccdf76c rsyslog-8.35.0-2.fc26 has been pushed to the Fedora 26 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-2018-fdbccdf76c rsyslog-8.35.0-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: After upgrading from Fedora 25 to Fedora 26, I found my rsyslog service was not started and not enabled (and not wanted by any target). This does not appear to affect all upgrades even on very similar systems. Version-Release number of selected component (if applicable): old rsyslog version: unknown (fc25) new rsyslog version: rsyslog-8.30.0-3.fc26.x86_64 old systemd version: unknown new systemd version: systemd-233-7.fc26.x86_64 old dnf-plugin-systemd version: unknown new python3-dnf-plugin-system-upgrade version: python3-dnf-plugin-system-upgrade-2.0.3-1.fc26.noarch How reproducible: Upgrading to Fedora 26 from a Fedora 25 installation with rsyslog enabled (upgrade system used was 'dnf system-upgrade' Steps to Reproduce: 1. From a Fedora 25 installation, install and enable rsyslog i.e. dnf install rsyslog systemctl enable rsyslog 2. Upgrade the system to Fedora 26 ie. dnf system-upgrade download --releasever=26 dnf system-upgrade reboot 3. Check the syslog service: systemctl | egrep syslog find /etc/systemd/ /usr/lib/systemd/ -iwholename "*syslog*" -print -exec ls -l '{}' ';' Actual results: The rsyslog package is installed but is not enabled. # find /etc/systemd/ /usr/lib/systemd/ -iwholename "*syslog*" -print -exec ls -l '{}' ';' /etc/systemd/system/syslog.service lrwxrwxrwx. 1 root root 39 Nov 5 16:27 /etc/systemd/system/syslog.service -> /usr/lib/systemd/system/rsyslog.service /usr/lib/systemd/system/syslog.socket -rw-r--r--. 1 root root 1235 Oct 26 22:23 /usr/lib/systemd/system/syslog.socket /usr/lib/systemd/system/syslog.target.wants total 0 /usr/lib/systemd/system/rsyslog.service -rw-r--r--. 1 root root 360 Oct 25 22:25 /usr/lib/systemd/system/rsyslog.service Expected results: The expected results should include a /etc/systemd/system/<runlevel-name>.target.wants/rsyslog.service symlink, as shown in the following after re-enabling the service via 'systemctl enable rsyslog' : # find /etc/systemd/ /usr/lib/systemd/ -iwholename "*syslog*" -print -exec ls -l '{}' ';' /etc/systemd/system/multi-user.target.wants/rsyslog.service lrwxrwxrwx. 1 root root 39 Nov 7 00:18 /etc/systemd/system/multi-user.target.wants/rsyslog.service -> /usr/lib/systemd/system/rsyslog.service /etc/systemd/system/syslog.service lrwxrwxrwx. 1 root root 39 Nov 5 16:27 /etc/systemd/system/syslog.service -> /usr/lib/systemd/system/rsyslog.service /usr/lib/systemd/system/syslog.socket -rw-r--r--. 1 root root 1235 Oct 26 22:23 /usr/lib/systemd/system/syslog.socket /usr/lib/systemd/system/syslog.target.wants total 0 /usr/lib/systemd/system/rsyslog.service -rw-r--r--. 1 root root 360 Oct 25 22:25 /usr/lib/systemd/system/rsyslog.service Additional info: I have upgraded three systems from fc25 to fc26, and this has only affected one out of the three. The rsyslog service was definitely enabled prior to the upgrade, was always started on boot, and my rsyslog log files are present up to the time I performed the upgrade. I'm unable to find a log file containing the prior versions of rsyslog, dnf-plugin-system-upgrade, or systemd, but I'm happy to add more information if I can find a log from the system upgrade.