How do you debug the lp subsystem

How do you debug the lp subsystem

Post by Gary Gende » Thu, 10 Jul 2003 03:47:54



I've installed a network printer and it stopped working from one
particular machine.  Everything seems to be installed and running, but
any print job gets stuck in the queue.

My log has a bunch of errors like;

Jun 12 19:16:11 lpsched[193]: [ID 744729 lpr.info] fault (Lexmark_4039),
type (write root), status(14): exec exit fault

How does one go about tracking down a network printing problem?

Thanks,
Gary

 
 
 

How do you debug the lp subsystem

Post by Lars Tunkran » Thu, 10 Jul 2003 06:36:16



> I've installed a network printer and it stopped working from one
> particular machine.  Everything seems to be installed and running, but
> any print job gets stuck in the queue.

> My log has a bunch of errors like;

> Jun 12 19:16:11 lpsched[193]: [ID 744729 lpr.info] fault (Lexmark_4039),
> type (write root), status(14): exec exit fault

> How does one go about tracking down a network printing problem?

> Thanks,
> Gary

$ ps -ef | grep lpsched        (  make a note of the PID number )

$ truss -rall -wall -vall -fao trace-filename  -p PID_number_of_lpsched  &

   nnnnn   (  process number of the truss )

$ lp -p lexmark  filename

   ( wait untill you are sure that the error occured )

$ kill nnnnn  ( pid of the truss )

   study the  trace file.

//Lars

 
 
 

How do you debug the lp subsystem

Post by Greg Andre » Thu, 10 Jul 2003 10:47:40



>I've installed a network printer and it stopped working from one
>particular machine.  Everything seems to be installed and running, but
>any print job gets stuck in the queue.

>My log has a bunch of errors like;

>Jun 12 19:16:11 lpsched[193]: [ID 744729 lpr.info] fault (Lexmark_4039),
>type (write root), status(14): exec exit fault

>How does one go about tracking down a network printing problem?

You start with the basics:

   Version of Solaris?

And the printer basics:

   output of "lpget printer-name"
   output of "lpstat -v printer-name"
   output of "lpstat -lp printer-name"

  -Greg
--
Do NOT reply via e-mail.
Reply in the newsgroup.

 
 
 

How do you debug the lp subsystem

Post by Brad » Fri, 11 Jul 2003 09:18:33




> >I've installed a network printer and it stopped working from one
> >particular machine.  Everything seems to be installed and running, but
> >any print job gets stuck in the queue.

> >My log has a bunch of errors like;

> >Jun 12 19:16:11 lpsched[193]: [ID 744729 lpr.info] fault (Lexmark_4039),
> >type (write root), status(14): exec exit fault

> >How does one go about tracking down a network printing problem?

> You start with the basics:

>    Version of Solaris?

> And the printer basics:

>    output of "lpget printer-name"
>    output of "lpstat -v printer-name"
>    output of "lpstat -lp printer-name"

Another way would be to delete the print queue on the problem system and
restablish it.  If you want, before you delete the old queue, create a new
one to test it.

Brad

- Show quoted text -

Quote:>   -Greg
> --
> Do NOT reply via e-mail.
> Reply in the newsgroup.

 
 
 

1. LP subsystem problem

Hello,
I am running Solaris 2.5.1 on SS-5 and US-1 clients.
I have a HP 4000N using the Jetadmin software. It works fine until there
is a load
(read concentration of print requests) on the system. Then what happens
is it prints a
document with:

This job is recovered from page 152!!
(Note: There may be a few pages duplicated)

The print host does not report a error from lpstat -t
A remote host that was directing a print job to print host shortly after

this error condition reports a error from lpstat -t. Bouncing lpsched
locally
has no effect. Bouncing lpsched on print host clear the condition (that
was never reported)
and proceeds with outstanding print requests.

Is this senario familar to anyone?
Any work arounds?

Thanks

2. Sun E450-No display,No ok prompt.

3. LP Subsystem

4. Restoring overwritten ufsdump

5. looking for replacement lp subsystem

6. ADSL, MTU and upload traffic

7. Security Vulnerability in lp subsystem

8. kernel file/record locking problem

9. 2.6x86 boot subsystem: only 1 (of 3) DOS partition is bootable

10. lp interface for printing dos files

11. lp/jetadmin - I've done *something* stupid

12. lp(1) suid to lp-Secure files fail.