Re: remote printing for an USB printer
On Sun 21 Dec 2014 at 20:46:55 +0100, Pierre Frenkiel wrote:
> On Sun, 21 Dec 2014, Brian wrote:
>
> >On Sat 20 Dec 2014 at 22:03:50 +0100, Pierre Frenkiel wrote:
> >> I think that a so mature OS as Debian should provide the same
> >> facility.
> >
> >It does.
>
> the experience proves that it does not: otherwise, why nobody could
> explain the problem I described and suggest a fix?
Describing a problem accurately (which you have done) and coming up with
a solid fix are two different things.
> The only help I got up to now was: "do a correct setup"
> that is very helpful!
Getting no responses would be getting no help. I'll suspend judgement on
whether the Wheezy client is at fault. It could be the server. (Please
see the log). I have successfully set up a print queue for your printer;
details later if you want them.
> >> This also shows that the sharing is correctly setup on the server side.
> >
> >For the Android.
>
> I would be curious to understand how a CUPS sharing setup on the server
> could work for Android and not for Linux?
A guess, because you would know more about how an Android works than I:
the Android can process Bonjour broadcasts directly whereas a Wheezy
client needs some help. I'm Androidless so could be wromg.
> >Where is the printer queue set up? On the client or on the server?
>
> I don't understand at all this question: how could I setup on the client
> a printer connected via USB on the server?
> On the client, the only thing you can do is to add a shared printer,
> but not modify it's setup.
You have misunderstand the question.
> >Empty the error_log with '>/var/log/error_log'; print ; send the client
> >log to the list if you wish.
>
> I join the client error_log, severely cut as it became huge very quickly
> you can remark all lines like "Print file accepted - job ID 2025"
> which explains why the queue is growing on the server, but not why it
> does that.
>
> >> cups-browsed needs to be correctly set up on the server for the client
> >to be able to see the advertised queues. > > "listen 192.168.1.12"
> should not be the least bit necessary.
> I installed cups-browsed, but that changed nothing, which seems noraml,
> as the lient already sees the print queue and can print to it.
> I repeat: the problem is not that I can't print, but that I print
> too much!
It is impossible for a Wheezy client to discover the queues on a 1.7
CUPS server without the help of cups-browsed on the server. Please read
the documentation.
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Create-Job IPP/2.0
> D [21/Dec/2014:16:55:49 +0100] [Job 35] printer-uri="ipp://192.168.1.12:631/printers/phsm"
Your queue on 192.168.1.12 is phsm
> D [21/Dec/2014:16:55:49 +0100] [Job 35] requesting-user-name="frenkiel"
> D [21/Dec/2014:16:55:49 +0100] [Job 35] job-name="prn_pr_31736"
> D [21/Dec/2014:16:55:49 +0100] [Job 35] document-format="application/postscript"
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Get-Jobs: successful-ok (successful-ok)
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Create-Job: successful-ok (successful-ok)
> I [21/Dec/2014:16:55:49 +0100] [Job 35] Print file accepted - job ID 2025.
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Set job-printer-state-message to "Print file accepted - job ID 2025.", current level=INFO
The queue accepts the job.
> D [21/Dec/2014:16:55:49 +0100] [Job 35] job-id=2025
> D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
> D [21/Dec/2014:16:55:49 +0100] Discarding unused printer-state-changed event...
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Sending file 1 using chunking...
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Send-Document: successful-ok (successful-ok)
> D [21/Dec/2014:16:55:49 +0100] [Job 35] PAGE: 1 1
> D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
> I [21/Dec/2014:16:55:49 +0100] [Job 35] Waiting for job to complete.
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Set job-printer-state-message to "Waiting for job to complete.", current level=INFO
Everything looks ok.
> D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
> D [21/Dec/2014:16:55:49 +0100] Discarding unused printer-state-changed event...
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Get-Job-Attributes: successful-ok (successful-ok)
> D [21/Dec/2014:16:55:49 +0100] [Job 35] update_reasons(attr=0(), s="+cups-ipp-conformance-failure-report,cups-ipp-missing-job-state")
Oops. What's going on here?
> I [21/Dec/2014:16:55:49 +0100] [Job 35]
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Set job-printer-state-message to "Waiting for job to complete.", current level=INFO
> D [21/Dec/2014:16:55:49 +0100] [Job 35] update_reasons(attr=1(none), s="(null)")
> D [21/Dec/2014:16:55:49 +0100] Discarding unused job-progress event...
> D [21/Dec/2014:16:55:49 +0100] Discarding unused printer-state-changed event...
> D [21/Dec/2014:16:55:49 +0100] [Job 35] Get-Printer-Attributes: successful-ok (successful-ok)
> D [21/Dec/2014:16:55:49 +0100] PID 32121 (/usr/lib/cups/backend/ipp) stopped with status 4.
> I [21/Dec/2014:16:55:49 +0100] [Job 35] Backend returned status 4 (stop printer)
> D [21/Dec/2014:16:55:49 +0100] Discarding unused job-state-changed event...
> I [21/Dec/2014:16:55:49 +0100] [Job 35] Printer stopped due to backend errors; please consult the error_log file for details.
Now we have got a problem. The ipp backend on the client gives up. It
doesn't fail for me, so what is different about your setup?
I haven't looked at the rest of the log in detail but I think it just
shows the client retrying. Except when we get to
> D [21/Dec/2014:17:19:54 +0100] process_browse_data: phsm@192.168.1.12 not found...
> D [21/Dec/2014:17:19:55 +0100] process_browse_data: phsm-env@192.168.1.12 not found...
> E [21/Dec/2014:17:20:08 +0100] Bad printer URI in browse data: ipp://192.168.1.19
> D [21/Dec/2014:17:20:08 +0100] process_browse_data: phsm-photo@192.168.1.12 not found...
> D [21/Dec/2014:17:20:24 +0100] [cups-polld 192.168.1.12:631] Found 3 printers.
> D [21/Dec/2014:17:20:24 +0100] process_browse_data: phsm@192.168.1.12 not found...
> D [21/Dec/2014:17:20:25 +0100] process_browse_data: phsm-env@192.168.1.12 not found...
> E [21/Dec/2014:17:20:38 +0100] Bad printer URI in browse data: ipp://192.168.1.19
> D [21/Dec/2014:17:20:38 +0100] process_browse_data: phsm-photo@192.168.1.12 not found...
> D [21/Dec/2014:17:20:54 +0100] [cups-polld 192.168.1.12:631] Found 3 printers.
This may or may not be significant for the printing process.
Reply to: