Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
cancel
Showing results for 
Search instead for 
Did you mean: 

Printing

Jäger Helmut_1
Occasional Advisor

Printing

I have severe problems with printing:
Version: Compaq Tru64 UNIX V5.1B (Rev. 2650); Fri Nov 4 10:49:47 CET 2005
Patches:
- T64V51BB25AS0004-20040616 IOS540
- T64V51BB25AS0004-20040616 OSF540
- T64V51BB26AS0005-20050502 IOS540
- T64V51BB26AS0005-20050502 OSF540
When I try to print some files with "lp" or "lpr" then I will get the following error:
Memory fault
And no print is done!!!

Any help would be accepted with pleasure!!

Helmut Jaeger
12 REPLIES
Ivan Ferreira
Honored Contributor

Re: Printing

What is the output of lpc stat?

Is the lpd daemon running?

Check your filesystem space.

Verify the cksum of these files, I will post the files in mys 5.1b pk5 chksum:

960818503 191728 /usr/lbin/lpd
960818503 191728 /usr/lbin/lpd
960818503 191728 /usr/lbin/lpd
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Ivan Ferreira
Honored Contributor

Re: Printing

Run this also:

/usr/lbin/fverify -n < /usr/.smdb./OSFPAT02606900540.inv
/usr/lbin/fverify877758 (0) begin logging at Fri Nov 4 07:48:27 2005

0 verification errors encountered.
0 corrections performed.
/usr/lbin/fverify877758 end logging at Fri Nov 4 07:48:27 2005

No errors should be reported.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Jäger Helmut_1
Occasional Advisor

Re: Printing

In attached file you can see my results.
I'm surprised, because the verify says, that no files for lpd, lpc, .... are not existing, but they are real existing. So I'm worrying in this case!!

What to do?

Kind regards
Ivan Ferreira
Honored Contributor

Re: Printing

I forgot to methion that before running fverify, you need to do:

cd /

Have you verified the cksum for the files also?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Jäger Helmut_1
Occasional Advisor

Re: Printing

Now I did the verify from / and no errors were reported.
I also have the same chksum with /usr/libin/lpd!
Jäger Helmut_1
Occasional Advisor

Re: Printing

I found this:
http://ftp.support.compaq.com.au/pub/patches/Digital_UNIX/v4.0d/DIGITAL_UNIX_V4.0D/doc/txt/OSFPAT00118800425.abs

But I think, this is for Unix 4.0x, but the same message and errors!!!
Ivan Ferreira
Honored Contributor

Re: Printing

Is this the only problem related to memory. Any other application/command with the same issue?

Does the dia command reports any errors?

I saw problems like this (in other linux version) that was solved by running fsck, in this case, verify.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Johan Brusche
Honored Contributor

Re: Printing


A "Memory fault" is not a HW error, but caused by a program trying to access memory that is NOT allocated to itself.

A "Memory fault" normally leaves a core-file
behind in the cwd. One can examine this core with : ladebug /usr/bin/lpr core.
Then the 't' or 'where' command shows the program stack.

Maybe /etc/printcap got scrambled . You can check for errors in the file and the associated print environment with the command "lpc check all"

You could then post the results....

Rgds,
__ Johan ./

_JB_
Ivan Ferreira
Honored Contributor

Re: Printing

Agree, you can use cat -e /etc/printcap to check for non printable characters. You can also copy that file and start with a basic printcap file with just one printer to see if the problem persists.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Jäger Helmut_1
Occasional Advisor

Re: Printing

Thanks for your efforts!

This ist the output of the ladebug:
# ladebug /usr/bin/lpr core
_bsd_tgetent() failed with status 0
Welcome to the Ladebug Debugger Version 69 (built May 4 2003 for Tru64 UNIX)
------------------
object file name: /usr/bin/lpr
core file name: core
Warning: cannot open core file : core
Reading symbolic information ...done
Error: could not start debuggee
Could not start process for /usr/bin/lpr
No image loaded ... Recovering ...
(ladebug) t
The "where" command has failed because there is no running program.

This is the output of "lpc check all":
/etc/hosts.equiv: Access is restricted to about 2 hosts or netgroups.
/etc/hosts.lpd: Access is restricted to 1 hosts.
all: unknown printer
No configuration problems found.

I tried also to start with only one printer (created with lprsetup), but with the command "lp dPrinter test.txt" it gave me the same error:
memory fault

Some suggestions???
Jäger Helmut_1
Occasional Advisor

Re: Printing

Now it seems I found the error:
I copied the "printcap.dat" from an old Unix 4.0 System and some Parameters (like zf or Pc) are not supported under V5.1.
When I started with a new (clean) printcap.dat, I also did set this parameter by hand, because I did believe, I need them.
With a really clean new printcap it now works and I can print!!
Many thanks for your help!!!

Helmut Jaeger
Jäger Helmut_1
Occasional Advisor

Re: Printing

I did find the solution as I posted before!

Thanks to all!