Plantage de la jeedom smart de plus en plus souvent

Bonjour. Avant d’ouvrir un ticket, je me permets de communiquer les logs que je trouve après un plantage qui m’oblige à faire un arrêt marche au bouton. Je n’arrive pas à trouver d’où ca vient. J’ai créé une autre box qui pilote une prise pour relancer le jeedom, mais j’avoue que c’est galère. Merci de vos idées.

MQTT2d me donne (je n’inscris qu’une ligne, le reste est en boucle pareil)

0000|[2024-02-14 09:38:59]ERROR : Error on send to jeedom : {"message":"connect ETIMEDOUT 127.0.0.1:80","name":"Error","stack":"Error: connect ETIMEDOUT 127.0.0.1:80 0001|at AxiosError.from (/var/www/html/plugins/mqtt2/resources/mqtt2d/node_modules/axios/dist/node/axios.cjs:837:14) 0002|at RedirectableRequest.handleRequestError (/var/www/html/plugins/mqtt2/resources/mqtt2d/node_modules/axios/dist/node/axios.cjs:3016:25) 0003|at RedirectableRequest.emit (node:events:517:28) 0004|at eventHandlers.<computed> (/var/www/html/plugins/mqtt2/resources/mqtt2d/node_modules/follow-redirects/index.js:14:24) 0005|at ClientRequest.emit (node:events:517:28) 0006|at Socket.socketErrorListener (node:_http_client:501:9) 0007|at Socket.emit (node:events:517:28) 0008|at emitErrorNT (node:internal/streams/destroy:151:8) 0009|at emitErrorCloseNT (node:internal/streams/destroy:116:3) 0010|at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"adapter":["xhr","http"],"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-T**OK**EN","xsrfHeaderName":"X-XSRF-T**OK**EN","maxContentLength":-1,"maxBodyLength":-1,"env":{},"headers":{"Accept":"application/json, text/plain, */*","Content-Type":"application/x-www-form-urlencoded","User-Agent":"axios/1.5.1","Content-Length":"122","Accept-Encoding":"gzip, compress, deflate, br"},"method":"post","url":"http://127.0.0.1:80/plugins/mqtt2/core/php/jeeMqtt2.php?apikey=DfpcpeJwx5g43xbMPQSYZ7FecerSMMBchJkpGu7qIrgGd8K92BY547KBudJHkjat","data":"{\"iRobot\":{\"feedback\":{\"31F4020081514600\":{\"signal_rssi\":-32,\"signal_snr\":57,\"error_message\":\"None\",\"state\":\"Charging\"}}}}"},"code":"ETIMEDOUT","status":null} 0011



Zwave me dit

0000|[2024-02-14 09:49:25]ERROR : Error on send request to jeedom HTTPConnectionPool(host='127.0.0.1', port=80): Max retries exceeded with url: /plugins/openzwave/core/php/jeeZwave.php?apikey=hLZNE3UvLTeavWF9Mr94f64Yu79hfD3e (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f7007ccd0>, 'Connection to 127.0.0.1 timed out. (connect timeout=0.5)')) retry : 0/3
0001|[2024-02-14 09:49:25]ERROR : Error on send request to jeedom HTTPConnectionPool(host='127.0.0.1', port=80): Max retries exceeded with url: /plugins/openzwave/core/php/jeeZwave.php?apikey=hLZNE3UvLTeavWF9Mr94f64Yu79hfD3e (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f7007c6d0>, 'Connection to 127.0.0.1 timed out. (connect timeout=0.5)')) retry : 1/3
0002|[2024-02-14 09:49:25]ERROR : Error on send request to jeedom HTTPConnectionPool(host='127.0.0.1', port=80): Max retries exceeded with url: /plugins/openzwave/core/php/jeeZwave.php?apikey=hLZNE3UvLTeavWF9Mr94f64Yu79hfD3e (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f5048a210>, 'Connection to 127.0.0.1 timed out. (connect timeout=0.5)')) retry : 2/3
0003|[2024-02-14 09:49:25]ERROR : Critical error on  send_changes_async local variable 'r' referenced before assignment
0004

RfPlayer me donne

0000|[2024-02-14 09:46:18.565]ERROR : Error on send request to jeedom HTTPConnectionPool(host='127.0.0.1', port=80): Read timed out. (read timeout=120) retry : 1/3
0001|[2024-02-14 09:46:19.577]ERROR : Error on send request to jeedom HTTPConnectionPool(host='127.0.0.1', port=80): Max retries exceeded with url: /plugins/rfplayer2/core/php/jeeRfplayer2.php?apikey=KjG9TSOX3viYe4uIQ51ntPfMrUcSh59k (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f75743b70>, 'Connection to 127.0.0.1 timed out. (connect timeout=1.0)')) retry : 2/3
0002|[2024-02-14 09:46:21.085]ERROR : Error on send request to jeedom HTTPConnectionPool(host='127.0.0.1', port=80): Max retries exceeded with url: /plugins/rfplayer2/core/php/jeeRfplayer2.php?apikey=KjG9TSOX3viYe4uIQ51ntPfMrUcSh59k (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f757355c0>, 'Connection to 127.0.0.1 timed out. (connect timeout=1.5)')) retry : 3/3
0003|[2024-02-14 09:46:21.085]ERROR : Critical error on  send_changes_async local variable 'r' referenced before assignment
0004

En complément une vérification complète me donne


[START CONSISTENCY] [START CHECK AND FIX DB] [END CHECK AND FIX DB] Check jeedom package... **OK** Check jeedom database...**OK** Check crons... Check filesystem right... **OK** Flush cache widget... Check jeedom object...**OK** Check jeedom cmd...**OK** Set cache hour...**OK** Check nodejs... E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'oldstable' to 'oldoldstable' E: Repository 'http://ftp.uk.debian.org/debian buster InRelease' changed its 'Suite' value from 'oldstable' to 'oldoldstable' E: Repository 'http://ftp.uk.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'oldstable-updates' to 'oldoldstable-updates' E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/g/git/git_2.20.1-2+deb10u6_arm64.deb 404 Not Found [IP: 2a04:4e42:6a::644 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Vérification si la source deb-multimedia existe (bug lors du apt-get update si c'est le cas) deb-multimedia existe ! Désactivation de la source deb-multimedia ! Get:1 http://security.debian.org/debian-security buster/updates InRelease [34.8 kB] Hit:2 https://deb.nodesource.com/node_18.x nodistro InRelease Get:3 http://ftp.uk.debian.org/debian buster InRelease [122 kB] Get:4 http://ftp.uk.debian.org/debian buster-updates InRelease [56.6 kB] Hit:5 https://oph.mdrjr.net/meveric all InRelease Get:6 https://oph.mdrjr.net/meveric buster InRelease [4131 B] Get:7 https://oph.mdrjr.net/meveric buster/main arm64 Packages [48.0 kB] Reading package lists... Reading package lists... Building dependency tree... Reading state information... apt-utils is already the newest version (1.8.2.3). build-essential is already the newest version (12.6). lsb-release is already the newest version (10.2019051400). Suggested packages: git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-cvs git-mediawiki git-svn Recommended packages: less The following packages will be upgraded: git 1 upgraded, 0 newly installed, 0 to remove and 246 not upgraded. Need to get 5506 kB of archives. After this operation, 67.6 kB of additional disk space will be used. Err:1 http://security.debian.org/debian-security buster/updates/main arm64 git arm64 1:2.20.1-2+deb10u6 404 Not Found [IP: 2a04:4e42:6a::644 80] [Check Version NodeJS actuelle : v18.19.0 : [ **OK** ] [Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ **OK** ] Réactivation de la source deb-multimedia qu'on avait désactivé ! **OK** [END CONSISTENCY]

Bonjour.

Mettez une copie d’écran de la page santé svp.

Merci de votre réponse:

Bonjour,

oldoldstable : Impossibilité d'installer les dépendances mqtt - #4 par akenad

akenad :slight_smile:

Merci, je vais voir ce que cela donne dans le temps. Par contre le plugin kroomba ne fonctionne plus, la dépendance ne se lance pas et ne se réinstalle pas, mqtt2. Mais peut-être rien à voir. Beaucoup de mises à jour se sont déclenchées.