Closed amanrique1 closed 11 months ago
The issue is that you used https://cmsweb-testbed.cern.ch/dbs2go-writer
URL which is only used for dev purposes when we test new dbs2go code. The cmsweb-testbed has official DBS instance, https://cmsweb-testbed.cern.ch/dbs/int/global/DBSWriter
. Said that, you can use curl command to check any DBS instance, e.g. here is how you see its APIs:
curl -s -L -k --key ~/.globus/userkey.pem --cert ~/.globus/usercert.pem https://cmsweb-testbed.cern.ch/dbs/int/global/DBSWriter/apis
[{"api":"/dbs/int/global/DBSWriter/physicsgroups","methods":["GET","POST"]},{"api":"/dbs/int/global/DBSWriter/blockorigin","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/filechildren","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/blocks","methods":["GET","POST","PUT","GET"]},{"api":"/dbs/int/global/DBSWriter/fileparents","methods":["GET","POST","GET"]},{"api":"/dbs/int/global/DBSWriter/filesummaries","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/filelumis","methods":["GET","POST"]},{"api":"/dbs/int/global/DBSWriter/acquisitioneras_ci","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/fileparentsbylumi","methods":["POST","POST","GET"]},{"api":"/dbs/int/global/DBSWriter/dbstats","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/status","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/help","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/datatiers","methods":["GET","POST","GET"]},{"api":"/dbs/int/global/DBSWriter/datasets","methods":["GET","POST","PUT","GET"]},{"api":"/dbs/int/global/DBSWriter/parentDSTrio","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/acquisitioneras","methods":["GET","POST","PUT","GET"]},{"api":"/dbs/int/global/DBSWriter/outputconfigs","methods":["GET","POST","GET"]},{"api":"/dbs/int/global/DBSWriter/blockchildren","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/datasetparents","methods":["GET","GET"]},{"api":"/dbs/int/global/DBSWriter/fileArray","methods":["POST"]},{"api":"/dbs/int/global/DBSWriter/healthz","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/runs","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/blockdump","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/blockparents","methods":["GET","POST","GET"]},{"api":"/dbs/int/global/DBSWriter/datasetlist","methods":["POST"]},{"api":"/dbs/int/global/DBSWriter/errors","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/metrics","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/datasetchildren","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/serverinfo","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/blockTrio","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/files","methods":["GET","POST","PUT","GET"]},{"api":"/dbs/int/global/DBSWriter/primarydatasets","methods":["GET","POST","GET"]},{"api":"/dbs/int/global/DBSWriter/releaseversions","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/datatypes","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/processingeras","methods":["GET","POST","GET"]},{"api":"/dbs/int/global/DBSWriter/blocksummaries","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/bulkblocks","methods":["POST"]},{"api":"/dbs/int/global/DBSWriter/primarydstypes","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/datasetaccesstypes","methods":["GET","POST","GET"]},{"api":"/dbs/int/global/DBSWriter/runsummaries","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/apis","methods":["GET"]},{"api":"/dbs/int/global/DBSWriter/dummy","methods":["GET","POST"]},{"api":"/dbs/int/global/DBSWriter/","methods":["GET"]}]
And, offical testbed URLs are:
Moreover, you don't need per-se python client as everything in DBS is based on RESTful APIs which you can use via curl or any other HTTP library, see https://github.com/dmwm/dbs2go/blob/master/docs/Client.md.
Thanks @vkuznet The other test URL worked
I'm using the dbs3-client on Python 3.8 and 3.9. Since last week, I've been getting 502 Proxy Error when calling any method on the test and production URL. The code I'm running has nothing special, it is the following:
The error received is: