headers
Anders Synstad | 6 Apr 2011 15:48
Picon

Problems with "Caught SIGPIPE"

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
Permalink | Reply | 2 comments |
headers
Marco A P D'Andrade | 6 Apr 2011 18:17
Picon

Re: Problems with "Caught SIGPIPE"

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 <andersns <at> 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 <at> linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon

_______________________________________________
mon mailing list
mon <at> linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
Permalink | Reply | 1 comment |
headers
Anders Synstad | 7 Apr 2011 10:09
Picon

Re: Problems with "Caught SIGPIPE"

My initial thought is memory aswell, but I haven't had the time to check 
it yet.

I think that if the problem was related to libraries, I would see more 
of it, and not a random meltdown months appart.

Regards,
Anders

On 04/06/2011 06:17 PM, Marco A P D'Andrade wrote:
> 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 <andersns <at> basefarm.no <mailto:andersns <at> 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 <at> linux.kernel.org <mailto:mon <at> linux.kernel.org>
>     http://linux.kernel.org/mailman/listinfo/mon
>
>
Permalink | Reply | 0 comments |
headers
Nathan Gibbs | 26 Apr 2011 01:09

mon.cgi CMR8 Released

OK, I'm done hibernating for the winter, while crawling out of my cave, I
thought that I'd bring some software updates with me.

Updated mon.cgi.

http://www.cmpublishers.com/oss/#moncgi

Output Work
        Logo positioning support
        svc_details output organization
        More formalizing of links.
        A ton of XHTML Compliance fixes.
        ( I thought I covered that in the initial release. )
        Added CM Release Version info to $VERSION
Code Work
        Generalize query_opstatus command replaces specific commands.
        Better concealment of non authorized commands.

Enjoy.

--

-- 
Sincerely,

Nathan Gibbs

Systems Administrator
Christ Media
http://www.cmpublishers.com


_______________________________________________
mon mailing list
mon <at> linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
Permalink | Reply | 0 comments |
headers
Nathan Gibbs | 26 Apr 2011 02:33

clamd.monitor v0.18 Released

ore stuff from the cave.  :-)

Updated Clam AV monitor.

http://www.cmpublishers.com/oss/#clamd.monitor

Code & Output Polishing
CCEE patch 3rd Party DB support.

Enjoy.

--

-- 
Sincerely,

Nathan Gibbs

Systems Administrator
Christ Media
http://www.cmpublishers.com


_______________________________________________
mon mailing list
mon <at> linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
Permalink | Reply | 0 comments |
headers
Nathan Gibbs | 26 Apr 2011 02:42

snmpdiskspace.monitor snmpnetdisk.monitor snmpdefroute.monitor Updates

And finally, the last of the stuff from the cave.

Same bug fix for all three of these.
Output Cleanup on error conditions.

http://www.cmpublishers.com/oss/#snmpdiskspace.monitor
http://www.cmpublishers.com/oss/#snmpnetdisk.monitor
http://www.cmpublishers.com/oss/#snmpdefroute.monitor

Enjoy.

--

-- 
Sincerely,

Nathan Gibbs

Systems Administrator
Christ Media
http://www.cmpublishers.com


_______________________________________________
mon mailing list
mon <at> linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
Permalink | Reply | 0 comments |
headers
Nathan Gibbs | 26 Apr 2011 05:05

dns-gtld.monitor v0.5

lol, I was wrong. :-)

Found this guy in the back of the cave.

http://www.cmpublishers.com/oss/#dns-gtld.monitor

Error threshold option to mask intermittent GTLD NS issues.
Output Code Cleanup.

Enjoy.

--

-- 
Sincerely,

Nathan Gibbs

Systems Administrator
Christ Media
http://www.cmpublishers.com


_______________________________________________
mon mailing list
mon <at> linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
Permalink | Reply | 0 comments |

Gmane