perfsonar-user - Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: John Simpkins <>
- To: , "Garnizov, Ivan (RRZE)" <>
- Cc: "" <>
- Subject: Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread
- Date: Tue, 11 Oct 2016 20:56:42 +0000
- Ironport-phdr: 9a23:9EdtxBW492fb9osN3UroS+pUzmnV8LGtZVwlr6E/grcLSJyIuqrYZhaAt8tkgFKBZ4jH8fUM07OQ6P+wHzFbqs/c+Fk5M7VyFDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3HUNPK+/0Ao/fidisn6D3osWLIlYAuD3oZqx/Kg6eqxTKu9MQjJckLbw+jlODjXJSfeVEwn0sbXONlhC0pv2KzrMiuWwEuuwo8YhPWL/8frY/U5RWBSlgP21jt+PxshyWbwyP4DMnU2AOkRtOGECR9xD/RpTwmjb/t+F9niSWIJulHvgPRT2+4vIzG1fTgyAdOmt8qTmPhw==
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 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.
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, (continued)
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/04/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/04/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Andrew Lake, 10/04/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/05/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, John Simpkins, 10/06/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Michael Petry, 10/06/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, John Simpkins, 10/06/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/06/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/07/2016
- RE: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Garnizov, Ivan (RRZE), 10/10/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/11/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, John Simpkins, 10/11/2016
- RE: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Garnizov, Ivan (RRZE), 10/12/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Mark Feit, 10/18/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, John Simpkins, 10/19/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/07/2016
- RE: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Garnizov, Ivan (RRZE), 10/12/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/12/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Mark Feit, 10/12/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Mark Feit, 10/12/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/12/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, John Simpkins, 10/14/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, John Simpkins, 10/17/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/05/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Andrew Lake, 10/04/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/04/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC1 CentOS 7 testing thread, Bill Owens, 10/04/2016
Archive powered by MHonArc 2.6.19.