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: "Garnizov, Ivan (RRZE)" <>
  • To: John Simpkins <>, "" <>
  • Cc: "" <>
  • Subject: RE: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread
  • Date: Wed, 12 Oct 2016 08:18:25 +0000
  • Accept-language: en-GB, de-DE, en-US
  • Ironport-phdr: 9a23:DgMXJhHyUdeFjei551UWMZ1GYnF86YWxBRYc798ds5kLTJ75osywAkXT6L1XgUPTWs2DsrQf1LqQ7vurADFIyK3CmU5BWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnY6Uy/yPgttJ+nzBpWaz4Huj7jzqNXvZFBqgzq7KYhzKQ21rAPK/p0NgI56KacZ1x7IqXsOduhLkycgb1WMkhDnzsGh55N59SlM/fU7+IQIBaLlcqIjZbpJFzk8NW0posrxuk+QYxGI4y5WfWwMlBtaBBaBpDDkV5G58hHAhMc8kmHOPNP/S/Y7UC6k7rVsVjfmgTpBOzNvozKfsdB5kK8O+EHpnBd42YOBJdjNbPc=

Hi John,

 

In your email you are listing 2 errors both seem to relate to one and same task:

 

2016/10/11 16:17:10 (3243)” seems to be related to an invalid task specification “Unable to determine duration of test”. I have seen similar tasks running. Could you please share the command or the task, that triggered this error and of course the pscheduler version installed?

 

2016/10/11 16:17:10 (3243) WARN

It is stated in the log: “Proposal does not meet limits

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

 

Now I am not sure, if you are trying a new test (type), you had something custom there from 3.5.1 or it is still not implemented by pS Dev team.

 

Nevertheless it is strange, that the first issue did not interrupt the procedure, before reaching the second stage/error.

 

Regards,

Ivan

 

 

 

From: John Simpkins [mailto:]
Sent: Dienstag, 11. Oktober 2016 22:57
To: ; Garnizov, Ivan (RRZE)
Cc:
Subject: Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread

 

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

 

 

 

 

On Tue, Oct 11, 2016 at 3:00 PM Bill Owens <> wrote:

On Mon, Oct 10, 2016 at 09:46:17AM +0000, Garnizov, Ivan (RRZE) wrote:
>    Hi Bill,
>
>
>
>    Please issue “psc debug on” and review the messages in the syslog after a
>    while. Generally it is not a good idea to keep pscheduler in this mode as
>    it is quite “noisy”, but also quite helpful for debugging purposes. You
>    will be able to disable it with “psc debug off”.

Perhaps this is what's breaking?

Oct 11 14:13:31 bss532 journal: scheduler DEBUG    Got 75 rows
Oct 11 14:13:31 bss532 journal: scheduler DEBUG    TASK 7a6e676c-c382-42e7-bf6e-a7e4cb08428e, 0 runs, try 2016-10-11 14:13:30-04:00
Oct 11 14:13:31 bss532 journal: scheduler DEBUG    Trying to schedule 7a6e676c-c382-42e7-bf6e-a7e4cb08428e for 2016-10-11 14:13:41.170258-04:00 at https://bss532.nysernet.org/pscheduler/tasks/7a6e676c-c382-42e7-bf6e-a7e4cb08428e
Oct 11 14:13:31 bss532 journal: scheduler DEBUG    URL is https://bss532.nysernet.org/pscheduler/tasks/7a6e676c-c382-42e7-bf6e-a7e4cb08428e
Oct 11 14:13:31 bss532 journal: scheduler DEBUG    Posting https://bss532.nysernet.org/pscheduler/tasks/7a6e676c-c382-42e7-bf6e-a7e4cb08428e at 2016-10-11 14:13:41.170258-04:00
Oct 11 14:13:31 bss532 journal: pscheduler-api ERROR    Exception: ProgrammingError: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^#012#012Traceback (most recent call last):#012  File "./pschedulerapiserver/dbcursor.py", line 97, in dbcursor_query#012ProgrammingError: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^
Oct 11 14:13:31 bss532 journal: pscheduler-api ERROR    Exception: ProgrammingError: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^#012#012Traceback (most recent call last):#012  File "./pschedulerapiserver/dbcursor.py", line 97, in dbcursor_query#012ProgrammingError: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^
Oct 11 14:13:31 bss532 journal: pscheduler-api ERROR    Response 500: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^
Oct 11 14:13:31 bss532 journal: pscheduler-api ERROR    Response 500: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^
Oct 11 14:13:31 bss532 journal: safe_run/scheduler ERROR    Program threw an exception after 0:00:00.309999
Oct 11 14:13:31 bss532 journal: safe_run/scheduler ERROR    Program threw an exception after 0:00:00.309999
Oct 11 14:13:31 bss532 journal: safe_run/scheduler ERROR    Exception: URLException: https://bss532.nysernet.org/pscheduler/tasks/7a6e676c-c382-42e7-bf6e-a7e4cb08428e: 500: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^#012#012#012Traceback (most recent call last):#012  File "/usr/lib/python2.7/site-packages/pscheduler/saferun.py", line 41, in safe_run#012    function()#012  File "/usr/libexec/pscheduler/daemons/scheduler", line 430, in <lambda>#012    pscheduler.safe_run(lambda: main_program())#012  File "/usr/libexec/pscheduler/daemons/scheduler", line 394, in main_program#012    run_post(url, trynext, log)#012  File "/usr/libexec/pscheduler/daemons/scheduler", line 96, in run_post#012    status, task = pscheduler.url_get(task_url_text, params={'detail': 1})#012  File "/usr/lib/python2.7/site-packages/pscheduler/psurl.py", line 57, in url_get#012    + ": " + text)#012URLException: https://bss532.nysernet.org/pscheduler/tasks/7a6e676c-c382-42e7-bf6e-a7e4cb08428e: 500: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^
Oct 11 14:13:31 bss532 journal: safe_run/scheduler ERROR    Waiting 414.75 seconds before restarting
Oct 11 14:13:31 bss532 journal: safe_run/scheduler ERROR    Exception: URLException: https://bss532.nysernet.org/pscheduler/tasks/7a6e676c-c382-42e7-bf6e-a7e4cb08428e: 500: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^#012#012#012Traceback (most recent call last):#012  File "/usr/lib/python2.7/site-packages/pscheduler/saferun.py", line 41, in safe_run#012    function()#012  File "/usr/libexec/pscheduler/daemons/scheduler", line 430, in <lambda>#012    pscheduler.safe_run(lambda: main_program())#012  File "/usr/libexec/pscheduler/daemons/scheduler", line 394, in main_program#012    run_post(url, trynext, log)#012  File "/usr/libexec/pscheduler/daemons/scheduler", line 96, in run_post#012    status, task = pscheduler.url_get(task_url_text, params={'detail': 1})#012  File "/usr/lib/python2.7/site-packages/pscheduler/psurl.py", line 57, in url_get#012    + ": " + text)#012URLException: https://bss532.nysernet.org/pscheduler/tasks/7a6e676c-c382-42e7-bf6e-a7e4cb08428e: 500: column task.cli does not exist#012LINE 15:                     task.cli#012                             ^
Oct 11 14:13:31 bss532 journal: safe_run/scheduler ERROR    Waiting 414.75 seconds before restarting

I don't know how to interpret those errors, unfortunately.

Bill.




Archive powered by MHonArc 2.6.19.

Top of Page