| Summary: | default cron.d/0hourly fails for run-parts | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul <pnewell0705> |
| Component: | crontabs | Assignee: | Marcela Mašláňová <mmaslano> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | bugs.michael, mmaslano, tmraz |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-03 09:28:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
*** This bug has been marked as a duplicate of bug 540477 *** Michael: Thanks for checking this out ... I did a bug search on the above mentioned cron, crontab, whatever or run-parts before submitting this and it never occurred to me to search for "hourly". Apologies. Paul |
Description of problem: A default full installation of f14 x86_64 gives a /etc/cron.d/0hourly file whose job fails. The default /etc/crod.d0/hourly is: SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root 01 * * * * root run-parts /etc/cron.hourly The mail in /var/spool/mail/root shows that it failed: === From root Sat Jul 2 21:01:01 2011 Return-Path: <root> Received: from localhost.localdomain (yoyo [127.0.0.1]) by localhost.localdomain (8.14.4/8.14.4) with ESMTP id p63411DS002589 for <root>; Sat, 2 Jul 2011 21:01:01 -0700 Received: (from root@localhost) by localhost.localdomain (8.14.4/8.14.4/Submit) id p63411MU002587; Sat, 2 Jul 2011 21:01:01 -0700 Date: Sat, 2 Jul 2011 21:01:01 -0700 Message-Id: <201107030401.p63411MU002587> From: root (Cron Daemon) To: root Subject: Cron <root@yoyo> run-parts /etc/cron.hourly Content-Type: text/plain; charset=UTF-8 Auto-Submitted: auto-generated X-Cron-Env: <SHELL=/bin/bash> X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin> X-Cron-Env: <MAILTO=root> X-Cron-Env: <HOME=/root> X-Cron-Env: <LOGNAME=root> X-Cron-Env: <USER=root> /etc/cron.hourly/mcelog.cron: read: No such device === As this is the default that one gets on a fresh install, it shouldn't fail! I can't tell if it is a problem with cron, crontab, whatever or run-parts or something else. As I am having problems getting my own cron job to run, I really need to know that the default from a fresh install works "out of the box". Thank you in advance, Paul Version-Release number of selected component (if applicable): How reproducible: Check /var/spool/mail/root after hourly cron job is run to see problem Steps to Reproduce: 1. Wait until the clock is "on the hour" and 0hourly runs 2. In a terminal window, su -l and see the "You have new mail" message 3. Read the last mail from cron Actual results: Errors in execution Expected results: No errors in execution Additional info: Please let me know what else I can give to help