-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Ocasionally when trying to connect the broker gives "Socket error on client <unknown>, disconnecting." #1247
Comments
Do you think you could you try and capture wireshark trace of when this happens? |
My Mosquitto broker instance has been running in the cluster for 178 days straight and worked fine. Today, suddenly it decided to repeatedly reject any client connections.
It started behaving this way relatively after I made an unrelated change in my kubernetes configuration: I exposed some unrelated TCP service through my Nginx Ingress. Edit: |
Hi,
1582069468: Sending CONNACK to auth_manager (0, 0) The big concern for me is I have I'd say this is more like 1/20 for me. |
From time to time, I have the same As all of my devices are exactly the same (hardware and software except devise's name passed to MQTT) I can observe that the issue occurs more often on devices that stand further from my router (but I cannot replicate it when taking one of them with a power bank power supply of the range of the router). From my perspective, another, noticeable, issue is that after the Any ideas if it's possible to fetch "last will" on such kind of errors? |
@kotu-pl What version of Mosquitto are you using? Are you absolutely sure that a Will message is being set on your client? If you are able to provide a wireshark/tcpdump trace of the broker we may be able to figure out what is happening. |
the same issue was observed in my setup also I am using mosquitto-1.5.5 thanks, |
There seems to be several related problems (#523, #1023, #7, #1197) but I am not sure, so I am posting a new issue.
I have a simple test where
Once every few 100 attempts I get from the broker
I am using v1.6 and the C++ interface in mosquittopp. Below is the test code.
The console output is.
I thought that the problem may be that disconnect is being sent too quickly, but that is not it. The output then is.
As you can see the client attempts the connection again if it fails.
I have another more complex test where publishing and subscribing are involved also. There I get the error more often.
The text was updated successfully, but these errors were encountered: