Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1361919

Summary: shutdown from cron job results in segfault from systemd-logind
Product: [Fedora] Fedora Reporter: bruce.fleming
Component: systemdAssignee: systemd-maint
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 24CC: johannbg, lnykryn, msekleta, muadda, ssahani, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-02 04:43:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Includes select lines from dmesg (at top) and cron at the bottom. none

Description bruce.fleming 2016-07-31 23:28:04 UTC
Created attachment 1186195 [details]
Includes select lines from dmesg (at top) and cron at the bottom.

Description of problem:


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


How reproducible: Always


Steps to Reproduce:
1.create cron job to shutdown with time field.  here is what I used
00 22 * * * /usr/sbin/shutdown -P +2
2.Wait for the cron job to execute
3.

Actual results:Immediately (at 22:00) drops back to login screen instead of shutting down


Expected results:System issues warning message and then after 2 minutes powers off the system.


Additional info: This started happening with recent upgrade to F24.  I also found a reference to this for Ubuntu but not Fedora (https://github.com/systemd/systemd/issues/2796).  The results look identical to this referenced bug.

Comment 1 bruce.fleming 2016-11-02 04:43:41 UTC
the latest version os systemd has resolved the issue on my system