Problem printing big report...job keeps requeueing

[Luis Toro]

We have several network printers defined via jetadmin to an HP9000 HPUX 10.20 server. A user is trying to print a rather large report to a particular printer, and after printing 92 pages, the job stops and requeues. The cycle will continue until the job is cancelled. The same job prints fine on another printer. In researching the forum, I have turned off "True end of job". I have also copied over the interface scripts of the "good" printer, and still the same results. I have just turned off "Job Recovery" to see what happens. Attached is the configuration of the printer obtained by telnetting to it.

[Geoff Wild]

Idle time-out=0 seconds....

Why not set that instead to 270 seconds?

Default is 90.

Rgds...Geoff

[Simon Hargrave]

Is the report a basic text report, or more complicated with graphics etc? Is it possible that the printer is running out of memory (does it have less than the printer that works?)

Can you compare the differences in configuration between the printer that works, and the one that doesn't? Both on the printer itself, and on the unix interface script?

diff /etc/lp/interface/printer1 /etc/lp/interface/printer2

[Simon Hargrave]

Also perhaps check /var/adm/lp/log for anything strange?

[Luis Toro]

I did notice that. Based on the internal email chain on this issue, someone changed the idle timeout. It was 90, and the individual "disabled idle timeout". I assumed that by entering "0" for the timeout, it would cause it to be disabled.
I'll have him try 270

Thanks

[Luis Toro]

The only diifferences were in the PERIPH, TEOJ and PRINTERCFG variables. I have since made the scripts identical, except for the PERIPH. Nothing in the log of any value.

[Pepe Jimenez Muñoz]

Hi Luis,

Since time ago we get the same problem.

We can print very big jobs sending it directly to the printer:

# disable printer_name
# hpnpf â x printer_ip file_name

Hope this help !

[Luis Toro]

Sorry for the delayed response, but I had to wait for the monthend processing to see if this problem would resurface, and it has. I tried Pepe's recommendation, but I simply got a bunch of blank pages. I think this could be due to some control characters in the report file. I issued the following:
hpnpf -l /tmp/lplog -x ip_address filename
At this point I've asked the networking group to out a sniffer on to see if they see anything.

[Steve Steel]

Hi


Post output of

hpnpadmin -aEnv printerip


Steve Steel

[Luis Toro]

Steve,
I get:
*** Receive NO snmp response !
*** (printer down, cable off, or wrong Get community name?)

I can telnet to the printer, and get the config.