[SOLVED] cups.socket failed with error "No such device or address"

plmday · 2012-11-23 10:47:27

Hi,

I recently migrated to systemd following the migration guide. Unfortunately after the migration, remote printing no longer works. Changes I noticed when I tried to print in Okular is that the printing dialog display less options. After I chose the remote printer and clicked print, nothing happened. But I can print locally to PDF. Any idea?

Below is some info, let me know if you any other info to help diagnose the problem.

# dmesg | grep cups
[    6.880212] systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. See system logs and 'systemctl status cups.socket' for details.

# systemctl status cups
cups.service - CUPS Printing Service
          Loaded: loaded (/usr/lib/systemd/system/cups.service; disabled)
          Active: active (running) since Fri, 2012-11-23 11:24:54 CET; 15min ago
        Main PID: 3693 (cupsd)
          CGroup: name=systemd:/system/cups.service
                  â 3693 /usr/sbin/cupsd -f

Nov 23 11:24:54 dreams systemd[1]: Started CUPS Printing Service.

# systemctl status cups.socket
cups.socket
          Loaded: error (Reason: No such device or address)
          Active: inactive (dead)

Nov 16 17:19:35 dreams systemd[1]: Stopping CUPS Printing Service Sockets.
Nov 16 17:19:35 dreams systemd[1]: Closed CUPS Printing Service Sockets.
Nov 19 12:23:15 dreams systemd[1]: Starting CUPS Printing Service Sockets.
Nov 19 12:23:15 dreams systemd[1]: Listening on CUPS Printing Service Sockets.
Nov 19 16:39:36 dreams systemd[1]: Stopping CUPS Printing Service Sockets.
Nov 19 16:39:36 dreams systemd[1]: Closed CUPS Printing Service Sockets.
Nov 20 10:51:30 dreams systemd[1]: Starting CUPS Printing Service Sockets.
Nov 20 10:51:30 dreams systemd[1]: Listening on CUPS Printing Service Sockets.
Nov 20 11:58:54 dreams systemd[1]: Stopping CUPS Printing Service Sockets.
Nov 20 11:58:54 dreams systemd[1]: Closed CUPS Printing Service Sockets.

Last edited by plmday (2012-12-11 10:15:13)

peterb · 2012-11-25 10:01:14

Hi,

maybe you forgot to switch to systemd's cups socket file? It's described here:

https://wiki.archlinux.org/index.php/CU … to_Systemd

Regards

65kid · 2012-11-25 10:46:51

peterb wrote:

Hi,
maybe you forgot to switch to systemd's cups socket file? It's described here:
https://wiki.archlinux.org/index.php/CU … to_Systemd

Regards

uh, what? As far as I can see, this wiki section makes no sense whatsoever and whoever wrote this has no idea what he is doing. /usr/lib/systemd/system/cups.socket is a systemd unit describing the cups socket to listen on, /var/run/cups/cups.sock is the socket itself (which is also specified in the systemd unit).

Am I missing something here?

plmday · 2012-11-26 09:06:55

peterb wrote:

Hi,
maybe you forgot to switch to systemd's cups socket file? It's described here:
https://wiki.archlinux.org/index.php/CU … to_Systemd

Regards

Hi, thanks for the reply. No, I have already done that before I post the question. It did not work.

rdw · 2012-11-27 21:46:36

Hi,

I am experiencing the same problem as the original poster after migrating to (pure) systemd.

In particular, I receive exactly the same output from the following.

dmesg | grep cups

systemctl status cups

systemctl status cups.socket

The web interface

http://localhost:631

cannot be found (and nothing prints).

There are quite a few forum posts describing variations on this problem. There seems to be some confusion, as evidenced for example by the comments above. None of the various responses I have seen resolve the problem in my case - in particular, following the advice of the wiki does not work.

A recent forum post is the following - the original poster appears to have got things to work, but I cannot make sense of it...

https://bbs.archlinux.org/viewtopic.php?id=153365

Would anybody be able to give clear advice as to how to proceed? Thanks!

plmday · 2012-12-10 15:59:19

65kid wrote:

uh, what? As far as I can see, this wiki section makes no sense whatsoever and whoever wrote this has no idea what he is doing. /usr/lib/systemd/system/cups.socket is a systemd unit describing the cups socket to listen on, /var/run/cups/cups.sock is the socket itself (which is also specified in the systemd unit).
Am I missing something here?

Hi, 65Kid, it is even stranger now I do not have cups.sock in /var/run/cups any more. I do not know how it's gone. Before I switched to /usr/lib/systemd/system/cups.socket following the Wiki page, it was there.

65kid · 2012-12-10 16:24:07

plmday wrote:

65kid wrote:
uh, what? As far as I can see, this wiki section makes no sense whatsoever and whoever wrote this has no idea what he is doing. /usr/lib/systemd/system/cups.socket is a systemd unit describing the cups socket to listen on, /var/run/cups/cups.sock is the socket itself (which is also specified in the systemd unit).
Am I missing something here?
Hi, 65Kid, it is even stranger now I do not have cups.sock in /var/run/cups any more. I do not know how it's gone. Before I switched to /usr/lib/systemd/system/cups.socket following the Wiki page, it was there.

my guess is that is because you also changed the socket in /etc/cups/client.conf, as is stated in this non-sense wiki section. I'm going to remove it.

plmday · 2012-12-10 16:31:44

65kid wrote:

my guess is that is because you also changed the socket in /etc/cups/client.conf, as is stated in this non-sense wiki section. I'm going to remove it.

Wait, but if you look at the post linked by rdw, styan has no problem with that at all. He has exactly the systemd version cups.socket enabled and loaded.

65kid · 2012-12-10 16:54:21

plmday wrote:

65kid wrote:
my guess is that is because you also changed the socket in /etc/cups/client.conf, as is stated in this non-sense wiki section. I'm going to remove it.
Wait, but if you look at the post linked by rdw, styan has no problem with that at all. He has exactly the systemd version cups.socket enabled and loaded.

tbh, I don't know what is causing your problems as I am no cups expert, but what I can tell you is that the suggestion from the wiki section made no sense whatsoever and most certainly couldn't have fixed it. And in the link by rdw, there is no talk about changing the socket config as suggesting in the wiki.
What I suggest:

systemctl disable cups.service cups.path cups.socket cupsd.service
mv /etc/cups /etc/cups.bak
pacman -S cups cups-filters libcups
systemctl enable cups.service
reboot

enabling cups.service will automatically pull in cups.socket and cups.path. Do not mess with the systemd socket config, it should just work. If it still doesn't post the output of:

systemctl status cups.service cups.path cups.socket

plmday · 2012-12-11 10:13:41

Hi, 65kid, thank you so much. After reverting following your suggestion, all cups.service, cups.path and cups.socket are successfully loaded. Although I still could not print, I think it is another problem. The lesson learned: people, think twice before you edit the Wiki!

rdw · 2012-12-15 14:54:06

Thanks very much 65kid, this simple solution also now works for me! This was somewhat surprising to me, as I thought I had tried this earlier - perhaps an update to cups fixed something in the meantime. Anyhow, much appreciated!

Arch Linux

#1 2012-11-23 10:47:27

[SOLVED] cups.socket failed with error "No such device or address"

#2 2012-11-25 10:01:14

Re: [SOLVED] cups.socket failed with error "No such device or address"

#3 2012-11-25 10:46:51

Re: [SOLVED] cups.socket failed with error "No such device or address"

#4 2012-11-26 09:06:55

Re: [SOLVED] cups.socket failed with error "No such device or address"

#5 2012-11-27 21:46:36

Re: [SOLVED] cups.socket failed with error "No such device or address"

#6 2012-12-10 15:59:19

Re: [SOLVED] cups.socket failed with error "No such device or address"

#7 2012-12-10 16:24:07

Re: [SOLVED] cups.socket failed with error "No such device or address"

#8 2012-12-10 16:31:44

Re: [SOLVED] cups.socket failed with error "No such device or address"

#9 2012-12-10 16:54:21

Re: [SOLVED] cups.socket failed with error "No such device or address"

#10 2012-12-11 10:13:41

Re: [SOLVED] cups.socket failed with error "No such device or address"

#11 2012-12-15 14:54:06

Re: [SOLVED] cups.socket failed with error "No such device or address"

Board footer