We use to have 2 physical server that the alerts worked fine on.
Now they are fresh new vms.
I have installed the nagios agent on them and getting the following , I have deleted the old alerts and re added the server as well but same.
On one server.
connect to address 10.1.1.50 and port 12489: Connection refused
The other server
CRITICAL - Socket timeout
New servers getting socket timeout or connection refused.
Re: New servesr getting socket timeout or connection refused
Forgive me if this is a bit basic, but have you checked whether the IP address and port matches between the XI server and host machine?
Which agent are you installing? If you link the document or web page, then I can follow along and try to determine what should be changed.
The linked document below is a good place to get started monitoring something new in Nagios XI.
https://assets.nagios.com/downloads/nag ... os-XI.pdf
Which agent are you installing? If you link the document or web page, then I can follow along and try to determine what should be changed.
The linked document below is a good place to get started monitoring something new in Nagios XI.
https://assets.nagios.com/downloads/nag ... os-XI.pdf
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: New servers getting socket timeout or connection refused
We use NSClient++ as the agent. The version is 0.4.4 (64bit)
I specified the host and password on the client side and the password on the nagios side.
I specified the host and password on the client side and the password on the nagios side.
Re: New servers getting socket timeout or connection refused
Hi,
It's likely a firewall issue. Is the NSClient service running and did you restart the service after specifying the host and password? If you cannot establish communication, please post the nsclient.ini file to the thread.
You can test if a port is accessible by using the nmap command from the Nagios XI server
Thanks.
Reference
Configuring The Windows Agent: NSClient++
It's likely a firewall issue. Is the NSClient service running and did you restart the service after specifying the host and password? If you cannot establish communication, please post the nsclient.ini file to the thread.
You can test if a port is accessible by using the nmap command from the Nagios XI server
Code: Select all
nmap <windows machine address> -p T:12489
Reference
Configuring The Windows Agent: NSClient++
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!