Hello,
thanks for your answers and suggestions. But I fear I have some problems understanding what you mean.
But first I think you need some more information. Most of our monitored systems where monitored via IP-address, not via hostnames by using the "testip" tag. Only 196 systems are tested using DNS-names.
user-96a6f34c5806@xymon.invalid schrieb am 24.06.2010 16:08:04:
Also, run a long-running ping test against an IP list and in another
window against a domain name list.
How can I ping a domain? That does not work, I never heared that I can ping a DNS domain name:
# ping de068.corpintra.net
ping: unknown host de068.corpintra.net
I can ping any host in that domain:
# ping s068t001.de068.corpintra.net
PING s068t001.de068.corpintra.net (53.42.8.236) 56(84) bytes of data.
64 bytes from s068t001.de068.corpintra.net (53.42.8.236): icmp_seq=0 ttl=127 time=0.266 ms
64 bytes from s068t001.de068.corpintra.net (53.42.8.236): icmp_seq=1 ttl=127 time=0.244 ms
64 bytes from s068t001.de068.corpintra.net (53.42.8.236): icmp_seq=2 ttl=127 time=0.268 ms
64 bytes from s068t001.de068.corpintra.net (53.42.8.236): icmp_seq=3 ttl=127 time=0.281 ms
64 bytes from s068t001.de068.corpintra.net (53.42.8.236): icmp_seq=4 ttl=127 time=0.261 ms
64 bytes from s068t001.de068.corpintra.net (53.42.8.236): icmp_seq=5 ttl=127 time=0.287 ms
64 bytes from s068t001.de068.corpintra.net (53.42.8.236): icmp_seq=6 ttl=127 time=0.233 ms
64 bytes from s068t001.de068.corpintra.net (53.42.8.236): icmp_seq=7 ttl=127 time=0.261 ms
It seems to make no difference if I ping the name with or without domain or the IP address.
If your DNS is not resolving properly, it can increase your ping
times as well, because ping does a DNS lookup as well when it
executes.
Ok, but then the turnaround time calculation of Hobbit would be wrong. The 20 seconds DNS resolve time is included in the ping test time, so it is double calculated!?
Check your DNS server/records, walk through your bb-hosts file to
determine if something is timing out/not resolving, and I suspect
you'll find the culprit
How can I check DNS server/records if I have no administrative access to the DNS server. The DNS server entries on my Hobbit server seems to be correct:
# cat /etc/resolv.conf
domainname de068.corpintra.net
search de068.corpintra.net
nameserver 53.42.4.22 # primary DNS server
nameserver 53.42.6.22 # secondary DNS server
But I think you are right with some DNS problems, because we have some timing issues sometimes with accessing server shares and something. But I don't know how to find out this. So if there is somebody out there who is willing to help me resolving this, you man conatact me personally on thorsten dot user-85e84abddd63@xymon.invalid, because this would be not a real Hobbit related problem and so does not fit exactliy on this list.
resolution time never crawls above the microseconds all that much.
Your OP
states that sometimes it takes up to 20 seconds to get resolution, and
I'm
I think this meant that all DNS queries together in one run of the network test is 20 seconds. At 196 hosts using DNS this would be 0.1 seconds per host.
As much as I hate to suggest such a thing because of other potential
bugs,
could you gain any benefit from having nscd running on the Xymon host
only?
What do you mean with Xymon host _only_.
On my Hobbit host there seems to be no nscd running at all:
# ps -ef |grep nscd
root 1279 25262 0 11:00 pts/1 00:00:00 grep nscd
Should it run, if the Hobbit host is not a DNS server?
Thorsten Erdmann
---
Jerald M. Sheets jr.
On Wed, Jun 23, 2010 at 9:09 AM, <user-9219fb9415b1@xymon.invalid> wrote:
Hello again
Is there really no other option to speed up the ping test, maybe by
using
multiple instance of fping/hobbitping. A collegue has the same issue
on a
Hobbitserver running on HPUX.
I am running Redhat EL.
Thorsten Erdmann
user-9219fb9415b1@xymon.invalid schrieb am 18.06.2010 14:06:43:
Hi
On Monday, 14 June 2010 19:12:33 White, Bruce wrote:
My experience with "hobbitping", is that it is just slower.
You are
better off downloading and installing "fping". Once you do
this,
you
will need to rebuild hobbit and select fping in the build
process.
Instead of rebuilding hobbit, you can change FPING in
hobbitserver.cfg
to
"/path/to/fping -Ae " or similar.
sorry for the delay. I just tried fping. But the turnaround time is
exactly the same, no benefit. Any other ideas?
bbtest-net version 4.2.0
SSL library : OpenSSL 0.9.7a Feb 19 2003
LDAP library: OpenLDAP 20213
Statistics:
Hosts total : 834
Hosts with no tests : 20
Total test count : 819
Status messages : 820
Alert status msgs : 0
Transmissions : 10
DNS statistics:
# hostnames resolved : 287
# succesful : 287
# failed : 0
# calls to dnsresolve : 289
TCP test statistics:
# TCP tests total : 3
# HTTP tests : 2
# Simple TCP tests : 1
# Connection attempts : 3
# bytes written : 261
# bytes read : 1467
TIME SPENT
Event Starttime
Duration
bbtest-net startup 1276862496.735994
• Service definitions loaded 1276862496.738353
0.002359
Tests loaded 1276862496.780920
0.042567
DNS lookups completed 1276862511.817886
15.036966
Test engine setup completed 1276862511.823173
0.005287
TCP tests completed 1276862511.825895
0.002722
PING test completed (814 hosts) 1276862553.583528
41.757633
PING test results sent 1276862553.718441
0.134913
Test result collection completed 1276862553.718452
0.000011
LDAP test engine setup completed 1276862553.718454
0.000002
LDAP tests executed 1276862553.718455
0.000001
LDAP tests result collection completed 1276862553.718456
0.000001
NSLOOKUP tests executed 1276862554.634700
0.916244
Test results transmitted 1276862554.700414
0.065714
bbtest-net completed 1276862554.702291
0.001877
TIME TOTAL
57.966297
Thorsten Erdmann
user-9b139aff4dec@xymon.invalid schrieb am 15.06.2010 12:32:39:
Regards,
Buchan
If you are not the intended addressee, please inform us immediately
that you have received this e-mail in error, and delete it. We
thank
you for your cooperation.
If you are not the intended addressee, please inform us immediately
that
you have received this e-mail in error, and delete it. We thank you for your
cooperation.
If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.