-
Notifications
You must be signed in to change notification settings - Fork 1k
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
OSError: [Errno 104] ECONNRESET #174
Comments
Not sure if this is any help - a comment in some example code
|
Do u mean to change this in the lib?!... Just to understand my simple aplication:
If could I treat this error in my application would be better than change something in the lib...u dont think so?!... couldn't stop an aplication because this. I'll seize to ask if when reconect in my broker it's possible subscribe in topic... because I was noticed that when mqtt client is down (offline) and active reconect mode, block all aplication (including whiles and so on). |
Apologies, I hadn't read it properly and rushed to reply. My original comment is no help and should be ignored. |
Is this still a problem in the latest version of mqtt.simple ? |
Hey, I've a question about connect method in umqtt lib: In the first time connection, even using robust mqtt, my broker need be on-line. If my server is Down at the moment return this error:
Traceback (most recent call last):
File "umqtt/simple.py", line 56, in connect
OSError: [Errno 104] ECONNRESET
If my broker is on-line at first connection, and after i put down my server, it keeps working well (trying reconnect).
So, can I treat this error for dont stop my application, or it's a problem in the lib?
The text was updated successfully, but these errors were encountered: