docker-mosquitto always exits with code 139 when publishing/subscribing with wrong password about docker-mosquitto HOT 3 CLOSED

I am facing the same problem with PostgreSQL back-end too. docker-mosquitto_mosquitto_1 exited with code 139 is what I get when a connection using wrong password is attempted.

Can anyone please tell how to stop the docker container from exiting?

from docker-mosquitto.

I am facing the same issue here...

from docker-mosquitto.

This is due to the plugin failing to contact the backend. In the auth-plugin.conf sample file included, there is a declaration for an http backend. When the first backend is queried for an account with wrong password, this failed and the second one, http, is tried.

Here in quits because libcurl can not connect with the, nonexistent, server.

To fix this issue, add to auth-plugin.conf only the backends configured and the issue will go away.

Anyway, this seems dangerous to me in production. What if you do have an http backend but is temporarily down? I think that I will fix it to be-http.c return BACKEND_DEFER in this case so any other backed could be tried and, most important, the broker don't stop running.

from docker-mosquitto.