I'm using the following service to monitor our postgres db from nagios:
define service{
use test-service ; Name of servi$
host_name DEMOCGN002
service_description Postgres State
check_command check_nrpe!check_pgsql!192.168.1.135!test!test!test
notifications_enabled
Sorry for the long message, I wanted to be as clear as possible. I have to add hundreds of new servers to hundreds of configuration files in Nagios.
Can anyone let me know how I would reduce time between Last Check Time and Next Scheduled Check on a particular service. I have a very critical task to monitor and the time between checks is currently 5 minutes, which is too long for this service. Can I reduce that time? I need this to be 1 minute or even 30 seconds.
I want Nagios to check this service every 30 seconds.
We are using Nagios to check duplicate processes.
define service
{
use local-service
host_name xxx
service_description xxx Duplicate Processes
check_interval 1
max_check_attempts 1
contact_groups admins
event_handler restart-dependent-processes
I've got a web app that's split into two components. A WCF service hosted on port 4444 and a regular set of web services hosted on port 80 via IIS.
I've got my nodes set up in haproxy, but I now need to extend my configuration to ensure that my health checking for port 80 removes a node if port 4444 is down.
I have a problem with Nagios, and in particular with the check_tcp plugin, used to check the Citrix connection on a Windows server.
Nagios is in version 3.3.1 and nagios plugins are in version 1.4.15 (which seems to be the last ones).
When the connection is OK, the service's status is OK with Status Information saying : "TCP OK".
But when the Citrix service is not responding, the service's status
My client has a Linux machine that has a few software installed.
One of them uses port number 80 but is not a web service.
Now, I have to listen to ordinary people typing the url in the browser and show them
web pages.
1. We have an address m.info.mditac.or.kr.
2. People would use this address to access the web service.
3. AFAK, http uses port 80.
4.
I'm trying to use an Apache proxy as a front-end for a service running on a different server in my infrastructure. Let's call them proxy.example.com and service.example.com.
Proxy.example.com is listening on port 80, but service.example.com is listening on port 8888.
A friend of mine gives me a (user) ssh access on an ec2-instance (ubuntu) that he's got.
So, for reason that now I don't know, in the future I will have need of an open tcp port over the firewall to make listening some sort of service (like http or other).
I don't want to stress him every time that I need a tcp open port in the firewall but, meanwhile, I don't want to leave open (and vulnerably un
Email this page
