Hi! Usually SIGPIPE have three causes: 1. linked library problems, after reinstall or upgrade 2. Memory problems - try to run one full test on your server memory
Regards, MDA 2011/4/6 Anders Synstad <ander...@basefarm.no> > Hello all MON users, > > Last night, my MON server went a bit crazy, spamming down with "Caught > SIGPIPE" alarms. > > According to the graphs I got of the MON server, there was no unusual > activity related to number of processes, load, memory or io. > > The server hasn't logged anything unusual. I see no indications of running > out of fildescriptors, or oomkiller going on a frenzy. > > After a reboot, server was back to normal again. > > > Has anyone experienced MON going nuts and just sending "Caught SIGPIPE" on > every probe it forks out? I've had this happen once or twice before during > the last 2 years this server has been active. > > Or if anyone got any ideas what could be causing this. I know the basics of > the "Caught SIGPIPE" error itself, but I'm struggling with finding out what > has caused it. > > > > Regards, > Anders Synstad > Basefarm AS > > _______________________________________________ > mon mailing list > mon@linux.kernel.org > http://linux.kernel.org/mailman/listinfo/mon >
_______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
