[SOLVED] The services cups and cups.socket stop.

[hankivy]

I am running 6.6.116-desktop-1.mga9. All of the installed software is up to date.

Starting cups.socket results in the following.

Code: Select all

 [hank@localhost ~]$ sudo systemctl start cups.socket.service
Failed to start cups.socket.service: Unit cups.socket.service not found.
[hank@localhost ~]$ 

Starting cups results in the following.

Code: Select all

 [hank@localhost ~]$ sudo journalctl -xeu cups.service
[sudo] password for hank:
░░
░░ A start job for unit cups.service has finished with a failure.
░░
░░ The job identifier is 3924 and the job result is failed.
Dec 08 13:05:36 localhost.localdomain systemd[1]: cups.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit cups.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 08 13:05:36 localhost.localdomain systemd[1]: Stopped cups.service.
░░ Subject: A stop job for unit cups.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit cups.service has finished.
░░
░░ The job identifier is 4270 and the job result is done.
Dec 08 13:05:36 localhost.localdomain systemd[1]: cups.service: Start request repeated too quickly.
Dec 08 13:05:36 localhost.localdomain systemd[1]: cups.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit cups.service has entered the 'failed' state with result 'exit-code'.
Dec 08 13:05:36 localhost.localdomain systemd[1]: Failed to start cups.service.
░░ Subject: A start job for unit cups.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cups.service has finished with a failure.
░░
░░ The job identifier is 4270 and the job result is failed.
...skipping...
░░
░░ A start job for unit cups.service has finished with a failure.
░░
░░ The job identifier is 3924 and the job result is failed.
Dec 08 13:05:36 localhost.localdomain systemd[1]: cups.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit cups.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 08 13:05:36 localhost.localdomain systemd[1]: Stopped cups.service.
░░ Subject: A stop job for unit cups.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit cups.service has finished.
░░
░░ The job identifier is 4270 and the job result is done.
Dec 08 13:05:36 localhost.localdomain systemd[1]: cups.service: Start request repeated too quickly.
Dec 08 13:05:36 localhost.localdomain systemd[1]: cups.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit cups.service has entered the 'failed' state with result 'exit-code'.
Dec 08 13:05:36 localhost.localdomain systemd[1]: Failed to start cups.service.
░░ Subject: A start job for unit cups.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cups.service has finished with a failure.
░░
░░ The job identifier is 4270 and the job result is failed.
lines 217-250/250 (END)
 

Any advice is appreciated. Thank you.

[morgano]

It seems latest cups update have some problems on some systems.
Sorry about that.

It seems affected users get around it by commenting out a few lines in cups config file.
See https://bugs.mageia.org/show_bug.cgi?id=34800#c11 Comment 11

[doktor5000]

Starting cups.socket results in the following.

Code: Select all

 [hank@localhost ~]$ sudo systemctl start cups.socket.service
Failed to start cups.socket.service: Unit cups.socket.service not found.
[hank@localhost ~]$ 

FWIW, you tried to start cups.socket.service where the error message is expected.
It's either cups.socket or cups.service

BTW many services are socket-activated nowadays, so if the socket has any incoming connections the related service is started automatically.
Check e.g. https://0pointer.de/blog/projects/socke ... ation.html for more context.

Also journalctl -x misses a few points, it's usually easier if you just do

Code: Select all

systemctl status cups.service -al -n50

to show the status for a service (active/inactive/failed/dead) including the last 50 lines of journal logs and also the started processes.

[hankivy]

I got it to work. See the note in Bugzilla https://bugs.mageia.org/show_bug.cgi?id=34800#c24 .