Bug#354581: cupsys - networked printing hangup because spool limit reached
Package: cupsys
Version: 1.1.23-10sarge1
Problem:
I got Samsung printer connected using USB on host Zivotne1, and I got it
net-connected using CUPS on Zivotne2 too. Zivotne1 is CUPS server in
this order, and Zivotne2 is client.
Suddenly, after some time, Zivotne2 printing stopped. The CUPS only
offered some not very thankful error and switched the network printer
off. From /var/log/cups on client and on server I got only strange "no
file ?!?" errors.
The Zivotne1 has set MaxJobs 500 and spool/cups contained 499 files.
This was first suspicion for me. However, the local printing on Zivotne1
(the CUPS server) worked well.
I must have
1, delete the spool on server
2, cancel all jobs on client
3, started the printer on client
and afther all of that, the new print jobs started working.
Seems to me, that local jobs have no problem of cycling the jobs files,
whereas the network jobs cannot. The client sends the job to server,
however couldn't send the file. Server notices the job, however dosen't
have the file-to-print for that job, so ends up with error.
I assume the client goes to some kind of deadlock then, because i see
that printing HAVEN'T started even after cleaning up the spool/cups on
server, even after starting the printer manually. Only effectively way
out of the client's deadlock has been cancelling of all print jobs on
client.
Reply to: