On_disconnect() : Unexpected disconnection from broker

[ngrataloup]

Bonjour,

J’ai regulierement ce type d’erreurs dans jmqtt ! ce qui correspond à l’ensemble de mes brokers

0071|[2024-11-04 17:16:18,061] ERROR  Client450       Brk450Th     on_disconnect() : Unexpected disconnection from broker!
0072|[2024-11-04 18:12:30,032] ERROR  Client536       Brk536Th     on_disconnect() : Unexpected disconnection from broker!
0073|[2024-11-04 19:12:48,017] ERROR  Client1010      Brk1010Th    on_disconnect() : Unexpected disconnection from broker!
0074|[2024-11-04 19:13:44,600] ERROR  Client450       Brk450Th     on_disconnect() : Unexpected disconnection from broker!
0075|[2024-11-04 19:13:44,601] ERROR  Client450       Brk450Th     on_disconnect() : Unexpected disconnection from broker!
0076|[2024-11-04 20:12:36,058] ERROR  Client840       Brk840Th     on_disconnect() : Unexpected disconnection from broker!
0077|[2024-11-04 20:12:36,059] ERROR  Client901       Brk901Th     on_disconnect() : Unexpected disconnection from broker!
0078|[2024-11-04 20:12:45,162] ERROR  Client450       Brk450Th     on_disconnect() : Unexpected disconnection from broker!
0079|[2024-11-04 20:12:45,163] ERROR  Client450       Brk450Th     on_disconnect() : Unexpected disconnection from broker!
0080|[2024-11-04 20:12:48,007] ERROR  Client536       Brk536Th     on_disconnect() : Unexpected disconnection from broker!
0081|[2024-11-04 20:12:48,008] ERROR  Client1010      Brk1010Th    on_disconnect() : Unexpected disconnection from broker!
0082|[2024-11-04 22:14:06,046] ERROR  Client840       Brk840Th     on_disconnect() : Unexpected disconnection from broker!
0083|[2024-11-04 22:14:12,092] ERROR  Client536       Brk536Th     on_disconnect() : Unexpected disconnection from broker!

Coté mqtt manager, j’observe aussi ces déconnexions

0015|[2024-11-04 04:12:37] ERROR  : Reconnection to mqtt server
0016|[2024-11-04 05:12:37] ERROR  : Reconnection to mqtt server
0017|[2024-11-04 08:13:37] ERROR  : Reconnection to mqtt server
0018|[2024-11-04 10:14:37] ERROR  : Reconnection to mqtt server
0019|[2024-11-04 12:13:37] ERROR  : Reconnection to mqtt server
0020|[2024-11-04 13:12:43] ERROR  : Reconnection to mqtt server
0021|[2024-11-04 14:12:37] ERROR  : Reconnection to mqtt server

Les erreurs semble etre toujours entre XXh12 et XXh14

Coté mosquitto, RAS … mon mosquitto est installé sur un docker (indepedant de Jeedom), mais aucune trace d’arret dans les logs et le process linux est daté du 3 Nov. (dernier reboot), donc pas de relances aux xxh12

bref, je ne vois pas trop d’ou viennent ces déconnexions !

Si quelqu’un a une idée

Norbert

[ngrataloup]

Bon, j’affine le sujet.
Mon pb est detecté coté mosquitto. les connexions passent en timeout à XXh12 aléatoirement :

