Bug 1012420 - Cronie doesn't work when is executed as stand alone without systemd (for debuging issues)
Summary: Cronie doesn't work when is executed as stand alone without systemd (for debu...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cronie
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marcela Mašláňová
QA Contact: Jakub Prokes
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-26 12:47 UTC by Jakub Prokes
Modified: 2014-06-18 08:24 UTC (History)
0 users

Fixed In Version: cronie-1.4.11-5.el7
Doc Type: Bug Fix
Doc Text:
Cause: crond -n fails. Consequence: crond -n doesn't work the same way as it used to work. It's needed to change PAM setting. Fix: Man page now contain explanation: "The crond -n is useful for starting it out of init. With this option is needed to change pam setting. In /etc/pam.d/crond must not enable pam_loginuid.so module." Result: Man page informs user.
Clone Of:
Environment:
Last Closed: 2014-06-13 11:12:24 UTC
Target Upstream Version:

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

Description Jakub Prokes 2013-09-26 12:47:24 UTC 
Description of problem:
When is crond executed directly from command line any non root cronjob isn't executed.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. systemctl stop crond.service
2. create cronjob for common user
3. execute command: /usr/sbin/crond -n -x sch

Actual results:
Debug output contains:
log_it: (jenicek 29208) PAM ERROR (Cannot make/remove an entry for the specified session)
log_it: (jenicek 29208) FAILED to open PAM security session (Cannot make/remove an entry for the specified session)

and cronjob for "jenicek" isn't executed


Expected results:
Cron jobs will work same as system service.


Additional info:
It could be good to know, how to execute crond for debugin purposes on system with systemd.
Comment 2 Marcela Mašláňová 2013-09-26 13:24:52 UTC 
I would fix it by change of man page.

The crond -n is useful for starting it out of init. With this option is needed to change pam setting. In /etc/pam.d/crond must not enable pam_loginuid.so module.

It does work for me with this setting.
Comment 5 Ludek Smid 2014-06-13 11:12:24 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.