On 05-11-14 20:14, Javier Vasquez wrote:
On Wed, Nov 5, 2014 at 12:22 AM, Kyle Terrien <kyleterrien@gmail.com> wrote:
On 11/04/2014 07:50 PM, Javier Vasquez wrote: I noticed org.cups.cupsd.service just fails:
% systemctl status org.cups.cupsd.service ● org.cups.cupsd.service - CUPS Scheduler Loaded: loaded (/usr/lib/systemd/system/org.cups.cupsd.service; enabled) Active: failed (Result: exit-code) since Tue 2014-11-04 21:24:58 CST; 8min ago Main PID: 7988 (code=exited, status=1/FAILURE) ...
% journalctl -u org.cups.cupsd.service ... -- Reboot -- Nov 04 21:06:59 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:06:59 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:07:05 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:07:05 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. ...
if I run cupsd directly:
% sudo cupsd cupsd: Child exited with status 1 ...
Does /var/log/cups/error_log say anything?
No, it's empty:
% cat /var/log/cups/error_log %
Hi Javier, like you I also had the same problem you are experiencing. But after changing the LogLevel in /etc/cups/cupsd.conf to: LogLevel debug I saw what the real problem was in /var/log/cups/error_log: [05/Nov/2014:20:35:50 +0100] Group and SystemGroup cannot use the same groups. Next I changed SystemGroup in /etc/cups/cups-files.conf which was: SystemGroup sys root lp to: SystemGroup sys root In /etc/cups/cups-files.conf Groups is commented out so this will default to 'lp'. After changing this I was able to start the cupsd again. Hope this helps, -Lex