Closed jordanpadams closed 1 year ago
Is this a server-side issue @jordanpadams?
Stepping through the code, the client is calling either of these URLs:
Both return "503 Service Unavailable".
@nutjob4life that is my guess
@jimmie @tloubrieu-jpl βοΈ
If I remove the double backslash (between '1.0' and 'bundles' in the first URI) - I get a valid response albeit one indicating that the LIDVID is not found.
(*forward slash) confirmed.
new error:
INFO π PDS Deep Registry-based Archive, version 1.1.2
DEBUG π’ command line args = Namespace(loglevel=10, include_latest_collection_only=False, url='https://pds.nasa.gov/api/search/1.0', site='PDS_RNG', bundle='urn:nasa:pds:mess_rs_derived::3.0')
DEBUG π€ Comprehending the registry at https://pds.nasa.gov/api/search/1.0 for urn:nasa:pds:mess_rs_derived::3.0
DEBUG βοΈ Asking ``bundle_by_lidvid`` for urn:nasa:pds:mess_rs_derived::3.0
DEBUG βοΈ Asking ``collections_of_a_bundle`` for urn:nasa:pds:mess_rs_derived::3.0 at 0 limit 50
CRITICAL π¨ The server at https://pds.nasa.gov/api/search/1.0 gave an INTERNAL SERVER ERROR; you should contact its administrator if you can figure out who that is. The following information may be helpful to them in figuring out the issue: Β«'{"timestamp":1671740058345,"status":500,"error":"Internal Server Error","path":"/bundles/urn%3Anasa%3Apds%3Amess_rs_derived%3A%3A3.0/collections/all"}'Β»
INFO π Thanks for using this program! Bye!
now blocked by https://github.com/NASA-PDS/registry-api/issues/222
this appears to be working now per fix to NASA-PDS/registry-api#222
π Describe the bug
Running
pds-deep-archive-registry
with both the default config API (pds-gamma) or the operational deployment with--url https://pds.nasa.gov/api/search/1.0/
, yields a connection failure.π To Reproduce
π΅οΈ Expected behavior
Works
π Version of Software Used
1.1.2
π©Ί Test Data / Additional context
See example above
π¦ Related requirements
βοΈ Engineering Details
blocked by https://github.com/NASA-PDS/pds-api/issues/240