vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Andy wrote: > I am getting the following error in my messages file every couple of > minutes: > > lp[xxxxx]: [ID 889138 lpr.error] Warning: Received SIGPIPE; continuing > > The server is a SunFire V880 running SOlaris 8 2/02 + patches (but not > all the latest ones ;-). The server supports around 75-100 users and we > have 14 printers. Each of these printers is directed to an LPD queue on > a Windows 2000 server. > > I've "had a google" for the issue, but only seem to see recommendations > on the server side. We have disabled the printer service in inetd.conf > so this is either a client side issue (options in printers.conf?) or a > Windows server issue. > > If anyone can provide any ideas on how to get rid of the error I would > really appreciate it! The error simply means that connectivity b/t the client and server has been lost. The Sun side will continue to retry. It could be a dead print job triggering this. In this case, I'd say it's probably the sun print client/Win2k print server relationship. I'd do the following: clean out /var/spool/print including the .printd.lock file shut down any running printd processes get the latest lp patch for Solaris 8: 109320 is the number, I think the latest release is 06. Turn the in.lpd in the /etc/inetd.conf file back on. Shutting this off will have no effect on the problem and will cause other issues, like the inability to cancel print jobs even if you aren't a print server. |
| ||||
| ML Starkey <martha.starkey@sun.com> writes: > >clean out /var/spool/print including the .printd.lock file > >shut down any running printd processes > But reverse the order in which you do those things. I.e. kill any printd processes before deleting files in /var/spool/print. -Greg -- Do NOT reply via e-mail. Reply in the newsgroup. |