Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1264505 +++
Description of problem:
On every reboot, restorecond logs this error message to syslog:
`restorecond[695]: Unable to watch (/root/.ssh/*) No such file or directory`
And /root/.ssh/ doesn't exist. I don't think restorecond should throw an error in this case. I find it completely normal to not have a /root/.ssh/ folder thus restorecon should not even warn about that.
When restorecond is receiving a SIGTERM (e.g. on shutdown) it throws an error too:
`restorecond[709]: terminated`
I don't see why this should be an error message. If you need this message at all, a INFO loglevel should be enough.
Version-Release number of selected component (if applicable):
policycoreutils-restorecond-2.3-18.fc22.x86_64
policycoreutils-restorecond-2.3-17.fc22.x86_64
How reproducible:
on every reboot
Additional info:
restorecond might throw more errors, I haven't tested the whole codebase.
--- Additional comment from Fedora End Of Life on 2016-07-19 19:56:47 CEST ---
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
--- Additional comment from Christian Stadelmann on 2016-07-20 13:31:14 CEST ---
Still present.
--- Additional comment from Vit Mojzis on 2017-01-05 12:39:00 CET ---
Thank you for reporting the issue.
There is a pull request to decrease loglevel of the termination message.
https://github.com/fedora-selinux/selinux/pull/36
As for the "watch" error, please edit your /etc/selinux/restorecond.conf (paths to be watched) accordingly.
--- Additional comment from Christian Stadelmann on 2017-01-17 00:43:49 CET ---
(In reply to Vit Mojzis from comment #3)
> Thank you for reporting the issue.
> There is a pull request to decrease loglevel of the termination message.
> https://github.com/fedora-selinux/selinux/pull/36
>
> As for the "watch" error, please edit your /etc/selinux/restorecond.conf
> (paths to be watched) accordingly.
Thank you!
Note that we fixed only `restorecond[709]: terminated` part.
If you see messages like `restorecond[695]: Unable to watch (/root/.ssh/*) No such file or directory` please change your configuration in /etc/selinux/restorecond.conf
Changing the default during a product lifecycle could introduce regressions on users systems.
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, 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-2017:1883