API errors like:
Bad Gateway</h1> <h3>Whoa! Sorry about that!</h3> <p>Not sure what happened, but it's not meant to work like that!</p> <p>If you're seeing this consistently, can you tell us about it so we can fix it? Send us an email at <a href="mailto:[email protected]" target="_new">[email protected]</a>.</p>
OR
Traceback (most recent call last):
File "<path>\Python*\lib\site-packages\requests\adapters.py", line 439, in send
resp = conn.urlopen(
File ""<path>\Python*\lib\site-packages\urllib3\connectionpool.py", line 747, in urlopen
return self.urlopen(
File ""<path>\Python*\lib\site-packages\urllib3\connectionpool.py", line 747, in urlopen
return self.urlopen(
File ""<path>\Python*\lib\site-packages\urllib3\connectionpool.py", line 747, in urlopen
return self.urlopen(
[Previous line repeated 2 more times]
File ""<path>\Python*\lib\site-packages\urllib3\connectionpool.py", line 719, in urlopen
retries = retries.increment(
File ""<path>\Python*\lib\site-packages\urllib3\util\retry.py", line 436, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='<SERVERNAME>', port=443): Max retries exceeded with url: /api/v1/sensor (Caused by ReadTimeoutError("HTTPSConnectionPool(host='<SERVERNAME>', port=443): Read timed out. (read timeout=120)"))
The api/v1/sensor query will timeout after a certain period of time based on a default configuration of the gunicorn webserver (60 seconds), and if the results exceed 100,000 entries its possible for the query to exceed the timeout.