can not print

[Michael_33]

Hi All,

I found my printing job was hung.
I got this message when I do lpstat -t

server1: waiting for queue to be enabled on server7

device for printer1: /dev/null
printer1 accepting requests since Jul 3 15:46
printer printer1 now sending printer1-6059 to server7. enabled since
Aug 8 10:37

I can ping server7 successfully, but I have 2 lpsched daemon in server1. OS: hp-ux 10.20

Any idea?

Thanks

[A. Clay Stephenson]

Hi:

Only 1 lpsched allowed. On server1 do this:
lpshut
then do a ps -e to get the pid of the remaining lpsched and kill it.
cd /var/spool/lp
If FIFO or SCHEDLOCK files are still there, remove them.
lpsched to restart the scheduler

I think that will fix you, Clay

[Michael_33]

Hi Clay,

I have rerun the lp daemon, but when I do a
lpstat -t, it said printer1 is down, btw
printer1 is a remote printer ( actually is not
a real printer, it is just a "soft-copy" )
now I do a # enable printer1, and no error messages returned.

and this time I got 3 lpsched daemon! is it possiable something wrong with the remote server(server7)?

Thanks a lot!

[Victor_5]

Generally, Clay's suggestion can solve most of the cases of spooler. It looks like something wrong with your remote printer's - printer1 - own configuration, maybe re-configuration can helps? Sometimes, it is the easiest way to go.

[MANOJ SRIVASTAVA]

Hi Michael

You would need to reconfigure the printer again. Also you can look inot FIFO and SCHEDLCK files under /usr/spool/lp directory and remove them after manually shutting down the lp scheduler and then restarting after deletting these files .

In case this doesnt work then the option left is to remove and recreate the printer.


Manoj Srivastava

[Michael_33]

Hi All,

Thanks for the reply, but when I do a lpshut,
I can not find the 2 files under /var/spool/lp.
is it normal?

is it possible something wrong with "outputq"?

[Victor_5]

You can not see FIFO and SCHEDLOCK after shutdown your spooler if your spooler can work well. In your case, it is normal.

[Michael_33]

any other suggestion? thanks.

[Kelli Ward]

Just for fun, check this. Verify that the hostname (and IP Address) on your server and client are completely identical (in /etc/hosts) and that your printer set up has the hostname correctly listed right down to letter case. Make any applicable changes, delete any current print jobs and re-enable your printer, if neccessary.
I have had many cases of printers no longer working because a network address or hostname change. Since you can ping server7, focus on your client first.
Hope this helps,
K

[Kelli Ward]

Oops, my bad.
Focus on the server first.
Also, check to make sure both server and client have read permission on the /etc/hosts file.
Remote printer communication is a 2 way street. Any break in the line and it won't work at all. On a general basis.
K