I like a project monitoring ADABAS Data Base.
Someone has already done some monitoring on such databases.
Thank You
Search found 9 matches
- Thu Jan 15, 2015 3:20 pm
- Forum: Open Source Nagios Projects
- Topic: Plugin's for DB ADABAS
- Replies: 2
- Views: 1216
- Wed Nov 12, 2014 9:31 am
- Forum: Open Source Nagios Projects
- Topic: CHECK_NRPE: Socket timeout after 20 seconds.
- Replies: 67
- Views: 27289
Re: CHECK_NRPE: Socket timeout after 20 seconds.
Post
1. New NRPE.cfg config
2. Execute command prompt
3. NRPE Log
please!!
1. New NRPE.cfg config
2. Execute command prompt
3. NRPE Log
please!!
- Tue Nov 11, 2014 9:41 am
- Forum: Open Source Nagios Projects
- Topic: CHECK_NRPE: Socket timeout after 20 seconds.
- Replies: 67
- Views: 27289
Re: CHECK_NRPE: Socket timeout after 20 seconds.
hi kakaluru And should not affect the replication process database has no relationship with the nrpe process. An important detail is that the NRPE is and always should be this rule is for monitoring not for automation of tasks . It's a fine line that often thinks as monitoring goes to validate proce...
- Fri Nov 07, 2014 10:08 am
- Forum: Open Source Nagios Projects
- Topic: CHECK_NRPE: Socket timeout after 20 seconds.
- Replies: 67
- Views: 27289
Re: CHECK_NRPE: Socket timeout after 20 seconds.
Hello Kakaluru The first thing you need is to change the following line in the hosts file nrpe.cfg BUGZILLABCK before allowed_hosts = 127.0.0.1 After allowed_hosts = 127.0.0.1, IP Nagios Server before dont_blame_nrpe = 0 After dont_blame_nrpe = 1 At the end of the file you have all commands with arg...
- Thu Nov 06, 2014 9:29 am
- Forum: Open Source Nagios Projects
- Topic: CHECK_NRPE: Socket timeout after 20 seconds.
- Replies: 67
- Views: 27289
Re: CHECK_NRPE: Socket timeout after 20 seconds.
Hello Kakaluru IP is the same BUGZILLABCK 10.174.16.11? The IP 192.168.30.38 is the Nagios Server? You can try the following and post the results /usr/local/nagios/libexec/check_nrpe -H 10.174.16.11 -n -c check_load That line is you should try from the Nagios server not from the same BUGZILLABCK You...
- Wed Nov 05, 2014 11:59 am
- Forum: Open Source Nagios Projects
- Topic: Critical: Return code of 139 is out of bounds
- Replies: 10
- Views: 5848
Re: Critical: Return code of 139 is out of bounds
Hi Ravil
I see that the plugin has root permissions can try running as nagios from the console to rule than a permissions issue.
further validate a recommendation that the folder where the plugins also have the same permissions and run nagios nagios plugins with full path.
JN
I see that the plugin has root permissions can try running as nagios from the console to rule than a permissions issue.
further validate a recommendation that the folder where the plugins also have the same permissions and run nagios nagios plugins with full path.
JN
- Wed Nov 05, 2014 11:55 am
- Forum: Open Source Nagios Projects
- Topic: CHECK_NRPE: Socket timeout after 20 seconds.
- Replies: 67
- Views: 27289
Re: CHECK_NRPE: Socket timeout after 20 seconds.
One option you could evaluate not use xinetd nrpe but as a service / process thus can not depend on another process to verify that the NRPE is functioning properly on the remote computer. recommend additional long as you include a host with an agent to perform monitoring agent and the port through w...
- Wed Nov 05, 2014 11:46 am
- Forum: Open Source Nagios Projects
- Topic: Error Compiling NRPE
- Replies: 10
- Views: 7600
Re: Error Compiling NRPE
You can try to modify the configuration file in the following lines nrpe.cfg # COMMAND ARGUMENT PROCESSING # This option Determines whether or not the NRPE daemon will allow clients # Specify arguments to commands to That are Executed. This option only works # If the daemon configured WAS With The -...
- Wed Nov 05, 2014 11:35 am
- Forum: Open Source Nagios Projects
- Topic: CHECK_NRPE: Socket timeout after 20 seconds.
- Replies: 67
- Views: 27289
Re: CHECK_NRPE: Socket timeout after 20 seconds.
Hi Kakaluru Before testing the execution from the Nagios server you can try running the command locally on the remote machine something like / check_nrpe -c -H 127.0.0.1 check_load With this you're eliminating potential points of failure. If it works you can validate as the NRPE is configured with S...