Operating System - HP-UX
1845896 Members
5027 Online
110250 Solutions
New Discussion

Jet Admin Printer message

 
John M. Fritsch
Occasional Contributor

Jet Admin Printer message

When I try to add a printer using the JetAdmin tool I get the following message

!! Cannot shut down the spooler with lpshut !!
Having tried for 5 times. Please shut down the spooler from
the command line, then re-run this configuration.

What should I do?
6 REPLIES 6
A. Clay Stephenson
Acclaimed Contributor

Re: Jet Admin Printer message

It's telling you to run lpshut from the command line.
If this fails, you should kill lpsched and then look in /var/spool/lp for FIFO,SCHEDLOCK, and/or CLD_FIFO. If any of these are present remove them.

Should you need to restart the spooler, the command is lpsched.
If it ain't broke, I can fix that.
Ken Hubnik_2
Honored Contributor

Re: Jet Admin Printer message

Try running lpshut from the command line or make sure nothing is printing with lpstat command and kill lpsched process and restart spooler.
MANOJ SRIVASTAVA
Honored Contributor

Re: Jet Admin Printer message

ALso you do a ps -aef | grep lp and close all the porcess if the lpshut fails .and then restart using lpsched.



Manoj Srivastava
Tom Danzig
Honored Contributor

Re: Jet Admin Printer message

Are you running JetAdmin as root?
Pete Randall
Outstanding Contributor

Re: Jet Admin Printer message

I've had instances where lpshut would not work but I was able to cycle the scheduler with and /sbin/init.d/lp stop and /sbin/init.d/lp start.

Pete

Pete
Bill Hassell
Honored Contributor

Re: Jet Admin Printer message

This is no different than running lpshut and it truly does not shutdown lpsched. The reason is simple: one or more of the lpsched processes cannot be terminated, usually due to a network or datacom issue. Use this command to find all the broken lpsched processes:

ps -fulp

Then kill each one with -15, and if that doesn't get them all, use kill -9. Make a note about the printer names that had problems--they caused the issue. Now run jetadmin and you'll be fine.


Bill Hassell, sysadmin