no prints after reboot

[Thomas Schler_1]

Hi!

I have problems with the print scheduler on HPUX 11.0:

Each time after booting, I'm not able to print on any printer known by the system. But the 'lpstat -t' command and SAM report that the scheduler is running. After running the 'lp' command no errors are printed by 'lp' or 'lpstat -t', all seems to be ok. The status of the printers are ok. The work-around is to stop the scheduler and start it again either using lpshut/lpsched or SAM.

Does anybody know this problem? What can I do to be able to print immediately after booting the system?

Thomas

[Steffi Jones_1]

Hello Thomas,

you can try to start the script from /sbin/init.d/lp start and see if that gives you any errors.

Then you might want to look if anything changed in the lp script found in /etc/rc.config.d

Make sure that this directory doesn't have any "old" files like lp.old or similiar.

Steffi Jones

[Thomas Schler_1]

/sbin/init.d/lp start/stop:

No error messages, normal behaviour. (No *old files.)

/etc/rc.config.d/lp:

This file just sets LP to 1. No *old files: ls /etc/rc.config.d/*lp* only returns /etc/rc.config.d/lp. LP is only set in /etc/rc.config.d/lp. "/sbin/init.d/lp start" only uses $LP.

[Steffi Jones_1]

Hi Thomas,

have a look at the following file:

/etc/rc.log

and see if you can find any errors when the system boots regarding lp.

What is the latest lp patch you have installed? You might want to install the lp patch, not because I know that it would fix the problem, but you would replace the binaries and that would help if you have some kind of corruption with the bins.

Steffi Jones

[Mark Vollmers]

I agree with Steffi- look in the rc.log file. I have a program (after I updated it) that won't start up after reboot, and I have to do it manually. It gives an error in the rc.log when it tries to run the startup script. I havn't gotten around to replacing the startup command (the S999xxxxxx command) so that it works right on it's own. If for some reason it isn't in the startup procedure, I think you could add it so that it.

Mark

[MANOJ SRIVASTAVA]

Hi

Try this

lpshut
rm /usr/spool/lp/FIFO
rm /usr/spool/lp/SCHEDLOCK
lpsched

I think this owuld solve your problem.

Manoj Srivastav

[Thomas Schler_1]

Hi all, thank you very much for your help, but nothing helps:

rc.log:

There are no error messages, no hints on any failures. The content is normal.

lp patch:

The latest patch regarding the lpspool subsystem installed on the system is PHCO_22365. That's the latest patch available from HP. I compared the outputs of 'what usr/bin/lp' and 'cksum usr/bin/lp' with the given strings in the patch description text, they are the same. So, the lp binary should be ok.

lpshut; rm /usr/spool/lp/FIFO; rm /usr/spool/lp/SCHEDLOCK; lpsched:

Did not solve the problem. As I mentioned, the work-around is this sequence of commands (/usr/spool/lp/FIFO and /usr/spool/lp/SCHEDLOCK are removed by 'lpshut').

[Ruediger Noack]

Hi Thomas,

some months (or years ?) ago i had a similar problem (HP-UX 10.20).
lpstat reportet sceduler is running, but there was no lpsched in process list (ps -ef). I found a core dump, i think in /var/spool/lp.
The problem was a corrupted outputq-file (var/spool/lp/outputq). My solution was to clear this file and restart the scheduler. You can modify the rc-script to do this.

May be it helps
Ruediger

[Thomas Schler_1]

Ruediger:

On my system, lpstat, too, reports that the scheduler is running but the process list also shows that the lpsched is running. I found no core file in /var/spool/lp. As you told I wiped out the outputq file (cp /dev/null outputq) but the old problem still remains. Still, no success.