Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Test Results empty despite tests having run - new install

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Test Results empty despite tests having run - new install


Chronological Thread 
    < Chronological >      < Thread >
  • From: "Dockendorf, Trey" <>
  • To: "" <>
  • Subject: [perfsonar-user] Test Results empty despite tests having run - new install
  • Date: Tue, 13 Aug 2019 16:03:25 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=osc.edu; dmarc=pass action=none header.from=osc.edu; dkim=pass header.d=osc.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3v2JMH/9zkl4hhnqMeDgwC1C/O+EJ94c7q0XYKDmSjU=; b=Y79IRAJRj7TSevfBXZa6OaU1vUk01n7uoalL3WnUAnW/Hmxi4U0vhi3yXy6+97SFeyUa8MrJf2mS6LWmj/aT1NhXzrZA33VHVkPR7+LM/zJcJsZTvFrC4ujSbFe9jHXrowj1YHre19ogaWNCdi56pQ+aFSYMdZx0k/QPipif4574cXGx5aazAx6Xtlov7wb0SnX/bbdl8y82IiPPA5cLK9Qv0iU0p3p0QdRBrLxUa1MFfaGZ0yIcxYnjCHzxg8itW8rpXbAt0SqtR+AzyhHCStxhz5uzHuwYEdRdT1ZIRYiL8fv+oua2iPeYFwaubcbN4dJB01om9zzdlmDOcnfW8w==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=j8zdjgZw4aKUHReqFYJtJpxFUvGXc0o8I2iSqvRK2XaRP63kPY+Ss5IwmYVzmV6UJKMkTs/qGnZ8bS/MAnI48D1xPZxfnpUUKZ4QgaMNDgmqbmyPafuAYbM/V/OBOFFTwC9LCeaUmUTYRAGq0MFAAbMJkJhwq2qbC/e2Y724L9LnLRKblqx/ddDgJi1lce4fynNJbzmzpp9LjmdaY33M5Lz3HLG2Pzxx4S1kPaj6UtG703tK8EZqIqo+LalCyGuFmZEuhpI2UwAACMGsLwlAgYNa7g+9EMQPQEKsusXTVFqnpWYbcl3RLv7zpex4tsjcm3NlypPGnhk0VjfBcZmklg==

I recently installed perfSONAR 4.1.6 here: https://psonar-bw.hpc.osc.edu/toolkit/.  I have setup several tests for both bandwidth and latency and several have run according to logs and esmond but the Test Results still shows no results. How do I go about debugging the lack of test results being shown?

 

The only issue I’ve seen in logs is the IP used for communicating to the system is the secondary interface that is 1GbE and intended for latency tests. This host has 2 interfaces on 2 different subnets, one for latency and one for bandwidth and the 10GbE bandwidth interface (em6) is primary and latency interface (em2) is secondary but latency interface is what’s used in pscheduler.log.

 

Thanks,

- Trey


Archive powered by MHonArc 2.6.19.

Top of Page