[icinga-devel] Make sockets non-blocking

Hiren Patel hir3npatel at gmail.com
Thu May 6 10:21:35 CEST 2010


On Thu, 6 May 2010 09:45:52 +0200
Christoph Maser <cmr at financial.com> wrote:

> > > This is a patch against the CVS - if you prefer a git-am style patch,
> > > that's fine.  I tried to clone the git off of sourceforge this morning,
> > > and got an empty repo.  If there's a better place to clone from, let me
> > > know and I'll fix it up for that.
> >
> > So, it turned out my initial attempt to keep the patch small had some
> > limitations.  Working patch attached.
> >
> > To recap, the main problem is that I/O operations are blocking.  This is
> > less important to local file or unix sockets, but can block the main
> > nagios process when the I/O operations are tcp based.
> 
> 
> 
> This is an ancient discussion. The question is what do you do with the
> events/results when you loose connection to whatever "logging
> backend" (read local file or database). Just think disk is full and
> icinga cora can not wirte any logs/results. Do you just discard all the
> information or do you rather want to block/kill icinga core?
> You can queue up a certain amount of protocols at different layers but
> what do you do once all your buffers are exhausted?
> 

one suggestion I had, was to start sending alerts to the admin address configured in icinga.cfg.
since this would classify as a critical issue, and logging is no longer possible..
just my 2c.




More information about the icinga-devel mailing list