+++ 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: 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:
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):
on every reboot
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
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 ---
--- 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.
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.
> As for the "watch" error, please edit your /etc/selinux/restorecond.conf
> (paths to be watched) accordingly.
I tried today's rhel74.nightly:
[root@localhost ~]# systemctl restart restorecond
[root@localhost ~]# systemctl status restorecond
● restorecond.service - Restorecon maintaining path file context
Loaded: loaded (/usr/lib/systemd/system/restorecond.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2017-02-14 15:05:36 CET; 2s ago
Process: 9922 ExecStart=/usr/sbin/restorecond (code=exited, status=0/SUCCESS)
Main PID: 9923 (restorecond)
Feb 14 15:05:36 localhost.localdomain systemd: Starting Restorecon maintaining path file context...
Feb 14 15:05:36 localhost.localdomain restorecond: Unable to watch (/root/.ssh/*) No such file or directory
Feb 14 15:05:36 localhost.localdomain systemd: Started Restorecon maintaining path file context.
[root@localhost ~]# rpm -qf /usr/lib/systemd/system/restorecond.service
Note that we fixed only `restorecond: terminated` part.
If you see messages like `restorecond: 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.