Databases
StackOverflow2013
Postsdbo
POIcinga check_jboss "NRPE: unable to read output"
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIcinga check_jboss "NRPE: unable to read output"
    text
    copied!<p>I'm using <code>Icinga</code> to monitor some servers and services. Most of them run fine. But now I like to monitor a JBoss-AS on one server via <code>NRPE</code>. Therefore I'm using the <code>check_jboss</code>-Plugin from MonitoringExchange. Although each time I try running a test-command from my Icinga-Server via NRPE I'm getting a <code>NRPE: unable to read output</code> error. When I try executing the command directly on the monitored server it runs fine. It's strange that the execution on the monitored server takes around 5 seconds to return a acceptable result but the NRPE-Exceution returns immediately the error. Trying to set up the NRPE-timeout didn't solve the problem. I also checked the permissions of the check_jboss-plugin and set them to "777" so that there should be no error. I don't think that there's a common issue with NRPE, because there are also some other checks (e.g. check_load, check_disk, ...) via NRPE and they are all running fine. The permissions of these plugins are analog to my check_jboss-Plugin.</p> <p>Following one sample exceuction on the monitored server which runs fine:</p> <pre><code>/usr/lib64/nagios/plugins/check_jboss.pl -T ServerInfo -J jboss.system -a MaxMemory -w 3000: -c 2000: -f JBOSS OK - MaxMemory is 4049076224 | MaxMemory=4049076224 </code></pre> <p>Here are two command-executions via NRPE from my Icinga-Server. Both commands are correctly </p> <pre><code>./check_nrpe -H xxx.xxx.xxx.xxx -c check_hda1 DISK OK - free space: / 47452 MB (76% inode=97%);| /=14505MB;52218;58745;0;65273 ./check_nrpe -H xxx.xxx.xxx.xxx -c jboss_MaxMemory NRPE: Unable to read output </code></pre> <p>Does anyone have a hint for me? If further config-information needed please ask :)</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload