nootnl
January 10, 2022, 11:33am
1
Hi,
I am trying to install a local network printer using YAST.
When I start the printer application I get a message “Restart locally running CUPS daemon”. I answer “yes”. I then get an error message “Error failed to restart the CUPS daemon” with details “Attempt to restart
service ‘cups’ failed.ERROR: " with no more detail. I then get the error message [size=2]”[/size]A locally running CUPS daemon is required, but it seems to be not accessible. Check with ‘lpstat -h localhost -r’ whether a local cupsd is accessible. A non-accessible cupsd leads to an endless sequence of further failures."
Output for lpstat :
noot@localhost:~> lpstat -h localhost -r
scheduler is not running
The KDE printer installer won’t work either , startup message “Print service is unavailable-bad file descriptor”.
How to get the CUPS daemon up and running again ?
hcvv
January 10, 2022, 12:42pm
2
This is an important point. You try, but you do not tell what exactly you did. Thus it is rather impossible for others to comment on that.
BTW to start CUPS (as root):
systemctl start cups
(and for restart, the restart command)
But better first check it’s status:
systemctl status cups
nootnl
January 10, 2022, 12:59pm
3
Sorry, i have this issue for a good number of months now, I cannot recall how I ended up in this situation.
Output :
**localhost:/home/noot #** systemctl status cups
**×** cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: **failed** (Result: protocol) since Mon 2022-01-10 11:39:19 CET; 1h 9min ago
TriggeredBy: **×** cups.socket
**×** cups.path
Docs: man:cupsd(8)
Process: 1527 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=TERM)
Main PID: 1527 (code=killed, signal=TERM)
CPU: 5ms
Jan 10 11:39:19 localhost systemd[1]: **cups.service: Start request repeated too quickly.**
Jan 10 11:39:19 localhost systemd[1]: **cups.service: Failed with result 'protocol'.**
Jan 10 11:39:19 localhost systemd[1]: **Failed to start CUPS Scheduler.**
**localhost:/home/noot #** systemctl start cups
Job for cups.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status cups.service" and "journalctl -xeu cups.service" for details.
**localhost:/home/noot #** systemctl status cups.service
○ cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: protocol) since Mon 2022-01-10 12:51:35 CET; 1min 23s ago
TriggeredBy: **×** cups.socket
**×** cups.path
Docs: man:cupsd(8)
Process: 7575 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=TERM)
Main PID: 7575 (code=killed, signal=TERM)
CPU: 5ms
Jan 10 12:51:35 localhost.localdomain systemd[1]: cups.service: Scheduled restart job, restart counter is at 5.
Jan 10 12:51:35 localhost.localdomain systemd[1]: Stopped CUPS Scheduler.
Jan 10 12:51:35 localhost.localdomain systemd[1]: **Dependency failed for CUPS Scheduler.**
Jan 10 12:51:35 localhost.localdomain systemd[1]: **cups.service: Job cups.service/start failed with result 'dependency'.**
**localhost:/home/noot #** systemctl status cups.service
○ cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: protocol) since Mon 2022-01-10 12:51:35 CET; 2min 18s ago
TriggeredBy: **×** cups.socket
**×** cups.path
Docs: man:cupsd(8)
Process: 7575 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=TERM)
Main PID: 7575 (code=killed, signal=TERM)
CPU: 5ms
Jan 10 12:51:35 localhost.localdomain systemd[1]: cups.service: Scheduled restart job, restart counter is at 5.
Jan 10 12:51:35 localhost.localdomain systemd[1]: Stopped CUPS Scheduler.
Jan 10 12:51:35 localhost.localdomain systemd[1]: **Dependency failed for CUPS Scheduler.**
Jan 10 12:51:35 localhost.localdomain systemd[1]: **cups.service: Job cups.service/start failed with result 'dependency'.**
**localhost:/home/noot #**
You may search for cups stuff and run “zypper install --force” for each of the packages found:
**erlangen:~ #** zypper se -is cups
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+---------------------+---------+--------------+--------+-----------------------
i+ | cups | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | cups-client | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | cups-config | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | cups-filters | package | 1.28.8-3.2 | x86_64 | Haupt-Repository (OSS)
i | libcups2 | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i+ | libcups2-32bit | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | libcupsimage2 | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | python3-cupshelpers | package | 1.5.15-2.2 | noarch | Haupt-Repository (OSS)
i | python38-pycups | package | 2.0.1-1.8 | x86_64 | Haupt-Repository (OSS)
**erlangen:~ #**
nootnl
January 11, 2022, 11:54am
5
karlmistelberger:
You may search for cups stuff and run “zypper install --force” for each of the packages found:
**erlangen:~ #** zypper se -is cups
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+---------------------+---------+--------------+--------+-----------------------
i+ | cups | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | cups-client | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | cups-config | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | cups-filters | package | 1.28.8-3.2 | x86_64 | Haupt-Repository (OSS)
i | libcups2 | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i+ | libcups2-32bit | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | libcupsimage2 | package | 2.3.3op2-8.1 | x86_64 | Haupt-Repository (OSS)
i | python3-cupshelpers | package | 1.5.15-2.2 | noarch | Haupt-Repository (OSS)
i | python38-pycups | package | 2.0.1-1.8 | x86_64 | Haupt-Repository (OSS)
**erlangen:~ #**
Thanks. My output shows all duplicates and an older version of python38-pycups ?
noot@localhost:~> sudo zypper se -is cups
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+---------------------+---------+--------------+--------+----------------------
i | cups | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i | cups | package | 2.3.3op2-8.1 | x86_64 | openSUSE-20200721-0
i+ | cups-airprint | package | 1.1-1.5 | noarch | (System Packages)
i | cups-client | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i | cups-client | package | 2.3.3op2-8.1 | x86_64 | openSUSE-20200721-0
i+ | cups-config | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i+ | cups-config | package | 2.3.3op2-8.1 | x86_64 | openSUSE-20200721-0
i+ | cups-filters | package | 1.28.8-3.2 | x86_64 | Main Repository (OSS)
i+ | cups-filters | package | 1.28.8-3.2 | x86_64 | openSUSE-20200721-0
i | libcups2 | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i | libcups2 | package | 2.3.3op2-8.1 | x86_64 | openSUSE-20200721-0
i+ | libcups2-32bit | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i+ | libcups2-32bit | package | 2.3.3op2-8.1 | x86_64 | openSUSE-20200721-0
i | libcupsimage2 | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i | libcupsimage2 | package | 2.3.3op2-8.1 | x86_64 | openSUSE-20200721-0
i+ | python3-cupshelpers | package | 1.5.15-2.2 | noarch | Main Repository (OSS)
i+ | python3-cupshelpers | package | 1.5.15-2.2 | noarch | openSUSE-20200721-0
i+ | python38-pycups | package | 2.0.1-1.7 | x86_64 | (System Packages)
noot@localhost:~>
More suggestions ?
hcvv
January 11, 2022, 11:59am
6
As you can see yourself, you seem to have double versions of several packages installed, from different repos.
Can you please post
zypper lr -d
nootnl
January 11, 2022, 2:53pm
7
As additional info, I have another thread running as I experience update problems too.
One of the suggestions there is too reduce the number of repositories to the bare minimum.
Output:
noot@localhost:~> sudo zypper lr -d
[sudo] password for root:
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+----------------------------------------+---------------------------+---------+-----------+---------+----------+----------+------------------------------------------------------------------------------+--------
1 | Downloads | Downloads | Yes | ( p) Yes | Yes | 99 | plaindir | dir:/home/noot/Downloads |
2 | brave-browser | brave-browser | Yes | (r ) Yes | Yes | 99 | rpm-md | https://brave-browser-rpm-release.s3.brave.com/x86_64/ |
3 | download.nvidia.com-tumbleweed | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.nvidia.com/opensuse/tumbleweed |
4 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
5 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
6 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
7 | openSUSE-20200721-0 | openSUSE-20200721-0 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
8 | openSUSE_Tumbleweed | Packman | Yes | (r ) Yes | Yes | 99 | rpm-md | http://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/ |
9 | opensuse-guide.org-openSUSE_Tumbleweed | libdvdcss repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/ |
10 | oss | tmp | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.2/repo/oss/ |
11 | snappy | snappy | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.0 |
noot@localhost:~>
Would that be applicable in this issue too?
hcvv
January 11, 2022, 3:26pm
8
Well, I don’t know if it is the reason for this printer problem. but you can see that you #5 and #7 are the same (they have the same URL, thus even when they have different names ans aliases, they still point to the same repository and that is also the reason that packages are mentioned twice). Advice: remove #7 .
Then you say you run Tumbleweed, but #10 is for 15.2, and yes that can give problems. Advice: remove it.
#11 is even for 15.0. I have no idea where you have it for, but when you need packages from it, better change to a Tumbleweed version of that repo.
After you have repaired this list, you should do a
zypper dup
to be sure that now all packages are from the correct repos. Only after that it will be relevant to address any problems.
nootnl
January 12, 2022, 12:42pm
9
OK, was able to perform the zypper dup after cleaning up the repositories, updated some 3000+ items and rebooted.
System started up normally. The Yast printer installer however did not work, same problem as described above.
I will go through the steps suggested earlier and come back with the results.
nootnl:
OK, was able to perform the zypper dup after cleaning up the repositories, updated some 3000+ items and rebooted.
System started up normally. The Yast printer installer however did not work, same problem as described above.
I will go through the steps suggested earlier and come back with the results.
As a courtesy to users willing to help you may temporarily disable all repos but the following and upgrade:
**erlangen:~ #** zypper lr -uEP
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | URI
---+----------------------------------+---------------------------------+---------+-----------+---------+----------+--------------------------------------------------------------------------------
5 | Packman | Packman | Yes | (r ) Yes | Yes | 90 | http://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/
8 | download.opensuse.org-non-oss | Haupt-Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/tumbleweed/repo/non-oss/
9 | download.opensuse.org-oss | Haupt-Repository (OSS) | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/tumbleweed/repo/oss/
10 | download.opensuse.org-tumbleweed | Hauptaktualisierungs-Repository | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/update/tumbleweed/
**erlangen:~ #** zypper dist-upgrade --allow-vendor-change
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
Nothing to do.
**erlangen:~ #**
hcvv
January 12, 2022, 2:14pm
11
As alternative suggestion, show you cleaned up repo list as you have it now. for validation by people here.
nootnl
January 12, 2022, 3:34pm
12
This is the cleaned-up repository listing I now use (the original is lister earlier):
noot@localhost:~> sudo zypper lr -uEP
[sudo] password for root:
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | URI
--+----------------------------------------+---------------------------+---------+-----------+---------+----------+-------------------------------------------------------
1 | Downloads | Downloads | Yes | ( p) Yes | Yes | 99 | dir:/home/noot/Downloads
2 | brave-browser | brave-browser | Yes | (r ) Yes | Yes | 99 | https://brave-browser-rpm-release.s3.brave.com/x86_64/
3 | download.nvidia.com-tumbleweed | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | https://download.nvidia.com/opensuse/tumbleweed
4 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/tumbleweed/repo/non-oss/
5 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/tumbleweed/repo/oss/
6 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/update/tumbleweed/
7 | openSUSE_Tumbleweed | Packman | Yes | (r ) Yes | Yes | 99 | http://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/
8 | opensuse-guide.org-openSUSE_Tumbleweed | libdvdcss repository | Yes | (r ) Yes | Yes | 99 | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/
noot@localhost:~>
nootnl
January 12, 2022, 3:51pm
13
And these are the outputs from the earlier commands :
noot@localhost:~> lpstat -h localhost -r
scheduler is not running
noot@localhost:~> sudo systemctl start cups
[sudo] password for root:
Job for cups.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status cups.service" and "journalctl -xeu cups.service" for details.
noot@localhost:~> systemctl status cups.service
○ cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: protocol) since Wed 2022-01-12 15:42:56 CET; 31s ago
TriggeredBy: **×** cups.path
**×** cups.socket
Docs: man:cupsd(8)
Process: 7715 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=TERM)
Main PID: 7715 (code=killed, signal=TERM)
CPU: 10ms
noot@localhost:~> journalctl -xeu cups.service
**Hint: You are currently not seeing messages from other users and the system.**
** Users in the 'systemd-journal' group can see all messages. Pass -q to**
** turn off this notice.**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
**~**
-- Journal begins at Sat 2020-12-05 09:22:08 CET, ends at Wed 2022-01-12 15:42:55 CET. --
-- No entries --
noot@localhost:~> systemctl status cups
○ cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: protocol) since Wed 2022-01-12 15:42:56 CET; 3min 43s ago
TriggeredBy: **×** cups.path
**×** cups.socket
Docs: man:cupsd(8)
Process: 7715 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=TERM)
Main PID: 7715 (code=killed, signal=TERM)
CPU: 10ms
noot@localhost:~> sudo zypper se -is cups
[sudo] password for root:
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+---------------------+---------+--------------+--------+----------------------
i | cups | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i+ | cups-airprint | package | 1.1-1.6 | noarch | Main Repository (OSS)
i | cups-client | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i+ | cups-config | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i+ | cups-filters | package | 1.28.8-3.2 | x86_64 | Main Repository (OSS)
i | libcups2 | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i+ | libcups2-32bit | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i | libcupsimage2 | package | 2.3.3op2-8.1 | x86_64 | Main Repository (OSS)
i+ | python3-cupshelpers | package | 1.5.15-3.1 | noarch | Main Repository (OSS)
i+ | python38-pycups | package | 2.0.1-1.8 | x86_64 | Main Repository (OSS)
noot@localhost:~>
hcvv
January 12, 2022, 3:52pm
14
Looks much, much better.
You could disable libdvdcss (#8 ), because once you have the only package from there, that never changes.
Personally, I would give #7 another Alias, e.g. packman, because that better shows what it is.
nootnl:
And these are the outputs from the earlier commands :
noot@localhost:~> lpstat -h localhost -r
scheduler is not running
noot@localhost:~> sudo systemctl start cups
[sudo] password for root:
Job for cups.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status cups.service" and "journalctl -xeu cups.service" for details.
noot@localhost:~> systemctl status cups.service
○ cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: protocol) since Wed 2022-01-12 15:42:56 CET; 31s ago
TriggeredBy: **×** cups.path
**×** cups.socket
Docs: man:cupsd(8)
Process: 7715 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=TERM)
Main PID: 7715 (code=killed, signal=TERM)
CPU: 10ms
Please show
sudo cat /etc/cups/cupsd.conf|egrep -i "listen|web|browsing"
For reference I have
~> sudo cat /etc/cups/cupsd.conf|egrep -i "listen|web|browsing"
Listen localhost:631
Listen /run/cups/cups.sock
Browsing On
WebInterface Yes
Also you could try restarting cups
sudo systemctl restart cups
then immediately perform the printer configuration steps, either using YaST, or via the CUPS web interface (localhost:631) using a browser.
hcvv
January 12, 2022, 9:27pm
17
Hi Dean,
You may have missed that cupsd does imediatly crash (or does not even start).
Main message seems to me:
Job for cups.service failed because the service did not take the steps required by its unit configuration.
Looks still a bit as if not all components fit together (as you see above, the OP had a rather borked system).
I read that earlier in the thread, but the last invocation of ‘systsmectl status cups’ seemed to report no error? (Mind you I now see that it wasn’t run as root.)
hcvv
January 12, 2022, 10:41pm
19
Hm. may have missed that. Going to bed now before the wife will miss me;)
nootnl
January 13, 2022, 11:46am
20
Here is the output :
noot@localhost:~> sudo cat /etc/cups/cupsd.conf|egrep -i "listen|web|browsing"
[sudo] password for root:
noot@localhost:~> sudo systemctl restart cups
[sudo] password for root:
Job for cups.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status cups.service" and "journalctl -xeu cups.service" for details.
noot@localhost:~> sudo systemctl status cups.service
○ cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: protocol) since Thu 2022-01-13 11:29:21 CET; 13min ago
TriggeredBy: **×** cups.socket
**×** cups.path
Docs: man:cupsd(8)
Process: 21504 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=TERM)
Main PID: 21504 (code=killed, signal=TERM)
CPU: 6ms
Jan 13 11:29:21 localhost.localdomain systemd[1]: cups.service: Scheduled restart job, restart counter is at 10.
Jan 13 11:29:21 localhost.localdomain systemd[1]: Stopped CUPS Scheduler.
Jan 13 11:29:21 localhost.localdomain systemd[1]: **Dependency failed for CUPS Scheduler.**
Jan 13 11:29:21 localhost.localdomain systemd[1]: **cups.service: Job cups.service/start failed with result 'dependency'.**
noot@localhost:~>
The first comman gives no output.