influxdb-client-python: Write to InfluxDB cloud fails with ApiException: (503) Reason: Service Unavailable; upstream connect error or disconnect/reset before headers. reset reason: connection failure

Steps to reproduce: Using the Python client make repeated calls to the write API. Do this simultaneously from 2 or 3 different clients (not sure if this is relevant but this is the fail condition) Write rates are a call to the API every second or so I’m using the SYNCHRONOUS calls

influx_client = InfluxDBClient(url=os.environ['influx_url'], token=os.environ['token'],retries=retries) write_api = influx_client.write_api(write_options=SYNCHRONOUS) (repeatedly) influx_returns = write_api.write(InfluxBucket, my_org, Influx_lines,'ms')

Expected behavior: Until 17th Aug we were seeing the expected behaviour. All the writes succeeded.
Data was written reliably

Actual behavior: From 17th August we started getting

ApiException: (503) Reason: Service Unavailable; upstream connect error or disconnect/reset before headers. reset reason: connection failure

The errors definitely started on 17th Aug and I know we didn’t change anything because everyone was on holiday! I have AWS logs which show when this started image

You can see the discussion here that it’s affecting multiple users now

Specifications:

  • Python 3.8:
  • InfluxDB Version: Cloud v2
  • Platform: AWS Lambda written in Python

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 44 (7 by maintainers)

Most upvoted comments

Hi @bednar , Sorry asmith == @gefaila == myself That’s the code I myself posted here. And I posted that because it doesn’t work. 😃

As I explain in the post there, it fails with

HTTPSConnectionPool(host=‘eu-central-1-1.aws.cloud2.influxdata.com’, port=443): Max retries exceeded with url: /api/v2/write?orgID=xxxxxxxxxxxx&bucket=TEST_bucket&precision=ms (Caused by SSLError(SSLError(“bad handshake: Error([(‘SSL routines’, ‘tls_process_server_certificate’, ‘certificate verify failed’)])”)))

I think what’s needed is some code that has actually been verified as working with InfluxDB 2.0 Cloud