FS#36183 - icecream 20130220-2: daemon exits on startup
Attached to Project:
Arch Linux
Opened by Shawn Rutledge (ecloud) - Wednesday, 17 July 2013, 13:07 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 27 July 2013, 01:18 GMT
Opened by Shawn Rutledge (ecloud) - Wednesday, 17 July 2013, 13:07 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 27 July 2013, 01:18 GMT
|
Details
Description:
# systemctl start icecream # systemctl status icecream icecream.service - icecream worker Loaded: loaded (/usr/lib/systemd/system/icecream.service; enabled) Active: failed (Result: exit-code) since Wed 2013-07-17 14:47:15 CEST; 2s ago Process: 12153 ExecStart=/usr/lib/icecream/icecreamd (code=exited, status=0/SUCCESS) Main PID: 12156 (code=exited, status=1/FAILURE) #!/bin/bash CGroup: name=systemd:/system/icecream.service Jul 17 14:47:15 str systemd[1]: Started icecream worker. Jul 17 14:47:15 str systemd[1]: icecream.service: main process exited, code=exited, status=1/FAILURE Jul 17 14:47:15 str systemd[1]: Unit icecream.service entered failed state. It does not put anything new into the log file. I tried changing /usr/lib/icecream/icecreamd to echo the options to iceccd, then running it with those options, and iceccd is just exiting right away, even without the -d (daemonize). I switched to icecream-git for now, it's working again. |
This task depends upon
Closed by Dave Reisner (falconindy)
Saturday, 27 July 2013, 01:18 GMT
Reason for closing: None
Additional comments about closing: The AUR is unsupported.
Saturday, 27 July 2013, 01:18 GMT
Reason for closing: None
Additional comments about closing: The AUR is unsupported.
Error: no icecc user on system. Falling back to nobody. Success
but that's not the reason. Tried adding the icecc user just in case. If it's normal for there to be an icecc user, maybe the package can add it? Otherwise using nobody seems reasonable enough.