You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I am not able to report the issue on 5.2, I just realized I have not upgraded it from the 5.1.4...
the issue I report now is on 5.1.4, since the upgrade from to Snapshot 5.2 on Ubuntu22 completed successfully, but pSconfig gives me Traceback errors.
I'll repeat the install of 5.1.4 and then upgrade to 5.2 later so to document the upgrade, but here are my findings from 5.1.4
2024-12-18 14:50:02 WARNING pid=528537 prog=_run_end line=215 guid=6aabbd9d-6266-40da-953b-a1b9eaa08396 msg=Problem adding test latency(t2-psde v.rrze.uni-erlangen.de->psbrix.rrze.uni-erlangen.de), continuing with rest of config: BAD REQUEST. Status Code: 400Invalid task specification: At //schema: 1 is not one of [2]
2024-12-18 14:50:02 WARNING pid=528537 prog=_run_end line=215 guid=6aabbd9d-6266-40da-953b-a1b9eaa08396 msg=Problem adding test latency(t2-psde v.rrze.uni-erlangen.de->psbrix.rrze.uni-erlangen.de), continuing with rest of config: BAD REQUEST. Status Code: 400Invalid task specification: At //schema: 1 is not one of [2]
2024-12-18 14:50:02 INFO pid=528537 prog= line=112 guid=6aabbd9d-6266-40da-953b-a1b9eaa08396 msg=Agent completed running
2024-12-18 14:50:02 INFO pid=528537 prog= line=127 guid=6aabbd9d-6266-40da-953b-a1b9eaa08396 msg=Time until next record refresh is 3592
root@ps52-snap:~# psconfig validate /shared/tst--pscfg-ps.json
Loading config ...... OK
Validating JSON schema ...... OK
Verifying object references ...... OK
pScheduler Validation (Quick): 25%|в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–Ћ pScheduler Validation (Quick): 50%|в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–pScheduler Validation (Quick): 75%|в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–Љ [00:03<pScheduler Validation (Quick): 100%|в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€вpScheduler Validation (Quick) ...... OK
pSConfig JSON is valid
The text was updated successfully, but these errors were encountered:
So I am not able to report the issue on 5.2, I just realized I have not upgraded it from the 5.1.4...
the issue I report now is on 5.1.4, since the upgrade from to Snapshot 5.2 on Ubuntu22 completed successfully, but pSconfig gives me Traceback errors.
I'll repeat the install of 5.1.4 and then upgrade to 5.2 later so to document the upgrade, but here are my findings from 5.1.4
Error:
2024-12-18 14:50:02 WARNING pid=528537 prog=_run_end line=215 guid=6aabbd9d-6266-40da-953b-a1b9eaa08396 msg=Problem adding test latency(t2-psde v.rrze.uni-erlangen.de->psbrix.rrze.uni-erlangen.de), continuing with rest of config: BAD REQUEST. Status Code: 400Invalid task specification: At //schema: 1 is not one of [2]
2024-12-18 14:50:02 WARNING pid=528537 prog=_run_end line=215 guid=6aabbd9d-6266-40da-953b-a1b9eaa08396 msg=Problem adding test latency(t2-psde v.rrze.uni-erlangen.de->psbrix.rrze.uni-erlangen.de), continuing with rest of config: BAD REQUEST. Status Code: 400Invalid task specification: At //schema: 1 is not one of [2]
2024-12-18 14:50:02 INFO pid=528537 prog= line=112 guid=6aabbd9d-6266-40da-953b-a1b9eaa08396 msg=Agent completed running
2024-12-18 14:50:02 INFO pid=528537 prog= line=127 guid=6aabbd9d-6266-40da-953b-a1b9eaa08396 msg=Time until next record refresh is 3592
root@ps52-snap:~# psconfig validate /shared/tst--pscfg-ps.json
Loading config ...... OK
Validating JSON schema ...... OK
Verifying object references ...... OK
pScheduler Validation (Quick): 25%|в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–Ћ pScheduler Validation (Quick): 50%|в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–pScheduler Validation (Quick): 75%|в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–Љ [00:03<pScheduler Validation (Quick): 100%|в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€в–€вpScheduler Validation (Quick) ...... OK
pSConfig JSON is valid
The text was updated successfully, but these errors were encountered: