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: 

LPR.LOG

Slayer Slayer
Frequent Advisor

LPR.LOG

Hello All,

Today i was looking at the /var/adm/syslog.dated/current and i´ve noticed that the lpr.log was growing very fast.
I edited the file and i got many messages like this :
ERROR -- Wizard to SysAdmin: please issue t
his command to fix your print setup: 'chown daemon /usr/spool/lpd3/receb'
ERROR -- ... otherwise creating the print f
ilter error files will fail and filter errors will not be logged.

And also a Warning :

WARNING -- PrepareFilter: cannot open file
errsaaFwga, printer hpcqr, error Permission denied

Does anybody knows what these are ?

TIA

Regards

Brun
24 REPLIES
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Hi,

the spool dirs must be owned by daemon.
So use
chown daemon.daemon /usr/spool/lpd3/receb
so that files can be created.

greetings,

Michael
Ralf Puchner
Honored Contributor

Re: LPR.LOG

sound like you used the unsupported way creating printer entries: vi

Please use the supported tools like lprsetup/lprconfig etc. next time to prevent any problems.
Help() { FirstReadManual(urgently); Go_to_it;; }
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Hey Guys...
Thanks for the response.
Those 2 errors above were fixed after the change of the owner.

But i also noticed another error.

ERROR -- read_some_chars: read() failed, er
ror: Bad file number.

What about this one ..
I have checked the forum but i haven´t found anything about it.
Hope you can help me.
THanks a lot ..

Bru
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Hi,

are we still talking lpr.log?
If so, can you post the context?
At first thought it looks like a network problem.

hth,

Michael
Ralf Puchner
Honored Contributor

Re: LPR.LOG

it is a configuration problem, mostly parameter lp= is wrong - but this can not be happen if using lprconfig/lprsetup.

So it seems problem is a follow on to previous manual editing of printcap.

Help() { FirstReadManual(urgently); Go_to_it;; }
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Hi,

please post the printcap!

thanks,

Mochael
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Hey man sorry for the delay i wasn´t being able to connect to the web page.

But here is the printcap file.

# POA - HP4000
lp|lp0|0|rhp4000:\
:lf=/usr/adm/lperr:\
:lp=:\
:rm=hp:\
:rp=text:\
:sd=/usr/spool/lpd:\
:sh:
# POA - Cheque
lp1|1|cheque:\
:af=/usr/spool/lpd3/cheque/acct:\
:if=/usr/local/etc/smbcheque:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/cheque:
# POA - HP895
lp2|2|HP895:\
:af=/usr/adm/lp2acct:\
:if=/usr/lbin/lpf:\
:lf=/usr/adm/lp2err:\
:lp=:\
:rm=hp895:\
:rp=text:\
:sd=/usr/spool/lpd2:\
:sh:
# POA - HP680 Compras
lp3|3|hpcompra:\
:af=/usr/spool/lpd3/hpcompra/acct:\
:if=/usr/local/etc/smbhpcompra:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/hpcompra:
# POA - HPCQR
lp4|4|hpcqr:\
:af=/usr/spool/lpd3/hpcqr/acct:\
:if=/usr/local/etc/smbcqr:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/hpcqr:
# GRV - HP4050 Adm
lp5|5|hplaser:\
:af=/usr/adm/lp5acct:\
:lf=/usr/adm/lp5err:\
:lp=:\
:rm=hplaser:\
:rp=txt:\
:sd=/usr/spool/lpd5:\
:sh:
# POA - HP4L Recebimento
lp7|7|rhp4l:\
:lf=/usr/adm/lp7err:\
:lp=:\
:rm=hp4l:\
:rp=txt:\
:sd=/usr/spool/lpd7:\
:sh:
# POA - FX2180 NF
lp8|8|nota:\
:af=/usr/spool/lpd3/nota/acct:\
:if=/usr/local/etc/smbprint:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/nota:
# SCS - Financas
lp9|9|sccambio:\
:lf=/usr/adm/lp9err:\
:lp=:\
:rm=sccambio:\
:rp=text:\
:sd=/usr/spool/lpd9:\
:sh:
# SCS - Financas
lp10|10|scfint5m:\
:lf=/usr/adm/lp10err:\
:lp=:\
:rm=scfint5m:\
:rp=text:\
:sd=/usr/spool/lpd10:\
:sh:
# SCS - Compras
lp11|11|scs01:\
:lf=/usr/adm/lp11err:\
:lp=:\
:rm=printscs:\
:rp=hpcompq6:\
:sd=/usr/spool/lpd11:
# GRV - FX2180 Nota
lp13|13|fx_2180:\
:lf=/usr/adm/lp13err:\
:lp=:\
:rm=dasgrfs1:\
:rp=matricial:\
:sd=/usr/spool/lpd13:
# GRV - LEXMARK Recebimento
lp14|14|receb:\
:af=/usr/spool/lpd3/receb/acct:\
:if=/usr/local/etc/smbreceb:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/receb:
# GRV - HP1600 Sequenciamento
lp15|15|hpseq:\
:af=/usr/spool/lpd3/hpseq/acct:\
:if=/usr/local/etc/smbhpseq:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/hpseq:
# GRV - ZEBRA 105S
lp16|16|zebragrv:\
:lf=/usr/adm/lp16err:\
:lp=:\
:rm=printgrv:\
:rp=zebragrv:\
:sd=/usr/spool/lpd16:
# POA - KYOCERA
poafisc|lp17:\
:lf=/usr/adm/lp17err:\
:lp=:\
:rm=10.251.21.194:\
:rp=lp1:\
:sd=/usr/spool/lpd17:
# POA - MANUFATURA
pofab|lp19:\
:lf=/usr/adm/lp19err:\
:lp=:\
:rm=10.251.21.21:\
:rp=text:\
:sd=/usr/spool/lpd19:
# POA PLOTTER ENGENHARIA
plotter|lp6:\
:lf=/usr/adm/lp6err:\
:lp=:\
:rm=10.251.21.17:\
:rp=text:\
:sd=/usr/spool/lpd6:
# POA - KYOCERA
poafisc|lp17:\
:lf=/usr/adm/lp17err:\
:lp=:\
:rm=10.251.21.194:\
:rp=lp1:\
:sd=/usr/spool/lpd17:
# POA - MANUFATURA
pofab|lp19:\
:lf=/usr/adm/lp19err:\
:lp=:\
:rm=10.251.21.21:\
:rp=text:\
:sd=/usr/spool/lpd19:
# POA PLOTTER ENGENHARIA
plotter|lp6:\
:lf=/usr/adm/lp6err:\
:lp=:\
:rm=10.251.21.17:\
:rp=text:\
:sd=/usr/spool/lpd6:
# PC&L POA
xerox|lp12:\
:lf=/usr/adm/lp12err:\
:lp=:\
:rm=10.251.21.20:\
:rp=text:\
:sd=/usr/spool/lpd12:

Thanks a lot

Regards
BRu
Ralf Puchner
Honored Contributor

Re: LPR.LOG

and what is the exact error message containing the name of printer?

As written before check the lp= keyword which leads to the problem. lpd tries to read some characters from the remote system but cannot due to wrong printcap entry or used mechanism.
Help() { FirstReadManual(urgently); Go_to_it;; }
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Hi,

just wondering, how this would work:
# GRV - HP1600 Sequenciamento
lp15|15|hpseq:\
:af=/usr/spool/lpd3/hpseq/acct:\
:if=/usr/local/etc/smbhpseq:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/hpseq:

no remote machine?

Michael
Ralf Puchner
Honored Contributor

Re: LPR.LOG

that's one reason why lprconfig is the only supported way.

But it seems useless to correct entries made manually leading to follow on problems.
Help() { FirstReadManual(urgently); Go_to_it;; }
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Hey Guys,

Here is the error that the printer is giving.

ERROR -- read_some_chars: read() failed, error: BAd file number

I am chekcing everything to try to solve this problem.

THanks a lot for your Help..

Appreciate

BRuno
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Bruno,

we need to know, which printer is involved.
That error message is in lor.log?

please check the log files of the printers specified by lf= to see, which printer it is.

Michael
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Hey Michael .

