LP scheduler

[cl_5]

Hi
I??ve got a C3600 with HPUX11 and there are many printers in the lpspooler. The problem is every time I start with lpsched i get the message "scheduler is running". so far so good. But the scheduler dies immediately again. What??s the problem. Please help!
Many Thanks
carsten

p.s. Jetadmin is Rev 6.21

[James R. Ferguson]

Hi:

Try removing the file '/var/spool/lp/SCHEDLOCK' and then restart with 'lpsched'.

Regards!

...JRF...

[Ian Dennison_1]

Does /var/adm/syslog/syslog.log say anything? Or dmesg?

What is the latest patch set you have?

Share and Enjoy! Ian

[Jose Mosquera]

Hi,

This looks like a /var/spool/lp inconsistente (i.e. an accidental file/dir deletion inside)

Pls check that /var/spool/lp/SCHEDLOCK exist, if not try to touch it with 540 file premission an lp:lp owner. Also check if when you run lpsched again this file keep on, if not a file/dir deletion have happened in /var/spool/lp!

In this case try to restore from a previous system backup this /var/spool/lp dir.

If you have a saved copy of your last working spool configuration (SAM/Printers and Plotters/LP Spooler/Save-Restore Spooler Configuration) you just need run de following command:

/usr/sam/lbin/lpmgr -R -xsavedir=/var/sam/lp

After run this, your last spool configuration commonly saved in "/var/sam/lp" will be retored entirely into /var/spool/lp dir.


Rgds.

[Rainer von Bongartz]

Try this procedure:



1. Bring the scheduler down (even if it does not seem to be running)

lpshut

2. If lpshut is working correctly, the files /var/spool/lp/FIFO and /var/spool/lp/SCHEDLOCK. If these files still exist, remove them.
rm /var/spool/lp/FIFO
rm var/spool/lp/SCHEDLOCK

3. Clear the outputq file.

> outputq

4. Kill any lpsched processes that may be reported by: ps -ef | grep lpsched

5. Restart the scheduler.

lpsched

6. Verify that it is running:

ps -ef | grep lpsched lpstat -t | more NOTE: The first line should report the status of the scheduler.


Regards
Rainer

[Steve Steel]

Hi

Rainer is correct but if this is not enough try lpsched -v and look in /var/adm/lp/log for info.

Maybe a corruption somewhere


steve Steel

[Jose Mosquera]

Oppss,

About /var/spool/SCHEDLOCK just delete it, and if doesn't work try to follow my previous recommendations to restore /var/spool/lp dir

Rgds.

[cl_5]

Thanks for your help, but nothing had an effect. I heeded all of your suggestions.
The logfiles are empty and dmesg said also nothing. And I don??t have a functional backup. Any ideas?

Thanks
carsten

[James R. Ferguson]

Hi (again):

You noted that the scheduler "dies". Do you mean that:

# 'ps -ef|grep lpsched|grep -v "grep lpsched"'

...returns nothing?

Too, make sure that /etc/hosts, /etc/resolv.conf and /etc/nsswitch.conf are readable by everyone (permissions and ownership = 444 bin:bin).

Regards!

...JRF...