Search found 16 matches
- Mon Jun 23, 2025 12:29 am
- Forum: Open Source Nagios Projects
- Topic: Nagios check_tcp not showing correct status on UI
- Replies: 14
- Views: 56521
Re: Nagios check_tcp not showing correct status on UI
Hey, I resolved it myself. Let's close this out.
- Mon Jun 23, 2025 12:09 am
- Forum: Open Source Nagios Projects
- Topic: Nagios check_tcp not showing correct status on UI
- Replies: 14
- Views: 56521
Re: Nagios check_tcp not showing correct status on UI
No, it gives a syntax error. See, like below. I am a bit confused on how I can monitor these ports using a single command ? Any documentation got this ? Jun 23 10:39:32 nagios-core nagios[2654]: Nagios Core 4.4.6 Jun 23 10:39:32 nagios-core nagios[2654]: Copyright (c) 2009-present Nagios Core Develo...
- Tue Jun 17, 2025 10:39 pm
- Forum: Open Source Nagios Projects
- Topic: Nagios check_tcp not showing correct status on UI
- Replies: 14
- Views: 56521
Re: Nagios check_tcp not showing correct status on UI
If I do not use that as a part of the syntax, it will throw syntax error.
- Sun Jun 15, 2025 11:56 pm
- Forum: Open Source Nagios Projects
- Topic: Nagios check_tcp not showing correct status on UI
- Replies: 14
- Views: 56521
Re: Nagios check_tcp not showing correct status on UI
The single quotes are basically taking arguments with "-a" flag. So not sure it is an incorrect syntax ?
Anyways I tried that as well, UI shows like below,
Anyways I tried that as well, UI shows like below,
Usage:
- Sun Jun 15, 2025 11:22 pm
- Forum: Open Source Nagios Projects
- Topic: Nagios check_tcp not showing correct status on UI
- Replies: 14
- Views: 56521
Re: Nagios check_tcp not showing correct status on UI
It is not resolved. I am still getting below message on UI. Please help. I just showed you in my earlier reply that from command line this works correctly but on UI it shows error.
(No output on stdout) stderr: Could not resolve hostname 15.207.248.93 -p 9200: Name or service not known
(No output on stdout) stderr: Could not resolve hostname 15.207.248.93 -p 9200: Name or service not known
- Sun Jun 15, 2025 10:56 pm
- Forum: Open Source Nagios Projects
- Topic: Nagios check_tcp not showing correct status on UI
- Replies: 14
- Views: 56521
Re: Nagios check_tcp not showing correct status on UI
Please understand that EC2 instance was turned off and once it is on it will be assigned with new IP. Hence 15.207.248.93 is the new IP address. This IP address is replaced everywhere, including nrpe.cfg, and .cfg file under server directory. [root@nagios-core ~]# /usr/local/nagios/libexec/check_tcp...
- Sun Jun 15, 2025 10:11 pm
- Forum: Open Source Nagios Projects
- Topic: Nagios check_tcp not showing correct status on UI
- Replies: 14
- Views: 56521
Re: Nagios check_tcp not showing correct status on UI
Please check the below, Service defination defined on nagios server, Path - /usr/local/nagios/etc/servers/ELK-stack.cfg define host { use linux-server host_name ELK-Stack alias My client server address 15.207.248.93 max_check_attempts 20 check_period 24x7 notification_interval 1 notification_period ...
- Sun Jun 15, 2025 9:14 am
- Forum: Open Source Nagios Projects
- Topic: Nagios check_tcp not showing correct status on UI
- Replies: 14
- Views: 56521
Nagios check_tcp not showing correct status on UI
Hi All, I am working to setup nagios monitoring on remote host for TCP ports 5044, 9200 & 5601. All these ports have containers running for elasticsearch, logstash & kibana respectively. The problem here is that whenever I try to setup monitoring on the /usr/local/nagios/etc/servers hosts.cf...
- Mon Apr 29, 2024 12:57 am
- Forum: Open Source Nagios Projects
- Topic: connect to address 127.0.0.1 and port 0: Connection refused
- Replies: 3
- Views: 2915
Re: connect to address 127.0.0.1 and port 0: Connection refused
Thanks for your response, but it shows status as "Unknown" after modifying the nrpe.cfg on client. Complete alert as below, looks like that is incorrect syntax. Current Status: UNKNOWN (for 0d 0h 2m 22s) Status Information: Usage: check_tcp -H host -p port [-w <warning time>] [-c <critical...
- Sat Apr 27, 2024 12:35 am
- Forum: Open Source Nagios Projects
- Topic: connect to address 127.0.0.1 and port 0: Connection refused
- Replies: 3
- Views: 2915
connect to address 127.0.0.1 and port 0: Connection refused
Hi All, Greetings of the day ! I have one RHEL EC2 instance running nginx listening to port 80. I have defined commands and service check in host config file to monitor this host. After running below command manually, I could see it's working perfectly. ./check_tcp -H 13.233.117.236 -p 80 -w 10 -c 2...