AWS IoT error <err> aws: Failed to read MQTT input: -128

[z3r0g2017]

AWS IoT error aws: Failed to read MQTT input: -128

from zephyr.

[github-actions]

Hi @z3r0g2017! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

[rlubos]

mqtt_input() returns -ENOTCONN (-128) in case underlying TCP/TLS connection was closed. If you're using qemu_86, it's fairly simple to monitor network traffic with wireshark, just attach it to the corresponding network interface. That should shed some light on whether it's just the peer closing the connection for whatever reason, or some bug in the networking stack.

[z3r0g2017]

I got it to work (hack) with qos1 by handling the mqtt disconnect event which is a noop in the original source code and using a return instead. qos0 is the default when run with qemu_x86. What is the correct config to use for qos1 in the prj.conf or the KConfig ?

[rlubos]

What is the correct config to use for qos1 in the prj.conf or the KConfig ?

There's CONFIG_AWS_QOS defined in the sample's Kconfig file.

by handling the mqtt disconnect event which is a noop in the original source code and using a return instead.

Looking at the sample's code, this change should literally make no difference, the callback returns anyway just after getting MQTT_EVT_DISCONNECT event.

[rlubos]

@z3r0g2017 Do we need to keep this open, given you got the sample to work? I don't know what the bug would be here.

If you still need help here, please provide wireshark logs showing when the client disconnects. Otherwise, please close the issue.