Unable to start Print Spooler.

[Khalil Ahmed]

I am having problems with the print spooler on one of my HP9000 K570 boxes running HP-UX 11. When I try to start the print spooler through SAM it doesnâ t generate an error and just remains in the â STOPPEDâ state. When I send a test print the lpstat comes back but shows print jobs queuing up. I have tried to do an â inetd â câ but it seems to have no effect. Any suggestions?

[G. Vrijhoeven]

Hi,

make sure the queues are enabled and accept requests.
enable
accept

and....make sure the printer is turned on.

HTH,

Gideon

[MarkSyder]

Any messages in /var/adm/lp/log?

Mark Syder (like the drink but spelt different)

[Naveej.K.A]

hi,

what does
lpstat -t
gives???

#lpsched
#cancel -e printer name
#enable printer name


with best wishes
Naveej

[G. Vrijhoeven]

Hi,

sorrie misread the question...
# lpsched
from the command line?
and check Marks log file.

HTH,

Gideon

[Geoff Wild]

Actually - from command do a

lpsched -v

More info will be in the log...

then do a

lpstat -r

not too sure why it won't start from SAM - anything in the log?

Rgds...Geoff

[Khalil Ahmed]

When I do an lpsched -v I get the following output:

scheduler is running

When I do an lpstat -r I get...

scheduler is not running (!!!)

Also after having done an lpstat -t if I have a look at the log file /var/adm/lp/log I find error message similar to the ones below:

FIFO: project1: p not enabled not busy /dev/null

FIFO: project1 pid and id unknown

Disabling and re-enabling the printers makes no difference.

Any ideas guys? If not I may have to put a call into HP.

Khalil

[Mark Grant]

do a "ps -ef | grep lpsched" to see if the scheduler really is running.

However, you seem to be in the circular discussion that "lp" is famed for!

[Khalil Ahmed]

Problem resolved. Had a closer look at the log file and saw that there was a reference to a directory printertest located in the directory /etc/lp/member. This was causing the print spooler to throw a wobbler! Got rid of the printertest directory and now everyhting is back to normal and working fine.

Many thanks for your pointers.

Khalil