lpsched taking too many resources

[Dan Copeland]

Hi all,

I have a 11.00 system in which lpsched is taking 100% of CPU. Do u guys know what patch I have to install to fix this problem? Any help is appreciated.

[Sean OB_1]

Does it always take 100%?

Have you checked the spools to see what jobs are there?

Have you done an lpshut and lpsched to restart it, and if so does it still take 100%?

[S.K. Chan]

I don't think there a patch for this symptom (I may be wrong). On 11.00 there is a PHCO_27132 lpspool subsystem cumulative patch but I don't see anything that would help. Still if you don't have it already, you may want to install this patch.
http://support2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_27132&context=hpux:800:11:00

[Sandip Ghosh]

I think, lpsched is in hung condition. Try to restart the lpsched. It should be fine.

Sandip

[doug hosking]

PHCO_27132 looks like the most recent lp patch
for 11.00, but I'm not sure that this will help. A guess at a possible cause:

Occasionally the lp system can get into states where it consumes a lot of CPU because of corrupted queue files under /var/spool/lp.
Files like outputq, pstatus and qstatus seem like likely suspects. It's been a while since I've had to deal with such problems, but I seem to recall that recreating these can sometimes cure lpsched loops. (On rare occasions they somehow get corrupted.) If restarting lpsched doesn't solve your problem, I'd be tempted to do an lpshut, rename/recreate these and restart lpsched. Of course this could affect any print jobs queued at the time. As always, make backups of the existing files before changing things.

[Pete Randall]

Frank,

I'm assuming, since we've had absolutely no feedback from you, that this problem still exists. I've seen a couple of threads concerning runaway lpsched processes. Do a boolean forums search on +lpsched +resources and you'll find them.

Pete

[Sean OB_1]

Frank,

Just a reminder to give points out to those who answered your questions. It only takes a moment, and helps make the forums more useful to everyone.

Sean