DNS error and Service bbd not OK: Service unavailable (connect timeout)
list Jayanta Kundu
Hi Guys, I configured both XYMON client and server into our client side, it working fine. I want to monitor it into our offshore office(in different place). In our offshore office I configured XYMON server. I connected client side XYMON server to our offshore office XYMON server. But I am unable to get data from client side(XYMON server) to our offshore office XYMON server. Following errors are shown: 1. If I check bbd(Client side Collector Server) error is: Service bbd on abixymon.mtncameroon.net is not OK : Service unavailable (connect timeout) Seconds: 0.00 2. If I check http(Client side Collector Server) error is: http://abixymon.mtncameroon.net/ - DNS error Seconds: 0.00 Kindly provide me the solution for the same. With Regards, Jayanta.
list Henrik Størner
▸
In <user-ae1c42ecffd6@xymon.invalid> Jayanta Kundu <user-d0758a3e63c3@xymon.invalid> writes:
2. If I check http(Client side Collector Server) error is: http://abixymon.mtncameroon.net/ - DNS error
Your Xymon server running the http test cannot do a DNS-lookup for abixymon.mtncameroon.net . Either fix the DNS issue, or specify the IP-address to use for the http test with the http://abixymon.mtncameroon.net=10.0.0.1/ syntax to override the DNS lookup. Regards, Henrik
list J. Epperson
▸
On Thu, December 9, 2010 06:12, Henrik Størner wrote:
In <user-ae1c42ecffd6@xymon.invalid>
Jayanta
Kundu <user-d0758a3e63c3@xymon.invalid> writes:2. If I check http(Client side Collector Server) error is: http://abixymon.mtncameroon.net/ - DNS errorYour Xymon server running the http test cannot do a DNS-lookup for abixymon.mtncameroon.net . Either fix the DNS issue, or specify the
IP-address to use for the http test with the
http://abixymon.mtncameroon.net=10.0.0.1/ syntax to override the DNS lookup.
Eureka! Didn't know about the "=ip" syntax, so this post sent me to the manpage. This is perfect for our situation of Internet-facing virtual hosts with private addresses in the internal split DNS. Up to now, if a NAT failure occurred for one of these, we didn't necessarily know, because we were testing via the RFC1918 address. Couldn't use straight-IP URLs because of virtual host settings and rewrite rules.