I have a DU3.2g system that is experiencing odd errors with lpd after
a "maintenence" reboot this week. The system came up OK, but people
can't print now. This error comes up:
norman(8) ~> lpr .cshrc
lpr: connect: No such file or directory
jobs queued, but cannot start daemon.
In the syslog, there are thousands of lines like this:
Feb 26 08:56:32 norman lpd[28329]: pid=24337 (sig=-1,err=0)
Feb 26 08:56:34 norman lpd[28329]: pid=26013 (sig=-1,err=0)
Feb 26 08:56:34 norman lpd[28329]: pid=32010 (sig=-1,err=0)
In the archives, this seems to be regarded as normal when lpd spawns
off a sub-process. But, this seems to be a problem, too, since when
lpd is started up manually using the /sbin/init.d/lpd script, hundreds
of lpd daemons begin to run.
All this computer does is shunt the print jobs off to a VMS computer
(the same as our other DU systems--which aren't having problems), and
I tried routing through a different Unix box which then sent the job on to
the VMS server, but there was no change.
If anyone has encountered this before, or has any insight as to what
may be causing this problem, I'd be greatly appreciative. Of course,
I'll post a summary afterwards.
Dan Bongert dbongert_at_ssc.wisc.edu
SSCC Unix System Administrator (608) 262-9857
Received on Fri Feb 26 1999 - 16:49:31 NZDT