Re: cron is failing to run for selinux context, but everything looks fine

[Ed Greshko]

On 2020-07-29 20:29, stan via users wrote:
> On Wed, 29 Jul 2020 05:38:29 +0800
> Ed Greshko  wrote:
> > On 2020-07-29 03:23, stan via users wrote:
> > > On Tue, 28 Jul 2020 10:35:54 -0700
> > > stan via users  wrote:
> > > > Before I open a bugzilla, I wanted to check if anyone has an
> > > > explanation for this, and a fix.
> > >
> > > Opened a bugzilla,
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1861505
> >
> > Could you clarify things a bit?
>
> I'll try.
> > I still don't know what "daemon watch" is.  What package/rpm supplies
> > this?
>
> Name        : dwatch
> Version     : 0.1.1
> Release     : 18.fc31
> Architecture: x86_64
> Install Date: Mon 10 Jun 2019 08:19:26 PM MST
> Group       : Applications/System
> Size        : 43883
> License     : GPLv2+
> Signature   : (none)
> Source RPM  : dwatch-0.1.1-18.fc31.src.rpm
> Build Date  : Mon 10 Jun 2019 08:18:22 PM MST
> Build Host  : localhost
> URL         : http://siag.nu/dwatch/
> Summary     : A program that watches over other programs
> Description :
> Dwatch (Daemon Watch) is a program that watches over other programs and
> performs actions based on conditions specified in a configuration file.
> See dwatch.conf for an example of what the file might look like.
>
> Dwatch is meant to be run from cron at regular intervals.

So, dwatch is not part of Fedora.

On an F31 system...

[egreshko@f31k ~]$ dnf info dwatch
Last metadata expiration check: 0:00:33 ago on Wed 29 Jul 2020 08:49:46 PM CST.
Error: No matching Packages to list

On an F32 system...

[egreshko@meimei ~]$ dnf info dwatch
Last metadata expiration check: 4:12:49 ago on Wed 29 Jul 2020 04:35:59 PM CST.
Error: No matching Packages to list

So, where did you acquire it?
> > Also, in the BZ you say "No cron jobs run" but in the thread it
> > sounded to me as if it was only cron jobs associated with "dwatch".
> > So, which is it?
>
> As far as I can tell, no cron jobs run.  I noticed dwatch not running
> because the entropy gathering daemons weren't running.  The others run,
> but their output isn't as noticeable to me.

Well, you should easily be able to tell if the hourly cron job runs...

journalctl -b 0 | grep hourly

should return a bunch of stuff like...

Jul 29 20:01:01 meimei.greshko.com CROND[29642]: (root) CMD (run-parts /etc/cron.hourly)
Jul 29 20:01:01 meimei.greshko.com run-parts[29645]: (/etc/cron.hourly) starting 0anacron
Jul 29 20:01:01 meimei.greshko.com run-parts[29651]: (/etc/cron.hourly) finished 0anacron
> > Then, just as a troubleshoot, have you tried running the system with
> > setenforce 0?
>
> I haven't, and that is a good suggestion.  I'll reboot with
> setenforce=0 on the kernel boot line.