Bug 5535 - crond is not started at startup
Summary: crond is not started at startup
Status: RESOLVED DUPLICATE of bug 5556
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 3342
  Show dependency tree / graph
 
Reported: 2012-04-21 16:09 CEST by jean michel masereel
Modified: 2012-04-22 15:15 CEST (History)
2 users (show)

See Also:
Source RPM: cronie-1.4.8-2.mga2.src.rpm or crontabs-1.10-15.mga1.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description jean michel masereel 2012-04-21 16:09:20 CEST 
Since the update from mga1 to mga2-beta3, my scheduled tasks aren't running.
crond doesn't appears in "ps" command. crond is present in the directory /etc/rc.d/init.d/
If I launch crond manually, it is ok for the scheduled tasks. But after a reboot, crond is not running again, and it's not ok for the scheduled tasks.

>systemctl status crond.service
crond.service - Command Scheduler
          Loaded: loaded (/lib/systemd/system/crond.service; disabled)
          Active: inactive (dead)
          CGroup: name=systemd:/system/crond.service

The last entry of :/var/log/cron/info.log is from before the update to beta3.

There is already something about that in the bug : https://bugs.mageia.org/show_bug.cgi?id=4145 marked as resolved and concerning alpha3, that's the reason why I re-post a new bug.
Manuel Hiebel 2012-04-21 23:47:32 CEST

CC: (none) => dmorganec, mageia
Blocks: (none) => 3342

Comment 1 Colin Guthrie 2012-04-22 01:13:17 CEST 
I believe this happens because rpm-helper was updated after crond. Can you confirm by checking the installation date/time of the two packages:

rpm -qi cronie
rpm -qi rpm-helper

We've discussed this on the list and we'll need a solution for the final release, but if you could confirm the theory, that would be great.
Comment 2 Colin Guthrie 2012-04-22 01:14:19 CEST 
Oh and to enable it, just type "systemctl enable crond.service" and it should be started next boot (but obviously we need to solve the transition problem)
Comment 3 jean michel masereel 2012-04-22 14:54:05 CEST 
Hi,
you where right :
Name        : cronie
Version     : 1.4.8
Release     : 2.mga2
Architecture: x86_64
Install Date: jeu. 19 avril 2012 12:59:29 CEST

Name        : rpm-helper
Version     : 0.24.8
Release     : 1.mga2
Architecture: noarch
Install Date: jeu. 19 avril 2012 14:56:55 CEST

and "systemctl enable crond.service" made crond starting after reboot.
Just to mention that in mcc/system/manage system services by (dis)enabling the "at startup" box was checked... And now its status is "stopped" (despite that it is running!)
Comment 4 Colin Guthrie 2012-04-22 15:15:55 CEST 
Yeah the MMC services stuff still needs to be converted over for systemd support.. it's on my list.

Glad this is a known issue, even if there is not a tracking bug for it yet. I've opened one now bug #5556. Thanks for the report.

*** This bug has been marked as a duplicate of bug 5556 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.