I recently started having a problem where about 75% of the time cups will not start. The web interface (cups-browsed) starts fine, but not the main cups server process (cupsd).
Dmesg shows that it was killed, but there is no more information
I check the running processes and confirm that cupsd is not running:
I can then launch cupsd manually from a command prompt and it will start and work fine without errors:
This happens most of the time, but not all of the time. My best guess is that it is some sort of timing issue with startup services, but I am not really sure where to look.
Dmesg shows that it was killed, but there is no more information
Code:
$ dmesg | grep cups [ 36.509001] init: cups main process (1304) killed by HUP signal [ 36.509014] init: cups main process ended, respawning [ 38.324324] audit: type=1400 audit(1424799911.058:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cups-browsed" pid=1548 comm="apparmor_parser"
Code:
$ ps -A | grep cups 1559 ? 00:00:00 cups-browsed
Code:
$ sudo cupsd $ ps -A | grep cups 1559 ? 00:00:00 cups-browsed 3893 ? 00:00:00 cupsd
Comment