[Support Ticket]: Retrievals not working leading to low Spark score

[xiaoliwe]

Curio component

• PoRep Pipeline
• Snap Deals
• Market
• IPNI provider
• Curio UI
• Other

Curio Version

curio version 1.25.1 + mainnet + git_b219def_2025-05-20T18 : 15 : 51 + 04 : 00

Describe the problem

• Why does CurioGUI show no such unsealed sector file?
• Spark retrieval prompts HTTP_500 error. Is there something wrong with our server configuration?

Logging Information

Spark's log
Timestamp                CID                                                                    Protocol   Consensus RetrievalResult
2025-06-15T11:07:06.241Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:07:06.879Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:06:55.120Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:06:55.747Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:06:57.264Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:06:59.007Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:07:00.250Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:07:00.884Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:07:02.481Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:42.931Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:19:04.430Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:55.632Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:56.422Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:58.426Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:04.939Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:09.223Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:09.793Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:10.518Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:12.710Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:13.773Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:17.325Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:18.459Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:30.054Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:32.102Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:33.374Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:34.800Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:36.119Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:18:39.356Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:14:35.279Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:14:05.974Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:15:35.544Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:15:36.179Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500
2025-06-15T11:14:44.020Z bafybeifwisksoxkcpoaxn4lphpru4kljyjaoiog74lmmlhsxpibwbba53q            http       ✅         HTTP_500

Repo Steps

The root cause of the RSR and the data is as follows.

To solve this problem, I followed the Troubleshooting Miner Score to measure and check the nodes and follow the following steps:

Step#01: Inspect recent measurements
.

Step#02: Run a Spark retrieval check locally

I found the CID came from the sector number 7606.

Step#03: To confirm whether it is in the Curio cluster and our storage cluster


The sealed and unsealed sectors have been stored there.