topic Re: memory fault when using lpstat command in Operating System - HP-UX

memory fault when using lpstat command

Dee_3 — Fri, 01 Aug 2008 18:32:20 GMT

I get the following error when I use the lpstat command:
list of printers then
printer lp89 is idle. enabled since Aug 1 09:31
fence priority : 0
Memory fault

I have applied 3 patches and rebuilt the kernel the way HP recommended and the issue still exists - any ideas? Thanks, Dee

Re: memory fault when using lpstat command

Tim Nelson — Fri, 01 Aug 2008 18:44:57 GMT

It could be one of any printer configs casing this.

Here is one idea.
use lpmgr to backup your printer configs.

remove all printers. Did the mem fault go away ?
-If so then manually/scriptually add all the printers back. Problem should be resolved.

-If not then you definately have a problem. Move or remove the /var/spool/lp/*status files. And try again.

you can always use lpmgr to put the entire config back to the way it was.

Interesting that a kernel rebuild was recommended for a lpstat issue, hmmmmmm....

Re: memory fault when using lpstat command

Dee_3 — Fri, 01 Aug 2008 18:53:48 GMT

the ideas are much appreciated. will give them a try - they use HUNDREDS of printers so this could be fun! thanks, Dee

Re: memory fault when using lpstat command

Tim Nelson — Fri, 01 Aug 2008 19:00:14 GMT

That is where the use of lpmgr is important to backup the configuration ( I figured you had a long list ).

If you really want to fix then here is where your scripting skills will come into play.

Script the removal and re-adds. Eventually you will run into the queue causing the issue?

Maybe start with remotes(LPR) first, if you have any?

Maybe run thought the list of printers and disable then re-enable. This has been known to fix stuff in the past also?

If you have a test/crash and burn server. Restore the queues with lpmgr over there to recreate the problem ?

/usr/sam/lbin/lpmgr -? will get you the options.
export with lpmgr
tar up your export directory
ftp to other server
untar
import

Re: memory fault when using lpstat command

Dennis Handly — Sat, 02 Aug 2008 09:15:34 GMT

You might try running lpstat in the debugger and see where it aborts. :-)

Or you could try various subsets of options and printers to see which ones are causing it to abort:
lpstat -a # or -c, -o, -p, -u, -v
lpstat -i # and try this with the others
lpstat -s
lpstat -t

If you find one that still aborts, these -a|-c|-o|-p|-u|-v take a list, so you can do your printers one by one until you find what aborts.