[arch-general] no cups web/server with new version?
Hi, I followed the cups instructions when it upgraded recently: % pacman -Qs cups local/cups 2.0.0-2 The CUPS Printing System - daemon package local/cups-filters 1.0.61-2 OpenPrinting CUPS Filters local/cups-pdf 2.6.1-2 PDF printer for cups local/lib32-libcups 1.7.5-1 The CUPS Printing System - client libraries (32-bit) local/libcups 2.0.0-2 The CUPS Printing System - client libraries and headers I stopped and removed the old service, reloaded daemons, started and enabled new services (org.cups.cupsd.service and cups-browsed.service). However it seems I don't have the server working, since I can't get to localhost:631, and: % dmesg | 'grep' cups [ 10.006918] systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. [ 10.006965] systemd[1]: Cannot add dependency job for unit cups.path, ignoring: Unit cups.path failed to load: No such file or directory. [ 1652.605967] systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. % lpinfo -v lpinfo: Bad file descriptor The only configs in cups-files: % 'grep' '^[^#]' /etc/cups/cups-files.conf SystemGroup sys root lp AccessLog /var/log/cups/access_log ErrorLog /var/log/cups/error_log PageLog /var/log/cups/page_log I noticed a prior e-mail about this, with similar dmesg indications, but the OP indicated he solved his problems by using the appropriate services. Though I think I have the right services started and enabled... BTW, the web interface was working prior to the update. Any hints? Thanks, -- Javier.
On 11/04/2014 06:06 PM, Javier Vasquez wrote:
I stopped and removed the old service, reloaded daemons, started and enabled new services (org.cups.cupsd.service and cups-browsed.service).
However it seems I don't have the server working, since I can't get to localhost:631, and:
% dmesg | 'grep' cups [ 10.006918] systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. [ 10.006965] systemd[1]: Cannot add dependency job for unit cups.path, ignoring: Unit cups.path failed to load: No such file or directory. [ 1652.605967] systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.
cups.socket and cups.path are the old names (used before the upgrade). Disable everything cups related by removing the symlinks. A find command should help you weed out stuff from before the upgrade: find /etc/systemd/system/ -iname "*cups*" Then, try reenabling and starting cups again. (Three symlinks should be created.) systemctl enable org.cups.cupsd.service systemctl start org.cups.cupsd.service Here is my current (working) configuration: $ find /etc/systemd/system/ -iname "*cups*" /etc/systemd/system/sockets.target.wants/org.cups.cupsd.socket /etc/systemd/system/printer.target.wants/org.cups.cupsd.service /etc/systemd/system/multi-user.target.wants/org.cups.cupsd.path The note about the renamed service files is on the wiki [1]. --Kyle Terrien [1] https://wiki.archlinux.org/index.php/Cups#CUPS_daemon
cups.socket and cups.path are the old names (used before the upgrade).
Right. Removed already. Thanks.
Disable everything cups related by removing the symlinks. A find command should help you weed out stuff from before the upgrade:
find /etc/systemd/system/ -iname "*cups*"
Then, try reenabling and starting cups again. (Three symlinks should be created.)
systemctl enable org.cups.cupsd.service systemctl start org.cups.cupsd.service
Here is my current (working) configuration:
$ find /etc/systemd/system/ -iname "*cups*" /etc/systemd/system/sockets.target.wants/org.cups.cupsd.socket /etc/systemd/system/printer.target.wants/org.cups.cupsd.service /etc/systemd/system/multi-user.target.wants/org.cups.cupsd.path
The note about the renamed service files is on the wiki [1].
Yes, thanks, I just didn't pay attention to the socket and path old units. Just the cups.service.
--Kyle Terrien
After disabling the remaining cups.socket and cups.path, rebooting, stopping and disabling org.cups.cupsd.service, and starting and enabling it again, I now don't see the dmesg cups stuff, thanks: % dmesg | 'grep' cups % However I still don't get cups working (not on the web interface, neither lpinfo): % sudo find /etc/systemd/ -name '*cups*' /etc/systemd/system/multi-user.target.wants/org.cups.cupsd.path /etc/systemd/system/printer.target.wants/org.cups.cupsd.service /etc/systemd/system/sockets.target.wants/org.cups.cupsd.socket % lpinfo -v lpinfo: Bad file descriptor 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) Nov 04 21:24:58 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:24:58 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:24:58 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. % 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. Nov 04 21:12:41 m1 systemd[1]: Stopped CUPS Scheduler. Nov 04 21:16:12 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:16:12 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:16:12 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:16:12 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. Nov 04 21:16:42 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:16:42 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:16:42 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:16:42 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. Nov 04 21:24:58 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:24:58 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:24:58 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:24:58 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. Notice I restarted it several times after some intermediate trials... if I run cupsd directly: % sudo cupsd cupsd: Child exited with status 1 Which is even more weird to me. cups named packages installed: % pacman -Qs cups local/cups 2.0.0-2 The CUPS Printing System - daemon package local/cups-filters 1.0.61-2 OpenPrinting CUPS Filters local/cups-pdf 2.6.1-2 PDF printer for cups local/lib32-libcups 1.7.5-1 The CUPS Printing System - client libraries (32-bit) local/libcups 2.0.0-2 The CUPS Printing System - client libraries and headers I tried re-installing cups and libcups with no sucees (just in case)... I'm still in the dark, sorry, :-( Thanks, -- Javier.
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)
Nov 04 21:24:58 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:24:58 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:24:58 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state.
% 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. Nov 04 21:12:41 m1 systemd[1]: Stopped CUPS Scheduler. Nov 04 21:16:12 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:16:12 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:16:12 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:16:12 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. Nov 04 21:16:42 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:16:42 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:16:42 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:16:42 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state. Nov 04 21:24:58 m1 systemd[1]: Starting CUPS Scheduler... Nov 04 21:24:58 m1 systemd[1]: Started CUPS Scheduler. Nov 04 21:24:58 m1 systemd[1]: org.cups.cupsd.service: main process exited, code=exited, status=1/FAILURE Nov 04 21:24:58 m1 systemd[1]: Unit org.cups.cupsd.service entered failed state.
Notice I restarted it several times after some intermediate trials...
if I run cupsd directly:
% sudo cupsd cupsd: Child exited with status 1
Which is even more weird to me. cups named packages installed:
% pacman -Qs cups local/cups 2.0.0-2 The CUPS Printing System - daemon package local/cups-filters 1.0.61-2 OpenPrinting CUPS Filters local/cups-pdf 2.6.1-2 PDF printer for cups local/lib32-libcups 1.7.5-1 The CUPS Printing System - client libraries (32-bit) local/libcups 2.0.0-2 The CUPS Printing System - client libraries and headers
I tried re-installing cups and libcups with no sucees (just in case)...
I'm still in the dark, sorry, :-(
Thanks,
Does /var/log/cups/error_log say anything? I suppose you could always revert to a stock configuration (using the .pacnews) if you have to. --Kyle Terrien
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 %
I suppose you could always revert to a stock configuration (using the .pacnews) if you have to.
--Kyle Terrien
Hmm, will try. The only *.pacnew I got from the cups upgrade was cups-files.conf, and it's already merged. I'll download it from the web and see if that helps. Thanks, -- Javier.
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
On Wed, Nov 5, 2014 at 1:56 PM, Lex Onderwater <Lex@onderwater.org> wrote:
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
Thanks a lot Lex. That was it. Actually as SystemGroup also includes by default sys and root, I just left it commented out as the Group line is. Seems to be working back. It didn't occur to me to increase verbosity (neither I knew how to before). Sorry about that. Thanks, -- Javier.
participants (3)
-
Javier Vasquez
-
Kyle Terrien
-
Lex Onderwater