Ponte mqtt published event stops firing after ~24 hours

[HAASLEWER]

Hi,

I have a strange issue where the publish event on Ponte for the MQTT broker stops firing the published event after about 24 hours sometimes less, sometimes more. I can see in the logs that the clients connected and disconnected but there are no publish events that fired, even though on the client logs I can see the client connected and published to Ponte. After restarting the node app all the clients reconnect and start publishing again. There are also no errors in the Ponte logs just the connect and reconnect messages.

Has anyone ever come across this? I checked on Mosca issues as well but can't find something similar.

[chombium]

Hi @HAASLEWER,

seems weird. Can you please send us some more info? How do you start Ponte and what's there in your published handler?
What's the message which you receive when the problem happens? Can it be that your processing of the MQTT message somehow breaks?
Can you see the received messages in the Ponte log?

Best Regards,
Jovan

[HAASLEWER]

Hi @chombium,

Thanks for the reply!

I start Ponte in exactly the same way as embedded example in the readme, just on different ports.

The publish handler does quite a few things but mainly it gets the topic and validates that it exists according to a db record and the JSON data is parsed and saved to a mongodb database.

I don't get any kind of message or error, the logger prints out that the client connected and after a while that the client disconnected, just as it normally would but without any publish messages.

No, I can't see the messages at all here's an example of the output:

{"name":"ponte","hostname":"message-broker-02","pid":14938,"service":"MQTT","client":"mqttjs_a7e21509","level":30,"msg":"client connected","time":"2017-03-30T15:17:11.307Z","v":0}
// Usually there would be publish statements here
{"name":"ponte","hostname":"message-broker-02","pid":14938,"service":"MQTT","client":"mqttjs_a7e21509","level":30,"msg":"closed","time":"2017-03-30T15:18:01.312Z","v":0}

This happens on mqtt.js, embedded c, paho python and arduino pubsub mqtt client libraries, all with exactly the same behavior.

Thanks again for the help!