-
Notifications
You must be signed in to change notification settings - Fork 55
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
iotagent-ul does not reconnect to mqtt broker in case of failed connection #251
Comments
Eevn i am facing the same issue.... |
Same problem. We are using iotagent 1.8.0 with docker. |
Could you try with latest version please? |
With the latest version (1.13.0) the problem has been solved. |
@tadeo-n thanks for the positive feedback report! Maybe the issue should be closed. What do you think @chicco785 @Ashokkurukundi ? |
I update the status. Seems with 1.13.0 the problem is less frequent, but still occurs. When MQTT is restarted sometimes IoTAgent does not reconnect to MQTT Broker. |
Under which circustances that occurs? Fully randomly? Or is the some pattern? Note that is the problem cannot be reproduced it is extremely hard to debug and solve... |
For now we haven´t found any pattern. The metrics reach MQTT but IoTAgent is not connecting to it, I don't see any errors on IoTAgent. IoTAgent restarts and the problem is solved. We have updated the version of the MQTT Broker (we are using the eclipse-mosquitto image) to see if it fixes it (I don't think so) . |
I was trying to reproduce your issue.
And then I've start mosquitto again:
|
Are you using any of these options? retries: Number of MQTT connection error retries (default is 5). |
Thanks Alvaro. Now we are using this parameters:
Seems it's working on test environment. Let us try for a while in production. I answer when I have verified. |
Hi tadeo-n Can we know is it stabilized and fixed? any observations such that we can take it up for our deployment as well. |
when the mqtt broker stops or there are connectivity issues, the agent does not recover the connection correctly.
The text was updated successfully, but these errors were encountered: