CUPS get stuck after restart on active cups-browsed print jobs
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- c, linux, ubuntu
- Área
- operating-systems
Línea de trabajo
Comienza revisando las unidades systemd de cups y cups-browsed, los registros del servicio reportados y el estado de la cola en /var/spool/cups después de un reinicio. Reproduce el fallo en Ubuntu 22.04 con un trabajo activo de cups-browsed y compara el comportamiento cuando se reinicia cada uno de los dos daemons. Se considera terminado cuando las impresoras en cola se recuperan sin errores destination-host persistentes ni requerir la eliminación de archivos de spool.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
Printer queues getting stuck or disabled and sometimes yield a status message "No suitable destination host found by cups-browsed, retrying later" or "No destination host name supplied by cups-browsed for printer , is cups-browsed running?". Printing on other printer queues from cups-browsed works successful, at least most of the time.
We tried solving the problem by clearing all print queues on the affected workstations at first (stopping both daemons and clear printers.conf), but it didn't stop it. The patch https://github.com/OpenPrinting/cups-browsed/commit/57d9351ea45f47b3bd185f263b1e37d276cf17b8 from #23 didn't really solved it, too.
At the moment, I suspect a line of shell script in our configuration management (fai) which restarts the cups-browsed daemon after a configuration change.
To Reproduce
Steps to reproduce the behavior:
- Print a job to a printer queue managed by cups-browsed. Helpful if the print job is bigger than a few pages so you got more time to react.
- Wait till the program printed and the job is processed by CUPS.
- Restart the
cupsorcups-browsedsystemd unit. Both should result in some or an other error described above. - Printing again to the same queue yields to the same error. Maybe a single print job passes through, but the same error is excepted.
Expected behavior
Printing works even through restart from one of the responsible daemons or the avoidance of persisting the error.
System Information:
- OS: Ubuntu
- Version 22.04 LTS
cups-browsed and cups-filters are backported from Ubuntu mantic (Version 2.0.0-0ubuntu2) because of trouble in earlier versions in junction to our CUPS server on Debian 11.
Also added the patch https://github.com/OpenPrinting/cups-browsed/commit/57d9351ea45f47b3bd185f263b1e37d276cf17b8
Additional context
From my current understanding, it's a problem when CUPS want to print but cups-browsed hasn't detected the remote printer. It could be because of those cases:
- cups-browsed is in restart and therefor, printing isn't possible.
- CUPS started and have unfinished jobs from the previous run. The daemon tries to print but cups-browsed didn't detected the remote printers yet, so no target to print.
When restarting CUPS, these problematic printing queues persist while other queues appear after cups-browsed detected them. Don't know if thats just a CUPS problem because theres a print job for him also.
On most workstations that reported the problem, we found log messages that systemd killed the service at some time and cups-browsed reports the following message for all print queues at the next start:
Timeout happened during creation of the queue <name>, turn on DebugLogging for more info.
We now tried to temporarily solve this problem by the following systemd unit override for cups.service:
# /etc/systemd/system/cups.service.d/20-cups-jobs.conf
[Service]
ExecStartPre=/usr/bin/find /var/spool/cups -maxdepth 1 -type f -delete
It cleans the printing queue before the start so it wont trigger an undetected cups-browsed printer.
I can give feedback if this solves it. At least at the next restart.
Would be nice if cups-browsed would be more resilient with this.
- Lenguaje dominante
- C
- Estrellas
- 51
- Forks
- 21
- Merge medio
- 22 h 49 min
- PR fusionados (30 d)
- 6
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de OpenPrinting/cups-browsed
-
Dificultad 3/5 1-2 días Aptitud para principiantes 67/100
OpenPrinting/cups-browsed#82 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
OpenPrinting/cups-browsed#77 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
OpenPrinting/cups-browsed#76 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 50/100
OpenPrinting/cups-browsed#75 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
OpenPrinting/cups-browsed#71 ·
Todos los issues de OpenPrinting/cups-browsed
Issues similares
-
`sha256()` returns a wrong hash when libsql-ffi is built with gcc 11 or laterPosiblemente ocupada @colinhacks la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
tursodatabase/libsql#2333 ·
Los mantenedores suelen responder en 11 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
OpenPrinting/cups#1826 ·
Los mantenedores suelen responder en 1 día
-
Backport to 3.0 advertises a suffix that does not existPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
389ds/389-ds-base#8152 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
RetroAchievements/rcheevos#580 · 1 comentario ·
Los mantenedores suelen responder en 5 días