lpstat problem - print jobs got stucked in print queue

[Tan Shirley]

Hi,

I have a funny problem here. I have a print queue name finsys and the print jobs got stuck in the unix print queue. The spooler is running, print queue is enabled, the Intel Netport Print Server (168.13.0.102) is also able to ping. But those print jobs just won't go out of the print queue. Below is the lpstat output which says :


#lpstat finsys
finsys-214 dgfin02 priority 0 Jan 29 17:19
(standard input) 4414 bytes
finsys-215 dgfin02 priority 0 Jan 30 14:47
(standard input) 4414 bytes
finsys-216 dgfin02 priority 0 Jan 29 17:17
(standard input) 974 bytes
finsys-217 dgfin02 priority 0 Jan 30 15:03
(standard input) 974 bytes
finsys-218 dgfin02 priority 0 Jan 30 17:10
(standard input) 1299 bytes
finsys-219 dgfin02 priority 0 Jan 30 17:12
(standard input) 1299 bytes
connection to 168.13.0.102 is down

newmfg: waiting for 168.13.0.102 to come up



Anyone can help ??

[Stefan Schulz]

Hmmm ... As far as i know ping is a very low level tool. If you can ping this Netport it doesn't necessarily mean that the Netport has all services available.

Did you already reset the Netport and lpshut / lpsched the print spooler?

I have sometimes problems with some netprinters here which can be resolved in this way.

Hope this helps. if not, perhaps you have some usefull information in /var/adm/lp/log.

[Cheryl Griffin]

It appears that there is something wrong with the print service.

Try restarting inetd daemon:
# inetd -c

[John Waller]

Is the physical printer on-line. I believe the netport can detect if a printer is not working cortrectly so will not pass requests to the printer. Route one solution is normally switch off printer , switch off netport, switch on printer , switch on netport, confirm lpsched is running and also priner queue is still enabled.

[Thomas Kollig]

Hi!

I had almost the same problem. I don't know why, but inetd was not running.

Bye,

Thomas