-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Timeout Error during Execution #71
Comments
I am using the ansible collection that uses this api in azure and getting timeouts quite often myself. |
Is this project actively maintained? |
In the official documentation, you can define the timeout time as follows, api = UptimeKumaApi('http://localhost:3001', 100), with an example timeout time of 100 seconds. Docs: https://uptime-kuma-api.readthedocs.io/en/latest/api.html#uptime_kuma_api.UptimeKumaApi.get_monitor |
i also have the timeout error. Unfortunately, it's currently not working with my playbooks. @lucasheld it would be great of you can give us a sign if you are currently maintaining this project or not. Thanks! |
Hi,
While making API calls to Uptime Kuma, frequently getting this Timeout Exception.
File "/var/task/uptime_kuma_api/api.py", line 1346, in delete_monitor return self._call('deleteMonitor', id_) File "/var/task/uptime_kuma_api/api.py", line 547, in _call r = self.sio.call(event, data, timeout=self.timeout) File "/var/task/socketio/client.py", line 287, in call raise exceptions.TimeoutError()
when the calls are made from local it has no issue. But when made from a lambda or an EC2, it gets this problem. For Example , if I'm making a get_monitors() call first and if I try to delete few based on the response, It gets timedout there. Logically only one works fine.
Am I missing anything ? can someone help ! TIA
The text was updated successfully, but these errors were encountered: