Anyone had any luck getting this to run on a T-51xx or T52xx?
Kevin Kelly
Lifetouch Inc
11000 Viking Drive
Eden Prairie, MN 55344
952-826-4192w
612-247-6897c
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
Temperature.sh doesn't work on Solaris 10 since the prtdiag it use to report temperature doesn't work anymore. In Solaris 10, prtdiag command no longer support temperature reporting.
tj
On Fri, Jun 11, 2010 at 2:58 PM, Kevin Kelly <kkelly at lifetouch.com> wrote:
Anyone had any luck getting this to run on a T-51xx or T52xx?
Kevin Kelly
Lifetouch Inc
11000 Viking Drive
Eden Prairie, MN 55344
952-826-4192w
612-247-6897c
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
-- T.J. Yang
Hi
for some time I am having problems with out ping test of hobbit. It runs longer that the time intervall. Is it possible to speed up the test? I don't want to make the intervall longer. I am using the hobbitping. I tried doubling --max_pps from 50 to 100 with no effect.
Most of the time the DNS-lookup eats up 20 seconds, but sometimes it is near zero! Why that? Most of my monitored system have a testip tag, so should not do any DNS lookup at all. But some WLAN accesspoints which are configured for using DHCP does not have the testip tag.
In the manpage of hobbitping I read something about a runtime of 18 seconds for 1000 clients. Why it is so slow on my machine? It's a fast machine, Opteron with 1GBit network interface.
Here ist the output of bbtest:
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 : 288
succesful : 288
failed : 0
calls to dnsresolve : 290
TCP test statistics:
TCP tests total : 3
HTTP tests : 2
Simple TCP tests : 1
Connection attempts : 3
bytes written : 261
bytes read : 1467
Error output: WARNING: Runtime 68 longer than time limit (60)
TIME SPENT Event Starttime Duration bbtest-net startup 1276505088.377616 - Service definitions loaded 1276505088.380818 0.003202 Tests loaded 1276505088.417419 0.036601 DNS lookups completed 1276505108.462455 20.045036 <<<---- Test engine setup completed 1276505108.479249 0.016794 TCP tests completed 1276505108.482081 0.002832 PING test completed (814 hosts) 1276505156.193513 47.711432 <<<---- PING test results sent 1276505156.334798 0.141285 Test result collection completed 1276505156.334808 0.000010 LDAP test engine setup completed 1276505156.334809 0.000001 LDAP tests executed 1276505156.334819 0.000010 LDAP tests result collection completed 1276505156.334820 0.000001 NSLOOKUP tests executed 1276505156.339081 0.004261 Test results transmitted 1276505156.473376 0.134295 bbtest-net completed 1276505156.475145 0.001769 TIME TOTAL 68.097529
Thorsten Erdmann
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.
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. The "hobbitping" tools was a nice idea, but never was fully developed.
.....Bruce
Bruce White Senior Enterprise Systems Engineer | Phone: 630-671-5169 | Fax: 630-893-1648 | bewhite at fellowes.com | http://www.fellowes.com/ Disclaimer: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc.
From: thorsten.erdmann at daimler.com [mailto:thorsten.erdmann at daimler.com]
Sent: Monday, June 14, 2010 4:04 AM To: hobbit at hswn.dk Subject: [hobbit] ping test is too slow
Hi
for some time I am having problems with out ping test of hobbit. It runs longer that the time intervall. Is it possible to speed up the test? I don't want to make the intervall longer. I am using the hobbitping. I tried doubling --max_pps from 50 to 100 with no effect.
Most of the time the DNS-lookup eats up 20 seconds, but sometimes it is near zero! Why that? Most of my monitored system have a testip tag, so should not do any DNS lookup at all. But some WLAN accesspoints which are configured for using DHCP does not have the testip tag.
In the manpage of hobbitping I read something about a runtime of 18 seconds for 1000 clients. Why it is so slow on my machine? It's a fast machine, Opteron with 1GBit network interface.
Here ist the output of bbtest:
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 : 288
succesful : 288
failed : 0
calls to dnsresolve : 290
TCP test statistics:
TCP tests total : 3
HTTP tests : 2
Simple TCP tests : 1
Connection attempts : 3
bytes written : 261
bytes read : 1467
Error output: WARNING: Runtime 68 longer than time limit (60)
TIME SPENT Event Starttime Duration bbtest-net startup 1276505088.377616
Service definitions loaded 1276505088.380818 0.003202 Tests loaded 1276505088.417419 0.036601 DNS lookups completed 1276505108.462455 20.045036 <<<---- Test engine setup completed 1276505108.479249 0.016794 TCP tests completed 1276505108.482081 0.002832 PING test completed (814 hosts) 1276505156.193513 47.711432 <<<---- PING test results sent 1276505156.334798 0.141285 Test result collection completed 1276505156.334808 0.000010 LDAP test engine setup completed 1276505156.334809 0.000001 LDAP tests executed 1276505156.334819 0.000010 LDAP tests result collection completed 1276505156.334820 0.000001 NSLOOKUP tests executed 1276505156.339081 0.004261 Test results transmitted 1276505156.473376 0.134295 bbtest-net completed 1276505156.475145 0.001769 TIME TOTAL 68.097529
Thorsten Erdmann
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.
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.
Regards, Buchan
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
bgmilne at staff.telkomsa.net schrieb am 15.06.2010 12:32:39:
Regards, Buchan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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.
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
thorsten.erdmann at daimler.com 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
bgmilne at staff.telkomsa.net schrieb am 15.06.2010 12:32:39:
Regards, Buchan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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.
I am running RHEL5.2, but am not having anywhere near the latency you are.
The only apparent difference between our output is that I am on Xymon 4.3.0-0.beta2. I am also going over a gigabit network, but my DNS 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 wondering if that isn't where you need to concentrate your efforts?
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?
Jerald M. Sheets jr.
On Wed, Jun 23, 2010 at 9:09 AM, <thorsten.erdmann at daimler.com> 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
thorsten.erdmann at daimler.com 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,
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
you -
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
bgmilne at staff.telkomsa.net schrieb am 15.06.2010 12:32:39:
Regards, Buchan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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.
I'll agree with jerald on this one.
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.
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
On Wed, Jun 23, 2010 at 10:20 AM, Jerald Sheets <questy at gmail.com> wrote:
I am running RHEL5.2, but am not having anywhere near the latency you are. The only apparent difference between our output is that I am on Xymon 4.3.0-0.beta2. I am also going over a gigabit network, but my DNS 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 wondering if that isn't where you need to concentrate your efforts? 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?
Jerald M. Sheets jr.
On Wed, Jun 23, 2010 at 9:09 AM, <thorsten.erdmann at daimler.com> 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
thorsten.erdmann at daimler.com 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
bgmilne at staff.telkomsa.net schrieb am 15.06.2010 12:32:39:
Regards, Buchan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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.
Also, run a long-running ping test against an IP list and in another window against a domain name list.
I'm willing to bet you get latency on the domain list vs. the IP list.
Jerald M. Sheets jr.
On Thu, Jun 24, 2010 at 9:42 AM, Patrick Nixon <pnixon at gmail.com> wrote:
I'll agree with jerald on this one.
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.
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
On Wed, Jun 23, 2010 at 10:20 AM, Jerald Sheets <questy at gmail.com> wrote:
I am running RHEL5.2, but am not having anywhere near the latency you are. The only apparent difference between our output is that I am on Xymon 4.3.0-0.beta2. I am also going over a gigabit network, but my DNS 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 wondering if that isn't where you need to concentrate your efforts? 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?
Jerald M. Sheets jr.
On Wed, Jun 23, 2010 at 9:09 AM, <thorsten.erdmann at daimler.com> 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
thorsten.erdmann at daimler.com 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
bgmilne at staff.telkomsa.net schrieb am 15.06.2010 12:32:39:
Regards, Buchan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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.
questy at gmail.com 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 erdmann at daimler dot com, 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, <thorsten.erdmann at daimler.com> 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
thorsten.erdmann at daimler.com 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
bgmilne at staff.telkomsa.net schrieb am 15.06.2010 12:32:39:
Regards, Buchan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Do not thread hijack.
thorsten.erdmann at daimler.com wrote:
Hi
for some time I am having problems with out ping test of hobbit. It runs longer that the time intervall. Is it possible to speed up the test? I don't want to make the intervall longer. I am using the hobbitping. I tried doubling --max_pps from 50 to 100 with no effect.
Most of the time the DNS-lookup eats up 20 seconds, but sometimes it is near zero! Why that? Most of my monitored system have a testip tag, so should not do any DNS lookup at all. But some WLAN accesspoints which are configured for using DHCP does not have the testip tag.
In the manpage of hobbitping I read something about a runtime of 18 seconds for 1000 clients. Why it is so slow on my machine? It's a fast machine, Opteron with 1GBit network interface.
Here ist the output of bbtest:
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 : 288
succesful : 288
failed : 0
calls to dnsresolve : 290
TCP test statistics:
TCP tests total : 3
HTTP tests : 2
Simple TCP tests : 1
Connection attempts : 3
bytes written : 261
bytes read : 1467
Error output: WARNING: Runtime 68 longer than time limit (60)
TIME SPENT Event Starttime Duration bbtest-net startup 1276505088.377616 - Service definitions loaded 1276505088.380818
0.003202 Tests loaded 1276505088.417419
0.036601 DNS lookups completed 1276505108.462455
20.045036 <<<---- Test engine setup completed 1276505108.479249
0.016794 TCP tests completed 1276505108.482081
0.002832 PING test completed (814 hosts) 1276505156.193513
47.711432 <<<---- PING test results sent 1276505156.334798
0.141285 Test result collection completed 1276505156.334808
0.000010 LDAP test engine setup completed 1276505156.334809
0.000001 LDAP tests executed 1276505156.334819
0.000010 LDAP tests result collection completed 1276505156.334820
0.000001 NSLOOKUP tests executed 1276505156.339081
0.004261 Test results transmitted 1276505156.473376
0.134295 bbtest-net completed 1276505156.475145
0.001769 TIME TOTAL
68.097529Thorsten Erdmann
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.
- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkwWcscACgkQmb+gadEcsb6sAgCcCwPz+eE3m0Kuqq8fD61IOU/1 mtkAoKHhu4hTA+M9tW76EuavgDMavaLF =z1eB -----END PGP SIGNATURE-----
Bruce's answer was 100% pertinent to the question asked, and in my experience the proper answer.
Hobbitping is not everything it could be, and it's much better from the get-go to use fping. Whether you like the answer or not doesn't make it any less an answer.
Jerald M. Sheets jr.
On Mon, Jun 14, 2010 at 2:19 PM, Ryan Novosielski <novosirj at umdnj.edu>wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Do not thread hijack.
thorsten.erdmann at daimler.com wrote:
Hi
for some time I am having problems with out ping test of hobbit. It runs longer that the time intervall. Is it possible to speed up the test? I don't want to make the intervall longer. I am using the hobbitping. I tried doubling --max_pps from 50 to 100 with no effect.
Most of the time the DNS-lookup eats up 20 seconds, but sometimes it is near zero! Why that? Most of my monitored system have a testip tag, so should not do any DNS lookup at all. But some WLAN accesspoints which are configured for using DHCP does not have the testip tag.
In the manpage of hobbitping I read something about a runtime of 18 seconds for 1000 clients. Why it is so slow on my machine? It's a fast machine, Opteron with 1GBit network interface.
Here ist the output of bbtest:
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 : 288
succesful : 288
failed : 0
calls to dnsresolve : 290
TCP test statistics:
TCP tests total : 3
HTTP tests : 2
Simple TCP tests : 1
Connection attempts : 3
bytes written : 261
bytes read : 1467
Error output: WARNING: Runtime 68 longer than time limit (60)
TIME SPENT Event Starttime
bbtest-net startup 1276505088.377616
Duration -
Service definitions loaded 1276505088.380818 0.003202 Tests loaded 1276505088.417419 0.036601 DNS lookups completed 1276505108.462455 20.045036 <<<---- Test engine setup completed 1276505108.479249 0.016794 TCP tests completed 1276505108.482081 0.002832 PING test completed (814 hosts) 1276505156.193513 47.711432 <<<---- PING test results sent 1276505156.334798 0.141285 Test result collection completed 1276505156.334808 0.000010 LDAP test engine setup completed 1276505156.334809 0.000001 LDAP tests executed 1276505156.334819 0.000010 LDAP tests result collection completed 1276505156.334820 0.000001 NSLOOKUP tests executed 1276505156.339081 0.004261 Test results transmitted 1276505156.473376 0.134295 bbtest-net completed 1276505156.475145 0.001769 TIME TOTAL 68.097529
Thorsten Erdmann
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.
- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkwWcscACgkQmb+gadEcsb6sAgCcCwPz+eE3m0Kuqq8fD61IOU/1 mtkAoKHhu4hTA+M9tW76EuavgDMavaLF =z1eB -----END PGP SIGNATURE-----
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Not true, actually -- someone's rewritten it to use prtpicl on Solaris 10 -- I think you need v5.0. I was planning on writing a v6.0 that would support ipmitool for x64 Solaris, but I haven't done it yet. Take a look on Deadcat for v5.0.
=R
TJ Yang wrote:
Temperature.sh doesn't work on Solaris 10 since the prtdiag it use to report temperature doesn't work anymore. In Solaris 10, prtdiag command no longer support temperature reporting.
tj
On Fri, Jun 11, 2010 at 2:58 PM, Kevin Kelly <kkelly at lifetouch.com> wrote:
Anyone had any luck getting this to run on a T-51xx or T52xx?
Kevin Kelly
Lifetouch Inc
11000 Viking Drive
Eden Prairie, MN 55344
952-826-4192w
612-247-6897c
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkwWcwYACgkQmb+gadEcsb66CQCghAx+8U1UQXA8t6rVP8byArUB kMoAoKTHUN7Nvn+UnCVloV0ZoTUPJo/G =2d+j -----END PGP SIGNATURE-----
Ryan
My statement was based on V 4.0. Thanks for the correction. Indeed V5.0 has prtpicl support.
Cheers
tj
On Mon, Jun 14, 2010 at 1:20 PM, Ryan Novosielski <novosirj at umdnj.edu> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Not true, actually -- someone's rewritten it to use prtpicl on Solaris 10 -- I think you need v5.0. I was planning on writing a v6.0 that would support ipmitool for x64 Solaris, but I haven't done it yet. Take a look on Deadcat for v5.0.
=R
TJ Yang wrote:
Temperature.sh doesn't work on Solaris 10 since the prtdiag it use to report temperature doesn't work anymore. In Solaris 10, prtdiag command no longer support temperature reporting.
tj
On Fri, Jun 11, 2010 at 2:58 PM, Kevin Kelly <kkelly at lifetouch.com> wrote:
Anyone had any luck getting this to run on a T-51xx or T52xx?
Kevin Kelly
Lifetouch Inc
11000 Viking Drive
Eden Prairie, MN 55344
952-826-4192w
612-247-6897c
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkwWcwYACgkQmb+gadEcsb66CQCghAx+8U1UQXA8t6rVP8byArUB kMoAoKTHUN7Nvn+UnCVloV0ZoTUPJo/G =2d+j -----END PGP SIGNATURE-----
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- T.J. Yang
participants (8)
-
bewhite＠fellowes.com
-
bgmilne＠staff.telkomsa.net
-
kkelly＠lifetouch.com
-
novosirj＠umdnj.edu
-
pnixon＠gmail.com
-
questy＠gmail.com
-
thorsten.erdmann＠daimler.com
-
tjyang2001＠gmail.com