Closed GoogleCodeExporter closed 9 years ago
Hi Sharad
First thing, are you sure your nagios is listening on port 80?
Reason is, this is typically used by HTTP and if you have a HTTP server
listening on port 80, I would not be surprised to see a socket timeout
exception as nagios expects a initialisation vector to be sent back to it on
connection and HTTP server wont send that obviously
To test if you have an HTTP server running on that port, open a browser and
type URL
http://<ip you configured for nagios>
If you get a web page or something like that sent back, then you have a HTTP
server running on that port
Original comment by rajneeshpatel
on 25 Oct 2012 at 8:10
Thanks for the quick answer.If I use port 5667 also I am getting the same
error. I have a VMware server and the ip for which is 10.0.200.120 and the port
for the same is 5667. IP of the system where the vmware is installed is
10.0.200.221. So In the Porgram set up my NagiosSettingsBuilder has ip
10.0.200.120 and the MessagePayloadBuilder has ip 10.0.200.221.
Please let me know if this configuration is correct or not.
Original comment by sharad.m...@gmail.com
on 26 Oct 2012 at 4:08
Can you check this document
http://nagios.sourceforge.net/download/contrib/documentation/misc/NSCA_Setup.pdf
and go through steps to make sure you have a properly setup NSCA daemon on
10.0.200.120
Otherwise try following from command line
telnet 10.0.200.120 5667
You should see following with a load of random chars returned. If not, you
either dont have NSCA running or something else running on that port
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
9?#?????B?
R?)?w?i,!u??4=BX?D?T??Q
?\".UL????H?V?0?(??G??ۿ???KJ]?D?(W???;??????'m??I??G{?}^?]?}??Gk????|??I??
W
Original comment by rajneeshpatel
on 26 Oct 2012 at 10:45
Original comment by rajneeshpatel
on 6 Nov 2012 at 4:36
Original issue reported on code.google.com by
sharad.m...@gmail.com
on 25 Oct 2012 at 11:49