Hi all
Two node cluster of GS80s running 5.1apk3. Ever since we set up a
couple of printers, using lpr, we have gotten a lot of "lpd[nnnnnn]:
ERROR -- lp: cannot lock file lock: No such file or directory" messages.
Sometimes lp is another printer, seems to be always what was printed on
last. The funny thing is we don't do much printing; maybe two or three
jobs a day. But the jobs we do print come out fine. This first started
happening months ago; I first noticed because we got a few "high event
activity" e-mails and it turned out to be zillions of these messages.
Printing seems to work just fine, so foolishly I just thought "dumb
machine, bothering me with this stuff" and put a little filter in the
sysman EVM viewer to filter them out, then went back to sleep.
Then last week /var filled up all the way and I realize it's these
wretched messages. I deleted the lpr logs from the subdirectories
within syslog.dated to give us some breathing space, but I need a more
permanent solution. There are 2500 files in the evmlog directory,
mainly consisting of billions of these messages. There are now so many
I can't even run EVM from sysman, or even an evmget for the last five
seconds, without filling up the /tmp directory, i.e., the root
partition, with a jumbo temporary file.
Any ideas? Thanks in advance; I will summarize.
John
John Speakman
Manager, Clinical Research Systems
Memorial Sloan-Kettering Cancer Center
New York, NY, USA
646 735 8187 / speakman_at_biost.mskcc.org
=====================================================================
Please note that this e-mail and any files transmitted with it may be
privileged, confidential, and protected from disclosure under
applicable law. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that any
reading, dissemination, distribution, copying, or other use of this
communication or any of its attachments is strictly prohibited. If
you have received this communication in error, please notify the
sender immediately by replying to this message and deleting this
message, any attachments, and all copies and backups from your
computer.
Received on Mon Sep 29 2003 - 21:23:14 NZST