Operating System - HP-UX
1820619 Members
1857 Online
109626 Solutions
New Discussion юеВ

Re: Scheduler can't be started

 
SOLVED
Go to solution
Mihaita Bighiu
Advisor

Scheduler can't be started

Hi,
After I did a full restore from Online backup the sheduler can't be started ( Unix FS full backup on HP-UX 11.00).
After restore completed successfully and reboot the system, I found on /etc/rc.log

Start print spooler
Output from "/sbin/rc2.d/S720lp start":
----------------------------
scheduler is running
line printer scheduler started

but there are no lpsched processes.

The command:
#lpsched returns:
scheduller is running

#/sbin/init.d/lp stop returns
EXIT CODE: 1
and the commnad
#/sbin/init.d/lp start returns
scheduler is running
line printer scheduler started

All lock files from /var/spool/lp have been removed and are not generated after scheduler have been restarted.

Do someone had the same problem before? What is wrong and what could be a solution in this case? Otherwise the system is up and running OK (Oracle and SAP)

Thanks for feedback,
MB.


5 REPLIES 5
S.K. Chan
Honored Contributor
Solution

Re: Scheduler can't be started

You mentioned you did a full restore from backup, in my mind I would want to check if the permission/ownership is correct.

# cd /usr/sbin
# ll lpsched
==> It should be (-r-sr-xr-x root:bin)
# ll -d /var/spool/lp
==> It should be (drwxr-xr-x lp:bin)

For locks .. double check this ..
# ll /var/spool/lp/tmplock
# ll /var/spool/lp/SCHEDLOCK

Then try restarting lpsched ..
# lpshut
# lpsched

It it does not work, what's the error ?


Sanjay_6
Honored Contributor

Re: Scheduler can't be started

Hi,

Try to shutdown the scheduler.

/usr/lib/lpshut

do a ps -ef and see if the scheduler is running.

to start the scheduler manually, try

/usr/lib/lpsched
do you have a printer configured.

Hope this helps.

Regds
Rich Wright
Trusted Contributor

Re: Scheduler can't be started

If no lpsched processes are running, remove the /var/spool/lp/SCHEDLOCK and /var/spool/lp/FIFO files and then issue the "lpsched" command.
If it still fails look at the /var/spool/lp/log file for any clues.
Mihaita Bighiu
Advisor

Re: Scheduler can't be started

Hi,

Thanks for your quik answers, but I still have the same problem after I did stop/restart scheduler ( lpsched -v), recreate the log file.
On log file I could see:


lpsched: can't open request directory request/ihp2_test/
FIFO: Destinations --
FIFO: lct7_p33: p not enabled not busy /dev/null
FIFO: ihp2: p not enabled not busy /dev/null
FIFO: DIST_1134_18: p not enabled not busy /dev/null
FIFO: pdc2_p34: p not enabled not busy /dev/null
FIFO: pdc2_p39: p not enabled not busy /dev/null
FIFO: pdc2_p46: p not enabled not busy /dev/null
FIFO: pdc2_p49: p not enabled not busy /dev/null
FIFO: pdc2_p59: p not enabled not busy /dev/null

FIFO: Printers --
FIFO: lct7_p33 pid and id unknown
FIFO: ihp2 pid and id unknown
FIFO: DIST_1134_18 pid and id unknown
FIFO: pdc2_p34 pid and id unknown
FIFO: pdc2_p39 pid and id unknown
FIFO: pdc2_p46 pid and id unknown
FIFO: pdc2_p49 pid and id unknown
FIFO: pdc2_p59 pid and id unknown
FIFO: Classes --
***** STOPPED Jul 11 16:21 *****
But I did restore /etc/lp direstory and all printers are there.

???

Thanks,
MB
Mihaita Bighiu
Advisor

Re: Scheduler can't be started

Hi,


Thanks to everibody. The problem was in /etc/lp and I had to restore this directory again.

have a nice day
MB.