These are the printers that are having the errors. I checked the lpr.log to find that out.

# POA - FX2180 NF
lp8|8|nota:\
:af=/usr/spool/lpd3/nota/acct:\
:if=/usr/local/etc/smbprint:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/nota:
---------------------------------------------
# GRV - LEXMARK Recebimento
lp14|14|receb:\
:af=/usr/spool/lpd3/receb/acct:\
:if=/usr/local/etc/smbreceb:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/receb:
---------------------------------------------
# GRV - HP1600 Sequenciamento
lp15|15|hpseq:\
:af=/usr/spool/lpd3/hpseq/acct:\
:if=/usr/local/etc/smbhpseq:\
:lp=/dev/null:\
:mx#0:\
:sd=/usr/spool/lpd3/hpseq:

But notice that all of these printers do not have the LF parameter.

THanks a lot again for your pacient.

REgards

Bruno
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Bruno,

that's something to work on. All of these printers do not have a device to print to. You may want to add the lf option to give it at least a chance to express itself. Also find out, if this isn't just junk entries and kick them out or redo them, if someone needs them.

Michael
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Michael,

I will checked that out ..

Can i just add the LF parameter to these printers ?

Thanks

BRuno
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Bruno,

refer to the other printer who do have lf and do it likewise.

Michael
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Michael i have a new question .
If you have time please help me out.

What is the lock file under the printer directory ?
I also have thi message about lock file.
DEBUG -- printjob: got lock on file 'lock' .Why is this ? do you know ?

THanks

Bruno
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Bruno,

in order to avoid 10 lpd printing the same file, only the one, who gets the lock file, is allowed to handle a queue, see man lpd

Michael
Ralf Puchner
Honored Contributor

Re: LPR.LOG

Bruno,

If you use the supported way next time there would be no problem at all, missing parameters are not possible by using the setup tools delivered with the OS and you will get support.

The "..read.." error message is typically a communication setup problem as written before. The lf parameter is such a parameter necessary for communication.

Help() { FirstReadManual(urgently); Go_to_it;; }
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Dear Ralf,

this is getting a little annoying!
Didn't it occur to you, that this might be the old stuff from a predecessor?

There is no need for repeating the same stuff again, which I think, he understood already.

Michael
Ralf Puchner
Honored Contributor

Re: LPR.LOG

I'm not sure if he really understood, it seems be an "ignoring". But fact is that with using the official setup tools such problems and all follow on problems will not occure.

I've spent a lot of time telling people doing a setup "manually" is not supported and in case of a problem customers are on their own.

So if I, as a HP representative help them doing some unsupported stuff he will blame HP if an additional problem occurs from that editing. Hell I've seen this so many times before during my time in Tru64 support. And I've seen many escalations rejected due to unsupported usage/handling.

So Michael, best way is if Bruno throws away the printcap and reconfigures the whole printing system via lprsetup. Why frickling around old stuff if a clean recreate will fix all problems within minutes?
Help() { FirstReadManual(urgently); Go_to_it;; }
Michael Schulte zur Sur
Honored Contributor

Re: LPR.LOG

Ralf,

I do understand your concern. You must know, what you do, if you edit printcap manually. I wonder however, if Bruno has all the information to throw away the printcap and start from scratch and use lprsetup.

Michael
Ralf Puchner
Honored Contributor

Re: LPR.LOG

Michael,

that's on of the other mysterious things. If someone is not familiar with a system why doesn't he spent time to learn the basics or differences instead of "doing something". An Alpha is mostly part of a production environment and not a simple PC system for testing.

A supported setup tool will guide you through the setup (it is also well explained within the documentation). It doesn't replace knowledge but makes it very easy to lower the risk.



Help() { FirstReadManual(urgently); Go_to_it;; }
Slayer Slayer
Frequent Advisor

Re: LPR.LOG

Hey guys ,

I really appreciate all yor help.
I am reading a lot of stuff about tru64 to get to know all the things you guys know.
I am planning to recreate the printcap file. but using the lprsetup to do the configuration stuff.
Hey guys lets not get frusted about it.We are also in a forum to learn and to teach.

Thanks for all your help.

Regards

Bruno