<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Could not start printer when attempting to print on Brother on Cups server" href="https://bugs.documentfoundation.org/show_bug.cgi?id=129146#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Could not start printer when attempting to print on Brother on Cups server" href="https://bugs.documentfoundation.org/show_bug.cgi?id=129146">bug 129146</a> from <a class="email" href="mailto:kurt.sanger@ksanger.com" title="KSanger <kurt.sanger@ksanger.com>"> KSanger</a> <pre>(In reply to Michael Weghorn from <a href="show_bug.cgi?id=129146#c10">comment #10</a>) > Some questions: > > 1) How was the printer set up on the client? Did you set it up manually or > was it auto-discovered and the queue auto-created, e.g. using cups-browsed? > > 2) What is the output of 'lpstat -v' on the client? > > 3) What CUPS version do you have (on client and server)? > > 4) Do you get any entries in CUPS log if you set log level to "Debug" in > /etc/cups/cupsd.conf, then restart CUPS and try again? (CUPS log file is > usually /var/log/cups/error.log, unless configured elsewhere or CUPS is > configured to log to journal instead; you can check e.g. whether directive > 'ErrorLog /var/log/cups/error_log' is present in /etc/cup/cups-files.conf.) #4 I changed the file to LogLevel debug. Then did a "sudo systemctl stop cups.service" But now I can not get the cup client to restart. "sudo systemctl start cups.service" ends in an error. Job for cups.service failed because the control process exited with error code. See "systemctl status cups.service" and "journalctl -xe" for details. [kurt@wart cups]$ journalctl -xe Sep 22 10:26:37 wart systemd[1]: Failed to start CUPS Scheduler. -- Subject: A start job for unit cups.service has failed -- Defined-By: systemd -- Support: <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a> -- -- A start job for unit cups.service has finished with a failure. -- -- The job identifier is 6743 and the job result is failed. Trying su -c 'service cups start' results in authentication failure. [kurt@wart cups]$ sudo service cups start Redirecting to /bin/systemctl start cups.service Job for cups.service failed because the control process exited with error code. See "systemctl status cups.service" and "journalctl -xe" for details.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>