Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread


Chronological Thread 
  • From: Mark Feit <>
  • To: John Simpkins <>, "" <>, "Garnizov, Ivan (RRZE)" <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread
  • Date: Tue, 18 Oct 2016 17:55:24 +0000
  • Accept-language: en-US
  • Authentication-results: umich.edu; dkim=none (message not signed) header.d=none;umich.edu; dmarc=none action=none header.from=internet2.edu;
  • Ironport-phdr: 9a23:O3HUnR82sVkLF/9uRHKM819IXTAuvvDOBiVQ1KB92+kcTK2v8tzYMVDF4r011RmSAtWdtqkP0reempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBX660e/5j8KGxj5KRE9ZqGsQtaT3IyL0LWQ/J3VKz5JgSK+YLVpZEGtrADJtcg+nI5jIaZ3xxfU9D8AMeNJyGVzDVSChBvm4Mqsupl5/G4Y7/U++shbeaPrZKkiS7FESjM8PDZxrIfEvAPFTBmI+D9Uc3sflFIIOTL3wVCwFsPwrCL88OV0wi+bL8roZb49RHKu4vE4ZgXvjXIiPiQ6uE/ai9A42KdVrRO9jx1534POZoyJbrxzcr6LLoBSfnZIQssED38JOYi7dYZaSrNZZes=
  • Spamdiagnosticoutput: 1:0

(Sorry for the late reply; the draft got buried.)

 

John Simpkins writes:

 

I'm seeing similar, but not quite the same, results.

 

2016/10/11 16:17:10 (3243) WARN> perfsonar_meshconfig_agent:381 main:: - Problem adding test, continuing with rest of config: 500 INTERNAL SERVER ERROR: Unable to determine duration of test: Traceback (most recent call last):

  File "/usr/libexec/pscheduler/commands/../classes/tool/bwctliperf3/duration", line 26, in <module>

    duration += int(json['omit'])

ValueError: invalid literal for int() with base 10: 'PT10S'

...

2016/10/11 16:17:10 (3243) WARN> perfsonar_meshconfig_agent:381 main:: - Problem adding test, continuing with rest of config: 403 FORBIDDEN: Task forbidden by limits:

Identified as everybody

Classified as everybody, default

Application: Defaults

    Group 1: Limit 'innocuous-tests' failed: Test type not in list

    Group 1: Limit 'rtt-default' failed: Test is not 'rtt'

    Group 1: Limit 'throughput-default' failed: Test is not 'throughput'

    Group 1: Want any, 0/3 passed, 3/3 failed: FAIL

    Group 1: Failed; stopping here.

    Application FAILS

Proposal does not meet limits

 

 

The limit failure is the result of a mistake on my part where a couple of the innocuous tests didn’t get put into the list used in the limit configuration we shipped with RC1.  The file we ship in RC2 will be fixed.

 

As a stopgap, you can edit /etc/pscheduler/limits.conf, locate the “innocuous-tests” section, add “rtt” to the list list of test types and restart httpd.

 

--Mark

 




Archive powered by MHonArc 2.6.19.

Top of Page