2024-11-05T02:12:27.015870120Z 1730772747: Client jmqtt_frigate has exceeded timeout, disconnecting.
2024-11-05T02:12:27.016100544Z 1730772747: Client auto-C5CCB50B-7B79-ED07-22EA-AA47DB085362 has exceeded timeout, disconnecting.
2024-11-05T02:12:39.014251904Z 1730772759: Client mqtt-jeedom_0.37ca7d has exceeded timeout, disconnecting.
2024-11-05T02:12:39.014790048Z 1730772759: Client DVES_1638FA has exceeded timeout, disconnecting.
2024-11-05T02:13:21.026427678Z 1730772801: Client auto-BE1DBDB0-C0B0-84CE-E8D4-EB6C380D6A73 has exceeded timeout, disconnecting.
2024-11-05T02:13:27.065254683Z 1730772807: Client shellyswitch25-68C63AF91E07 has exceeded timeout, disconnecting.
2024-11-05T02:13:27.066151298Z 1730772807: Client DVES_15835D has exceeded timeout, disconnecting.
2024-11-05T02:14:09.070737698Z 1730772849: Client mqttjs_e7a1de4e has exceeded timeout, disconnecting.
2024-11-05T02:14:15.063581210Z 1730772855: Client shellyswitch25-68C63AF91E97 has exceeded timeout, disconnecting.
2024-11-05T02:15:15.089830228Z 1730772915: Client DVES_15835D has exceeded timeout, disconnecting.
2024-11-05T03:12:21.021016054Z 1730776341: Client auto-B19C472B-1E0B-60E3-9509-E983BB6DF89A has exceeded timeout, disconnecting.
2024-11-05T03:12:39.018689219Z 1730776359: Client DVES_15835D has exceeded timeout, disconnecting.
2024-11-05T03:12:45.074791816Z 1730776365: Client DVES_1638FA has exceeded timeout, disconnecting.
2024-11-05T04:12:27.033140166Z 1730779947: Client jmqtt_tasmotas has exceeded timeout, disconnecting.
2024-11-05T04:12:27.033405300Z 1730779947: Client jmqtt_frigate has exceeded timeout, disconnecting.
2024-11-05T04:12:33.082859270Z 1730779953: Client auto-1D412C9C-58F1-8562-F7CC-B093552ABBAA has exceeded timeout, disconnecting.
2024-11-05T04:12:33.083021734Z 1730779953: Client auto-10A9AF77-560A-F5EE-23C4-2F7D4C5D96DD has exceeded timeout, disconnecting.
2024-11-05T04:12:33.083116237Z 1730779953: Client DVES_15835D has exceeded timeout, disconnecting.
2024-11-05T05:12:45.041496380Z 1730783565: Client DVES_1638FA has exceeded timeout, disconnecting.
2024-11-05T05:12:45.041704304Z 1730783565: Client auto-7CE1359B-2998-8C5D-5EC8-98CB065E69D3 has exceeded timeout, disconnecting.
2024-11-05T05:12:45.041792391Z 1730783565: Client auto-BB2F59A6-E688-EB0E-A0A8-1E9C97ABF324 has exceeded timeout, disconnecting.
2024-11-05T06:12:39.006379544Z 1730787159: Client DVES_1638FA has exceeded timeout, disconnecting.
2024-11-05T07:12:33.072128157Z 1730790753: Client jmqtt_tasmotas has exceeded timeout, disconnecting.
2024-11-05T07:12:33.072399416Z 1730790753: Client DVES_1638FA has exceeded timeout, disconnecting.

donc le pb, ou la source du pb est plutot à chercher de ce coté là …

[ngrataloup]

Et du coup, à force de creuser, je pense avoir trouver le coupable.
J’ai un docker speedtest2mqtt qui se lance à xxh12 et qui me remonte le serreurs suivantes (alors qu eles données remontent bien :

2024-11-05T06:12:00.500653589Z INFO:yacron:Starting job speedtest
2024-11-05T06:12:00.517949592Z INFO:yacron:Job speedtest spawned
2024-11-05T06:12:00.529905122Z [speedtest stdout] 2024-11-05T06:12:00+00:00 starting speedtest
2024-11-05T06:12:06.896578530Z {
2024-11-05T06:12:06.896773078Z     "type": "log",
2024-11-05T06:12:06.896824413Z     "timestamp": "2024-11-05T06:12:06Z",
2024-11-05T06:12:06.896868165Z     "message": "Error: [11] Cannot read from socket: Resource temporarily unavailable",
2024-11-05T06:12:06.896911624Z     "level": "error"
2024-11-05T06:12:06.896953626Z }
2024-11-05T06:12:33.048250219Z [speedtest stdout] 2024-11-05T06:12:33+00:00 speedtest results
2024-11-05T06:12:33.052873876Z [speedtest stdout] 2024-11-05T06:12:33+00:00 download = 18.79 Mbps
2024-11-05T06:12:33.055936563Z [speedtest stdout] 2024-11-05T06:12:33+00:00 upload =  14.94 Mbps
2024-11-05T06:12:33.061081071Z [speedtest stdout] 2024-11-05T06:12:33+00:00 ping =  35.575 ms
2024-11-05T06:12:33.066302956Z [speedtest stdout] 2024-11-05T06:12:33+00:00 jitter = 1.403 ms
2024-11-05T06:12:33.071768974Z [speedtest stdout] 2024-11-05T06:12:33+00:00 sending results to 192.168.8.200 as clientID speedtest2mqtt with options -r using user speedtest
2024-11-05T06:13:33.150002381Z Error: Unknown error.
2024-11-05T06:15:03.678066532Z INFO:yacron:Job speedtest exit code 0; has stdout: true, has stderr: false; fail_reason: None
2024-11-05T06:15:03.678811849Z INFO:yacron:Cron job speedtest: reporting success

J’imagine que pour une raison x ou y, ce docker me sature l’interface MQTT …
Docker desactiver pour voir si le pb persiste

[ngrataloup]

Bon, ben j’ai finalement trouvé … une commande mosquitto_sub avec l’option -r (pour retain) du docker speedtest2mqtt qui devait me saturer mon mosquitto et qui plantait au bout de 3-4min, et faisait planter les autres connexions

J’ai modifié les options d’envoi de la commande mosquitto_sub, à suivre

Norbert

[vegeta0911]

Tu est trop fort tu pose le problème, tu fait le dépannage, et la résolution. Bravo