perfSONAR User Q&A and Other Discussion

["Hitch, A Ryan (53629) CIV USN NIWC PACIFIC CA (USA)" <>]

CLASSIFICATION: UNCLASSIFIED
I have a test grid with 10 probes that has been running latencybg and 
throughput tests for a few weeks and I see an increasing number of 
non-starter tasks. These seem to be resulting from the following error in 
pscheduler.log, for example:
Sep 11 16:44:49 s00-perf journal: runner ERROR   2208189: Failed to post run 
for result: duplicate key value violates unique constraint "run_uuid_key"
Sep 11 16:44:49 s00-perf jounrla: runner ERROR   DETAIL: Key 
(uuid)=(95bd7ecf-e106-4cd6-8ab7-14a096843966) already exists.

###############
If I try and schedule a manual test I also encounter the same error, although 
sometimes it schedules successfully.

pscheduler task throughput –source s00-perf.test.lab –dest s02-perf.test.lab
Submitting task…
Task URL:
https://s00-perf.test.lab/pscheduler/tasks/9dbe7c21-37cf-421c-98ce-8f9c6ef12854
Running with tool ‘iperf3’
Fetching first run…

Next scheduled run:
https://s00-perf.test.lab/pscheduler/tasks/9dbe7c21-37cf-421c-98ce-8f9c6ef12854/runs/38c80711-5df7-4ed1-ab75/b9d10731abf4

Run scheduled at 2020-09-11T16:24:48Z is a non-starter:
Failed to post lead run: duplicate key value violates unique constraint 
"run_uuid_key"
DETAIL:  Key (uuid)=(437bda46-9719-4867-95c4-6c7de4013f01) already exists

###############
I even see this with a simple idle diagnostic test, sometimes it works and 
sometimes it doesn't.
pscheduler task idle --duration PT2S
Submitting task...
Task URL:
https://localhost/pscheduler/tasks/53cbff00-8ff7-48a3-88e4-a62e97570c7e
Running with tool 'snooze'
Fetching first run...

Next scheduled run:
https://localhost/pscheduler/tasks/53cbff00-8ff7-48a3-88e4-a62e97570c7e/runs/e38b0363-7e1e-4399-9d71-82d79b224814

Run scheduled at 2020-09-11T18:16:49Z is a non-starter:
Failed to post lead run: duplicate value violates unique constraint 
"run_uuid_key"
DETAIL:  Key (uuid)=(697a8b73-2930-4ceb-8f0c-7f48b61b8b51) already exists

###############
How are the postgres key values being generated and what could lead to 
duplicates? Any assistance in fixing this is much appreciated.

Best,
Ryan
CLASSIFICATION: UNCLASSIFIED

Attachment: smime.p7s
Description: S/MIME cryptographic signature