I installed yum-cron on my CentOS 7 VM, but decided I did not need it to run hourly. So I tried to rename, and later completely remove, /etc/cron.hourly/0yum-hourly and /etc/yum/yum-cron-hourly.conf. However, for weeks now I've been getting the following emails hourly:


Error reading config file: /etc/yum/yum-cron-hourly.conf

Except I have guaranteed that the file /etc/cron.hourly/0yum-hourly.cron.old no longer exists, in any form or by any name; the file has been deleted. I have restarted the crond and yum-cron services, yet the problem persists. Why (or perhaps more importantly, how) does cron keep insisting on running a job that no longer exists?


3 Answers 3


You did not delete 0yum-hourly.cron; you renamed it to an .old file that is still being executed.

Any scripts under /etc/cron.hourly will be executed hourly, so you have to remove the file or move it to a backup directory for cron to stop executing it.

  • 1
    From my original post: "I have guaranteed that the file /etc/cron.hourly/0yum-hourly.cron.old no longer exists; the only places any 0yum* file exists is in cron.daily, and my home directory." The file has been deleted.
    – ionothanus
    Commented Jun 1, 2018 at 1:21
  • The evidence suggests otherwise. Did you restart cron AFTER deleting this file? What do your logs say?
    – symcbean
    Commented Aug 2, 2023 at 15:28

You said that you deleted (or in the case of the latter, possibly renamed) the files:


Your error message says:

Error reading config file: /etc/yum/yum-cron-hourly.conf

From what I can surmise, the yum-cron service is still running but the conf file either doesn't exist or is named something else.

You will either need to stop the service or restore /etc/yum/yum-cron-hourly.conf. If you don't need yum-cron anymore then you can just uninstall it after stopping the service.


The cron utility does not "run from" /etc/cron.hourly rather it pulls its configuration from each of the /etc/cron.* directories. I would examine the cron server invocation script to see what options are being used and reconfigure the startup of cron as necessary.

Which startup file to look at depends on if you are using /etc/init.d or systemd or whatever.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .