Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] no graphs for throughput test results, they don't appear to be stored

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] no graphs for throughput test results, they don't appear to be stored


Chronological Thread 
  • From: Dan Doyle <>
  • To: Rajan Patel <>
  • Cc: perfsonar-user <>
  • Subject: Re: [perfsonar-user] no graphs for throughput test results, they don't appear to be stored
  • Date: Thu, 16 Feb 2017 12:54:27 -0500
  • Ironport-phdr: 9a23:iJSjcBcgOCBqvqAPhEyKf7+6lGMj4u6mDksu8pMizoh2WeGdxcS+Zh7h7PlgxGXEQZ/co6odzbGH7ua4BSdZuczJmUtBWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnYdFRrlKAV6OPn+FJLMgMSrzeCy/IDYbxlViDanb75/KBW7oR/NusQZjoduN7o9xgXUqXZUZupawn9lK0iOlBjm/Mew+5Bj8yVUu/0/8sNLTLv3caclQ7FGFToqK2866tHluhnFVguP+2ATUn4KnRpSAgjK9w/1U5HsuSbnrOV92S2aPcrrTbAoXDmp8qlmRAP0hCoBKjU063/chNBug61HoRKhvx1/zJDSYIGJL/p1Y6fRccoHSWZdQspdUipMCZ6+YYQSFeoMJfpXoIbgqVUOrxSwCwqiBO3xxDFPnXL20rE20+E7HAHGwAAsAdQDu2nUotXvM6cSVPi4wqfSwjXFcvhY1zD96YjMch8/vPqBWq9/ftDVyUYyEAPEjlGQppL+MjOa0uQNtHOU4PBkVeKpjG4otxt9ojmyxss2lIbGm58Vx0nC+C5kw4g1PcW1RFN0bNOgCpdcqiCXOotsTs8/TWxltzw2x7wCtJKjYSQHx5AqywTCZ/GGb4SE+A/vWeSMLTtimX5od66zihCv+ka60OL8TNO70FNSoypFjNbMsncN2gTW6sedS/t9+lqt1S+J1w/N5OBIO080lbDdK54m3rE8jJsTsVnZEiDohUr2kbeadkQi+ue29+Tqeqjqq5CYOoNulw3zM6QjltaiDek2PQUCRWmW9OCk2L3m50L5QbFKjvMskqnetZDXPdkUqbS9AwBI1YYi6xK/ACm93dQXmXkHK0lKdwiDj4jvPFHBPOr0Dfaig1i2jjhk2u3GMqX7AprRNnjDjKvhfbFl5k5E1gUz195f54lTCrEHOv3zQFb9tMHDDhAnKQy52OLnCNRm1oMCQmKDHLWVMKLUsV+U+O0vOe+Ma5EJuDrjMfQq+ePhjWJq0WMaKJOg35IRIEixAvliaxGQf3fmhd4bHX8Dogc6ZOPvgVyGFzVUYiDhcbg742QXAYTuIYDSQo3l1LCI2Cu8D5lbTm9CDVqFFXHvfMOFRrEBZD/EcZwpqSANSbX0E9xp7hqprgKvjuM/duc=

Hi Rajan,

Hopefully I understood this correctly - you have a remote server that you want to run throughput tests to from a server you have locally. I think the confusion here is that because web100clt tests work, you expect that the other tests will too. The "throughput" tests defined in the webUI (and in fact which most people use) are done in version 3.5 using a tool called bwctl, which requires there to be a daemon configured on the receiving end to answer the request. You will need "bwctl-client" on your machine and "bwctl-server" on the other (and vice versa if you want bidirectional testing - most people just install both everywhere in pS).

`bwctl -c 4.34.58.11` from a couple of my test hosts appears to not be able to connect, whereas the web100clt does work. My guess is that this far end server either isn't running bwctld or if it is is not configured properly to allow access. If you have access, can you verify that?

Also, this may have been a typo in your original message - if you are in fact running 3.4 I would recommend running 3.5 as it is the latest stable release.

Dan Doyle
GlobalNOC Software Developer
1-812-856-3892

On Feb 16, 2017, at 12:04 PM, Rajan Patel <> wrote:

I have 1 IP at Hurricane Electric running on 4.34.58.11 which I can manually run a web100clt test against, to test my throughput.

I want perfSonar to test throughput on a schedule, and see those results in graph form.

I have a test scheduled for 1 time every 5 minutes, the test lasts 20 seconds. Throughput tests will be running 23% of the time.

Throughput and Loss do not seem to be recorded. I only see Graphs for Ping.

I have attached screenshots and logs.

About my setup:
Yesterday evening I installed perfSonar 3.4.2 32bit and turned on my desired services, and set the necessary scheduled tests. Auto updates were left to ON.
This morning I checked "Test Results" and saw Ping was being tracked. I rebooted perfSonar, after the updates happened thinking this was necessary for the throughput test to get logged correctly. No luck.

Any help would be appreciated!

Thanks,

Rajan
<Screen Shot 2017-02-16 at 11.55.00 AM.png><Screen Shot 2017-02-16 at 11.54.40 AM.png><Screen Shot 2017-02-16 at 11.54.21 AM.png><Screen Shot 2017-02-16 at 11.54.02 AM.png><service_watcher.log><regular_testing.log><psb_to_esmond.log><owamp_bwctl.log><mesh_configuration_agent.log><lsregistrationdaemon.log><lscachedaemon.log><ls_registration_daemon.log.1><ls_registration_daemon.log><ls_cache_daemon.log.1><ls_cache_daemon.log><configdaemon.log><config_daemon.log><clean_esmond_db.log>

Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.19.

Top of Page