[Errno 111] Connection refused
I somehow made some change to gracedb-dev1
triggers a client error that gstlal
has seen on occasion on gracedb-playground
. And I'm seeing it with the redhat and conda distributions of the client code. Example:
[~]$ gracedb -s https://gracedb-playground.ligo.org/api/ ping
Response from https://gracedb-playground.ligo.org/api/: 200 OK
[~]$ gracedb -s https://gracedb-dev1.ligo.org/api/ ping
Error: HTTPSConnectionPool(host='gracedb-dev1.ligo.org', port=443): Max retries exceeded with url: /api/ (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f4991fd3a20>: Failed to establish a new connection: [Errno 111] Connection refused',))
[~]$ conda activate igwn-py39
(igwn-py39) [~]$ gracedb -s https://gracedb-dev1.ligo.org/api/ ping
Error: HTTPSConnectionPool(host='gracedb-dev1.ligo.org', port=443): Max retries exceeded with url: /api/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7faa599e8070>: Failed to establish a new connection: [Errno 111] Connection refused'))
I'm not seeing an error in the gunicorn logs, so i think it might be being booted at apache before it even reaches the gracedb app. I have verbose apache logging enabled on dev1, so maybe this will elucidate what might be happening in the cloud.