<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Nrpe on BAFM</title><link>https://christian.blog.pakiheim.de/tags/nrpe/</link><description>Recent content in Nrpe on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Thu, 19 Mar 2009 08:36:22 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/nrpe/index.xml" rel="self" type="application/rss+xml"/><item><title>Nagios: Watching Clustered environments (the other way)</title><link>https://christian.blog.pakiheim.de/posts/2009-03-19_nagios-watching-clustered-environments-the-other-way/</link><pubDate>Thu, 19 Mar 2009 08:36:22 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=1931</guid><description>&lt;p&gt;Well, recently I stepped up to watch our cluster environments &amp;hellip; Michael has a good howto on how to watch Windows Cluster environments in the &lt;a href="http://nsclient.com/nscp/wiki/TipsAndTrick"&gt;NSclient++ wiki&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Now, this has it&amp;rsquo;s own perks &amp;hellip; Which I stumbled upon when trying to write a Linux-HA OCF resource agent for the Nagios NRPE server. Combining that Linux-HA with SLES10 is a good thing generally, but using startproc in that resource agent is not such a good idea.&lt;/p&gt;
&lt;p&gt;Apparently Novell (or SuSE GmbH) thought it might be wise to include some additional logic into the wrapper. startproc, checkproc and killproc do check for the name of the executable. So if you try to start an additional process with the same name, you need to dig a bit deeper.&lt;/p&gt;
&lt;p&gt;For this to work, you need two additional things (quotations directly from &lt;strong&gt;man 8 startproc&lt;/strong&gt;):&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;-p&lt;/strong&gt; pid_file
(Former option &lt;strong&gt;-f&lt;/strong&gt; changed due to the LSB specification.) Use an alternate pid file instead of the default (/var/run/ &lt;strong&gt;&lt;!-- raw HTML omitted --&gt;&lt;/strong&gt;.pid). The pid read from this file is being matched against the pid of running processes that have an executable with specified path of the program. In order to avoid confusion with stale pid files, a not up-to-date pid will be ignored.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Now, then apparently this isn&amp;rsquo;t enough. startproc is still refusing to start a second process.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;-i&lt;/strong&gt; ignore_file
The pid found in this file is used as session id of the same binary program which should be ignored by &lt;strong&gt;startproc&lt;/strong&gt;.&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>Suspected NRPE weirdness</title><link>https://christian.blog.pakiheim.de/posts/2008-08-10_suspected-nrpe-weirdness/</link><pubDate>Sun, 10 Aug 2008 07:55:28 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=874</guid><description>&lt;p&gt;Well, I just noticed a really weird thing, when you have command line arguments enabled.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s a snippet from my &lt;em&gt;nrpe.cfg&lt;/em&gt;:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt" id="hl-0-1"&gt;&lt;a class="lnlinks" href="#hl-0-1"&gt;1&lt;/a&gt;
&lt;/span&gt;&lt;span class="lnt" id="hl-0-2"&gt;&lt;a class="lnlinks" href="#hl-0-2"&gt;2&lt;/a&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;dont_blame_nrpe=1
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;command[check_disk]=/usr/lib/nagios/plugins/check_disk -E -w $ARG1$ -c $ARG2$ -p $ARG3$
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;Now, if you&amp;rsquo;d check the free space for the root, it ain&amp;rsquo;t gonna show any inode percentage (that one isn&amp;rsquo;t what I&amp;rsquo;m talking about). But if you have to use bind mounts like I do (Tivoli needs a separate &amp;quot; &lt;em&gt;domain&lt;/em&gt;&amp;quot; -- that is a separate mount point for each domain), you might wanna check the free space on the &lt;em&gt;&lt;strong&gt;real&lt;/strong&gt;&lt;/em&gt; device, rather than the free space on the bind mount (which is gonna show you the free space of the parent file system - in my case the root fs).&lt;/p&gt;</description></item></channel></rss>