Spooler Problems!

[Mike_21]

I am having a few problems restarting the scheduler. It says it's started, but it really isn't? Any ideas?

Thanks

# /usr/sbin/lpshut
usr/sbin/lpshut: scheduler not running
#/usr/sbin/lpsched
cheduler is running
#lpstat -r
cheduler is not running

[A. Clay Stephenson]

Typically this happens when the lockfiles are not removed or more than 1 lpsched process is running.

1) lpshut
2) do a ps -e | grep lpsched. If another lpsched is running kill it using the process id obtained from ps.
3) cd /var/spool/lp
if the files FIFO or SCHEDLOCK are found, remove them
4) lpsched

That should fix you.

[Jay Newman]

If you want to get a better idea of what is going on, try again but use the command
lpsched -v
...this will write a verbose record to
/var/adm/lp/log .
Probably don't want to leave it that way, but should help you get a better picture of what is going on.

[Victor_5]

After shutdown the spooler, check
/var/spool/lp
If there are FIFO and SCHEDLOCK, remove them and try to start your spooler again.

[Mike_21]

FIFO and SCHEDLOCK don't exist.. Is there a command to cancel all jobs pending in the print q?

cancal maybe?

[Vincent Farrugia]

The command cancel -e cancels all the print jobs from all printers.

Vince

[Animesh Chakraborty]

Hi,
First cancel all the print jobs with cancel -e
then try /sbin/init.d/lp stop and /sbin/init.d/lp start.

best of luck
Animesh

[Mike_21]

The problem was that someone tried to remove a print queue the wrong way. The log file was looking for a directory in /var/spool/lp/request that did not exist. I simply added the directyory back and the spooler came back up.

[Kiyoung]

What about this.

# /usr/lib/lpshut
# cd /usr/spool/lp
# cat /dev/null > pstatus
# cat /dev/null > qstatus
# cat /dev/null > output
# lpsched

Best of luck.