Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] No Test results in homepage - No data available in table

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] No Test results in homepage - No data available in table


Chronological Thread 
  • From: Mark Feit <>
  • To: Michael Johnson <>, Daniel Matthews <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] No Test results in homepage - No data available in table
  • Date: Thu, 24 Jan 2019 22:32:34 +0000
  • Accept-language: en-US
  • Authentication-results: globalnoc.iu.edu; dkim=none (message not signed) header.d=none;globalnoc.iu.edu; dmarc=none action=none header.from=internet2.edu;
  • Ironport-phdr: 9a23:NwgCnRQ4cDvFcKUA668BpZIbWdpsv+yvbD5Q0YIujvd0So/mwa67ZBWPt8tkgFKBZ4jH8fUM07OQ7/iwHzRYqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjWwba9xIRmssQndqtQdjJd/JKo21hbHuGZDdf5MxWNvK1KTnhL86dm18ZV+7SleuO8v+tBZX6nicKs2UbJXDDI9M2Ao/8LrrgXMTRGO5nQHTGoblAdDDhXf4xH7WpfxtTb6tvZ41SKHM8D6Uaw4VDK/5KpwVhTmlDkIOCI48GHPi8x/kqRboA66pxdix4LYeZyZOOZicq/Ye94RWGhPUdtLVyFZAo2ycZYBD/YPM+hboYnypVoOogexCwajH+7v1iRHhnrq0aEmz+gsEwfL1xEgEdIUt3TUqc34OqAIXuCvz6nD0DXNYO1X2Tfh9YPFdRUhof+SUrJxbcrc0kgvFwXZjlqOs4zlOS2a1vgTv2SB8eVvSP+vhnchpgpsrDavwcIshZPIhoIT0l3I6Dt1zYIvKdGmVkJ3e8OoHZtUui2AKod6X8cvTmd1syg50r0LoYC3czIWxJg6whPTduGLf5WN7xLtW+udPSt0iXdndb2hiBu+7E2tx+jiWsWo31tGtjdJn9vCu3wX1RHe7tKLRuZj8ku8wzqDyg7e5+BcLUA6i6XWKIItz7s1m5ccsknMACz7lUD4gaKZeEgp9e2l5uv6bbjoqJ+RMo15hw78P6s0nMG0HP42PRIUX2eB/OSxzL3j8lP9QLVNlvA4irXUvpfGKcgGv6K0Hhdb34g65xa4FDipzs4UnX4aLFJZYx2HiJXpO1fTL/ziFfe/mVOskCt1yP/aIr3hA5LNLn7ZnLfmYLZ990pcyA00zdBc/Z5bFrYBIPfrVk/wstzXEAM5PhSqz+n9FNlxy4YTVX+SDqOENa7Sv1CF6v4zL+SJZoIapjnwJ+Ug6vPrk3M1hVAQcbGs3ZQNaXC4GvpmI1+eYXrpmtoBFGkKsRQ/TOz2k1CCUDhTZ2qsUKIm4DE0Fp6mAZnZSo+znbOBwT+3HodKaWBeFlCMDXDoep2cW/gSciKSLNRhkjsCVbe7UY8tzAyutBTkxLp9NefU/iwYtYn/1Nhu+eHfjxAy9TpoD8uDyWGNSX97nn8WSzMswq9wvFF9mR+/1v1dgvdYHNFXr9FOUgEhMpiUm+l4W4raVQbGdN6NTlGtBNS7Rzw9U4R1i/MHZUdwH52Hhwzf3ye1GPdBm7eOVMUc+avH0j78K9srmFjc06x0qlA8QYNhOGy6zvp6+QXSG6bIlVmUjaCnaf5a0SLQojTQhVGStV1VBVYjGZ7OWmoSMw6P9YyjvBHLUqOuBLI7MwBI1c+FLO5QZ8b0iUldHay/atvaZGi4n2G3DlCJ2/WBYJe5M2ke3SCIDk8CnkhT+HudLgExC2+npH6WFz1hE1/jIiaOuelzoX+2VAk4mgeNaUAy2L6y8BcRg/uXDfIOmL8IpXRppzB9Bl3o2dXQBpKJrBZge6MJZ9Q77TIlnWLUvgBwJNquNadn018YbwltuU7yjVN6BpgTnA==

Michael Johnson writes:

It looks like something isn't archiving correctly, either due to
something in esmond, or something in pscheduler's esmond archiver.

If you run something like this, you may get some insight into what is
going on
curl -k
https://129.22.159.119/pscheduler/tasks/621269ac-75dd-4120-9d41-42372141e988/runs/f0d5082b-3813-41b9-a9a6-cd083995abb0?pretty

Another way to do this would be to use the "result" command to dump the run
and archiving diagnostics:

pscheduler result --diags --archivings
https://129.22.159.119/pscheduler/tasks/621269ac-75dd-4120-9d41-42372141e988/runs/f0d5082b-3813-41b9-a9a6-cd083995abb0

--Mark





Archive powered by MHonArc 2.6.19.

Top of Page