You are not logged in.
Pages: 1
from time to time, starting of cupsd fails here and I have no idea why:
[root@arch64-1]# systemctl status cups
cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: failed (Result: core-dump) since Di 2013-09-03 21:12:38 CEST; 4min 19s ago
Process: 948 ExecStart=/usr/bin/cupsd -f (code=dumped, signal=ABRT)
Sep 03 21:12:38 arch64-1.xxx systemd[1]: Starting CUPS Printing Service...
Sep 03 21:12:38 arch64-1.xxx systemd[1]: Started CUPS Printing Service.
Sep 03 21:12:38 arch64-1.xxx cupsd[948]: cupsd: simple-watch.c:299: destroy_timeout: Assertion `*_head == _item' failed.
Sep 03 21:12:38 arch64-1.xxx systemd-coredump[951]: Process 948 (cupsd) dumped core.
Sep 03 21:12:38 arch64-1.xxx systemd[1]: cups.service: main process exited, code=dumped, status=6/ABRT
Sep 03 21:12:38 arch64-1.xxx systemd[1]: Unit cups.service entered failed state.A restart might work - or not.
How can I find the reason for this?
Offline
I have not experienced this, but I also don't use the cups.service directly. Insetad I have it autostarted on access with the cups.socket. I wonder if starting it only when it is needed will help its success…
There is also the cups.path, which watches for /var/spool/cups/d* and starts is if there is anything that matches that glob. But I have never used this, as I noticed that there is the creation of some of these files on my system whether or not I am currently printing.
Offline
Pages: 1