Sujet : Re: I lost CUPS
De : nunojsilva (at) *nospam* invalid.invalid (Nuno Silva)
Groupes : comp.os.linux.miscDate : 08. Aug 2024, 09:09:31
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v91ufs$3r6s8$1@dont-email.me>
References : 1
User-Agent : Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
On 2024-08-08,
vjp2.at@at.BioStrategist.dot.dot.com wrote:
It seems when I installed SNAP, CUPS stopped working. So I removed and
reinstalled it and I get:
>
sudo systemctl status cups
>
sudo systemctl status cups cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Wed 2024-08-07 11:31:06 EDT; 12s ago
Docs: man:cupsd(8)
Process: 23560 ExecStart=/usr/sbin/cupsd -l (code=killed,signal=TERM)
Main PID: 23560 (code=killed, signal=TERM)
>
cups.service: Service hold-off time over, scheduling restart.
cups.service: Scheduled restart job, restart counter is at 5.
Stopped CUPS Scheduler.
cups.service: Start request repeated too quickly.
cups.service: Failed with result 'start-limit-hit'.
Failed to start CUPS Scheduler.
Not knowing systemd, my guess at a glance is that these messages are
merely reporting a too quick retry to start the service, but not the
failure that triggered these restarts.
You'll want, like Lawrence said, to check logs. Cups logs, not systemd
logs. Or some cups-specific section of systemd logs (again, no idea of
how systemd handles this, at least on a UNIX-like system cups will have
log files under /var/log/cups/).
-- Nuno Silva