<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html><head><meta http-equiv="content-type" content="text/html; charset=UTF-8"></head><body style="font-family:Arial;font-size:14px"><p>
all,<br><br>
still struggling with printing ... :-(<br><br>
I have a network printer on my local LAN, which is powered-on.<br><br>
I can print from my client Ubuntu 14.04 to this network printer.<br><br>
I have "printer" exported in the TL-client program for becoming accessible at the TL-agent.<br><br>
I login to the TL-agent, and see the "thinlocal" queue, but "lpstat -t" show status "The printer is not responding" :<br><br>
# lpstat -t<br>
scheduler is running<br>
no system default destination<br>
device for thinlocal: thinlocal:/<br>
thinlocal accepting requests since wo 14 okt 2015 21:16:55 CEST<br>
printer thinlocal is idle. enabled since wo 14 okt 2015 21:16:55 CEST<br>
The printer is not responding.<br><br>
I found somewhere that the file /etc/cups/client.conf had to be created with a "ServerName" directive, to ensure that all jobs are forwarded to another host, in this case that other host would need to be the TL-server. So I created that file, restarted CUPS on the agent, but still "not responding".<br><br>
I checked on the TL-server, also this one shows the same status of print queue "thinlocal", altough from the ThinLinc admin manual it is not clear to me how the connectivity to or the status of a 'local' printer from a client-session can be inspected.<br><br>
The file /etc/cups/printers.conf on the agent, contains</p>
<p>
<Printer thinlocal><br>
UUID urn:uuid:fca79d8b-be0d-3bd4-5a19-359bccf24959<br>
Info thinlocal printer (special queue)<br>
Location The thin clients local printer<br>
DeviceURI thinlocal:/<br>
PPDTimeStamp *<br>
State Idle<br>
StateTime 1443430680<br>
Type 4180<br>
Accepting Yes<br>
Shared Yes<br>
ColorManaged Yes<br>
JobSheets none none<br>
QuotaPeriod 0<br>
PageLimit 0<br>
KLimit 0<br>
OpPolicy default<br>
ErrorPolicy retry-job<br>
</Printer><br><br>
I assume this file has been created by the "tl-setup" script, because I did not create nor alter it.<br><br>
The CUPS log "/var/log/cups/access_log" on the TL-server show that a print job from the agent was correctly accepted:<br><br>
10.50.0.53 - - [14/Oct/2015:20:18:16 +0200] "POST /printers/thinlocal HTTP/1.1" 200 122257 Print-Job successful-ok<br><br>
However the CUPS error log "/var/log/cups/error_log" shows immediately<br><br>
E [14/Oct/2015:20:18:21 +0200] [Job 1] The printer is not responding.<br>
...<br><br>
I set the logging level of CUPS on the TL-server already at DEBUG level, checked the /var/log/cups/error_log, but no extra information is logged to allow troubleshooting.<br><br>
I checked the /var/log/vsmserver logfile and found a single, maybe relevant line around the timestamp (1 second later) when the print job was submitted :<br>
...<br>
2015-10-14 20:18:17 DEBUG vsmserver: Handling connection from ('127.0.0.1', 60012)<br>
...<br><br>
Any some clue what needs to be done to get this printing ?<br><br>
cheers<br>
Rob<br>
</p></body></html>