Moving to systemd has meant that most of my shutdowns are incredibly fast. For approximately one in five or six, however, I get a timeout as cronie is not killed.
This is the relevant excerpt and it is always the same:
[60036.311517] systemd: cronie.service stopping timed out (2). Killing. [60036.311794] systemd: cronie.service changed final-sigterm -> final-sigkill [60036.311810] systemd: Running GC... [60036.313842] systemd: Received SIGCHLD from PID 21147 (python2). [60036.313883] systemd: Got SIGCHLD for process 21147 (python2) [60036.313959] systemd: Child 21147 died (code=killed, status=9/KILL) [60036.314851] systemd: Accepted connection on private bus. [60036.315074] systemd: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent [60036.317625] systemd: cronie.service: cgroup is empty [60036.317641] systemd: cronie.service changed final-sigkill -> failed [60036.317688] systemd: Job cronie.service/stop finished, result=done [60036.317830] systemd: Unit cronie.service entered failed state.
I have a cron job that runs every three minutes to check mail, and I wonder if this job running coincident with shutdown is what causes the time out.
Has anyone else seen this happening with the cronie.service?
I use systemd and cronie (no custom cron jobs) and there's no mention at all of cronie.service in almost a month of logs.
Sorry I can't help more, but just to reaffirm what smudge is saying, I use cronie and I have a few custom cron jobs, one of which is a (coincidentally) 3 minute check of my mail. I too see nothing in my past few weeks of logs, and have not experienced any shutdown delay.
Thanks WonderWoofy: that is both helpful and dispiriting
I wonder if it is the nature of the cron job that is the issue, not the scheduling.
I run offlineimap using this daemon script from the wiki and this in my crontab:
*/3 * * * * exec /usr/local/bin/start_daemon -n19 -c2 -p7 python2 /usr/bin/offlineimap &>/dev/null
I'll play around with that and see if it makes a difference.
As a side note, debugging shutdown's puts you on quite a slow test cycle...
I know what you mean with the slow test cycle. About three weeks after switching to systemd, my computer now reboots rather than shutting down. But it is slightly different than normal reboot, pausing briefly before starting back up. So I found on freedesktop.org how to debug late shutdown using system-shutdown. See here:
Unfortunately, after a couple days I could not figure out how to debug my problem as late as it is, since it is apparently happening after this debug hack. So I just gave up because my system runs otherwise totally normally. I tested a base arch install on both usb and spare hdd space, and it operates totally normally, so it must me my install.
In any case, I hope that helps weed out your issue though. My 3-minute call to offlineimap is way simpler. I didn't see the need to ionice it and all that, so I just used patrick brisbin's cron job.
#!/bin/bash read -r pid < ~/.offlineimap/pid if ps $pid &>/dev/null; then echo "offlineimap ($pid): another instance running." >&2 kill -9 $pid fi offlineimap -o -u quiet 2>/dev/null &
It throws some python errors sometimes, which end up in journalctl, but I don't know enough about python to debug it. Another instance of "well it works... I'll fix it later..."
Cool: I'll swap brisbin's script in to my crontab and see if that makes any difference. Might take a week or so to gather any conclusive evidence
Not even. Hung last night. So I guess I can rule out the mail fetching cron job.
I'm not sure what else could be causing cronie to not die gracefully. Meh. It's only one shutdown a week or so.
Just out of pure curiosity, how often do you shut down?
Hey, I am not judging you. I can agree with that scenerio. I just got a msata ssd about a month ago, and that coupled with systemd, my boot time is rediculous. So I often shut down rather than hibernate when taking my laptop around. It is actually faster to simply reboot, though I of course then have to reopen whatever I was working on. But that is really not a big deal.