Hi scottwilkerson
Even i am the same problem in nagios-xi ,During installation...
Connecting to assets.nagios.com|72.14.181.71|:80... failed: Connection timed out.
And After some times
--2014-01-09 01:39:41-- (try: 2) http://assets.nagios.com/downloads/nagi ... install.py
Connecting to assets.nagios.com|72.14.181.71|:80... failed: Connection timed out.
Retrying.
--2014-01-09 01:40:04-- (try: 3) http://assets.nagios.com/downloads/nagi ... install.py
Connecting to assets.nagios.com|72.14.181.71|:80... failed: Connection timed out.
Retrying.
--2014-01-09 01:40:28-- (try: 4) http://assets.nagios.com/downloads/nagi ... install.py
Connecting to assets.nagios.com|72.14.181.71|:80... failed: Connection timed out.
Retrying.
--2014-01-09 01:40:53-- (try: 5) http://assets.nagios.com/downloads/nagi ... install.py
Connecting to assets.nagios.com|72.14.181.71|:80... failed: Connection timed out.
Retrying.
--2014-01-09 01:41:19-- (try: 6) http://assets.nagios.com/downloads/nagi ... install.py
Connecting to assets.nagios.com|72.14.181.71|:80... failed: Connection timed out.
Retrying.
--2014-01-09 01:41:46-- (try: 7) http://assets.nagios.com/downloads/nagi ... install.py
Connecting to assets.nagios.com|72.14.181.71|:80... failed: Connection timed out.
Retrying.
--2014-01-09 01:42:14-- (try: 8) http://assets.nagios.com/downloads/nagi ... install.py
Connecting to assets.nagios.com|72.14.181.71|:80... failed: Connection timed out.
Retrying.
Even i had done telnet
telnet 72.14.181.71 80
Trying 72.14.181.71...
NO response from telnet
Also my internet is working fine..
mssql queries need to be monitor
Re: mssql queries need to be monitor
Please do not post in topics that are over a year old. I have split your post into a new topic to keep things clean.
As for your issue, can you try the following from the nagios server command line?
Post the output here
As for your issue, can you try the following from the nagios server command line?
Code: Select all
ping www.google.com
nmap localhost
iptables -L
Former Nagios employee
Re: mssql queries need to be monitor
output
nmap localhost
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2014-01-09 02:07 IST
Interesting ports on Linux (127.0.0.1):
Not shown: 1671 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
111/tcp open rpcbind
443/tcp open https
631/tcp open ipp
862/tcp open unknown
3306/tcp open mysql
5432/tcp open postgres
Nmap finished: 1 IP address (1 host up) scanned in 0.130 seconds
# ping www.google.com
PING www.google.com (74.125.236.112) 56(84) bytes of data.
And
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
nmap localhost
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2014-01-09 02:07 IST
Interesting ports on Linux (127.0.0.1):
Not shown: 1671 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
111/tcp open rpcbind
443/tcp open https
631/tcp open ipp
862/tcp open unknown
3306/tcp open mysql
5432/tcp open postgres
Nmap finished: 1 IP address (1 host up) scanned in 0.130 seconds
# ping www.google.com
PING www.google.com (74.125.236.112) 56(84) bytes of data.
And
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Re: mssql queries need to be monitor
Did ping not do anything? And if you run
wget google.com
what is the output?
wget google.com
what is the output?
Former Nagios employee