Error : AWS_ERROR_MQTT_UNEXPECTED_HANGUP

[jvasanthan]

Confirm by changing [ ] to [x] below:

• I've searched for previous similar issues and didn't find any solution

Platform:
Both in Ubuntu 16.04 and ARM

I am receiving the following messages continuously. The behavior is intermittent though. There is no issue in the way the certs, key etc., are handled, made sure there are no 2 instances running with same Client_ID and IOT policy is set right.

Connection interrupted with error libaws-c-mqtt: AWS_ERROR_MQTT_UNEXPECTED_HANGUP, The connection was closed unexpectedly.
Connection resumed
Connection interrupted with error libaws-c-mqtt: AWS_ERROR_MQTT_UNEXPECTED_HANGUP, The connection was closed unexpectedly.
Connection resumed

[jvasanthan]

Sometimes it throws "Error 5136 occured" and continues with

Connection interrupted with error libaws-c-mqtt: AWS_ERROR_MQTT_UNEXPECTED_HANGUP, The connection was closed unexpectedly.
Connection resumed
Connection interrupted with error libaws-c-mqtt: AWS_ERROR_MQTT_UNEXPECTED_HANGUP, The connection was closed unexpectedly.
Connection resumed

[graebm]

Is this causing you an issue, or you're just curious why it's happening occasionally? Is the connection resuming successfully in a reasonable amount of time?

What kind of internet connection do you have (wireless, ethernet, etc)? Wireless connections can be flaky. Is there any pattern to the connection duration (ex: interrupted every 24hrs)?

Are you connecting over websockets? The server will end the connection after 24 hours and the client must reconnect, that's expected behavior.

[jvasanthan]

Hi,

Thank you for your reply

Yes it is creating problem and I am also curious to know why its happening. AWS_ERROR_MQTT_UNEXPECTED_HANGUP message comes up every 500ms-1sec and during that time shadow & job updates are not intermittent, most of the time not received (I tested only shadow & jobs update)

I have tested it with both wireless and ethernet. Ethernet connection seemed to work better but still missed some shadow updates. I have attached application output messages.

Till now I haven't seen any pattern, I ran the application without logger in both wifi and ethernet then I switched on logger to send you more data, AWS_ERROR_MQTT_UNEXPECTED_HANGUP messages didnt come.

No I am not using websockets

ethernet.txt
wifi.txt

[khm971]

For me, this is caused by a duplicate client_id in the mqtt connection. Fort instance, if I have two devices running the same test code, I have to make sure that client_id in the mqtt connection constructor is not duplicated if I'm running the program twice.

[jvasanthan]

Yes I saw your earlier post in the forum and made sure there is no duplication.

[bretambrose]

Can you attach trace level logs showing the failures (https://github.com/awslabs/aws-crt-cpp/blob/master/include/aws/crt/Api.h#L47) ?

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.