Problème MQTT Manager suite à mise à jour des dépendances Z2M

Plugins
, ,
1

Bonjour,

Comme déjà deux ou 3 fois, j’ai un message qui me dit de mettre à jour les dépendances suite à Z2M 1.37.0.

Je lance la mise à jour des dépendances et je reçois un indication que le plugin MQTT2 n’est pas démarré.
J’essaie de forcer le redémarrage et je reçois la nitification suivante:

image
image844×166 18.8 KB

Effectivement les droits sur le fichier log mqtt2 sont root root.

image
image920×56 15.5 KB

Le contenu du fichier est:

[2024-05-12 15:50:00][INFO] : Début d'activation du plugin
[2024-05-12 15:50:01][INFO] : Info sur le démon : {"log":"mqtt2","state":"nok","launchable":"ok","launchable_message":"Gestion automatique d\u00e9sactiv\u00e9e","auto":"0","last_launch":"2024-05-03 18:26:20"}
[2024-05-12 15:50:04][INFO] : Début d'activation du plugin
[2024-05-12 15:50:05][INFO] : Info sur le démon : {"log":"mqtt2","state":"nok","launchable":"ok","launchable_message":"Gestion automatique d\u00e9sactiv\u00e9e","auto":"0","last_launch":"2024-05-03 18:26:20"}
r

Les droits sur update sont également root root et le contenu est:

[2024-05-12 15:49:58][ALERT] : Début de la mise à jour de : mqtt2
[2024-05-12 15:49:58][ALERT] : Téléchargement du plugin (source : market)...
[2024-05-12 15:49:58][ALERT] : Téléchargement de mqtt2...
[2024-05-12 15:49:58][ALERT] : URL https://market.jeedom.com/core/php/downloadFile.php?id=4213&version=stable&jeedomversion=4.4.5&hwkey=aaf0a3db9e84d171f9931f662ef46f03f4957a9b&username=hbisteau&password=2095b1a69caf5618235e6509860e7dd9fbfaec6c&password_type=sha1
--2024-05-12 15:49:58--  https://market.jeedom.com/core/php/downloadFile.php?id=4213&version=stable&jeedomversion=4.4.5&hwkey=aaf0a3db9e84d171f9931f662ef46f03f4957a9b&username=hbisteau&password=2095b1a69caf5618235e6509860e7dd9fbfaec6c&password_type=sha1
Resolving market.jeedom.com (market.jeedom.com)... 57.128.120.126
Connecting to market.jeedom.com (market.jeedom.com)|57.128.120.126|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/octet-stream]
Saving to: '/tmp/jeedom/market/mqtt2.zip'

     0K .......... .......... .......... .......... .......... 1.96M
    50K .......... .......... .......... .......... .......... 1.86M
   100K .......... .......... .......... .......... .......... 3.02M
   150K .......... .......... .......... .......... .......... 3.28M
   200K .......... .......... .......... .......... .......... 1.94M
   250K .......... .......... .......... .......... .......... 3.36M
   300K .......... .......... .......... .......... .......... 3.45M
   350K .......... .......... .......... .......... .......... 6.49M
   400K .......... .......... .......... .......... .......... 3.43M
   450K .......... .......... .......... .......... .......... 6.53M
   500K .......... .......... .......... .......... .......... 3.54M
   550K .......... .......... .......... .......... .......... 6.43M
   600K ........                                                122M=0.2s

2024-05-12 15:49:59 (3.18 MB/s) - '/tmp/jeedom/market/mqtt2.zip' saved [622620]

[2024-05-12 15:49:59][ALERT] : OK
[2024-05-12 15:49:59][ALERT] : Décompression du zip...
[2024-05-12 15:49:59][ALERT] : OK
[2024-05-12 15:49:59][ALERT] : Action de pré-update...
[2024-05-12 15:49:59][ALERT] : OK
[2024-05-12 15:49:59][ALERT] : Post-installation de mqtt2...
[2024-05-12 15:49:59][ALERT] : Vérification des droits sur les fichiers...
[2024-05-12 15:50:00][ALERT] : OK
[2024-05-12 15:50:00][ALERT] : Suppression des fichiers inutiles...
[2024-05-12 15:50:04][ALERT] : OK
[2024-05-12 15:50:04][ALERT] : END UPDATE SUCCESS

Informations Jeedom

Core : 4.4.5 (V4-stable)
DNS Jeedom : non

Plugin : MQTT Manager
Version : 2024-03-26 01:21:05 (stable)
Statut Démon : Stoppé - (2024-05-12 15:55:02)

Pourquoi cela se produit il ? N’est pas un bug de la mise à jour des dépendances du plugin Z2M.

Personnellement, je ne suis pas bloqué. Destruction des logs mqtt2, update et redémarrage de mqtt2 et ensuite de z2m.

2

Bonsoir.

Si vous utilisez la fonctionnalité de Jeedom pour rétablir les droits, c’est se reproduit aussi ?

3

Je n’ai pas essayé.
J’ai effectué

sudo su -
cd /var/www/html/log
rm mqtt2
rm update

Ensuite le redémarrage de mqtt2 se passe sans problème et le fichier de log est créé comme ceci

image
image934×52 15.1 KB

Edit: J’aai essayé. Les droits reviennent bien mais le problème se reproduit lors d’une nouvelle demandde de mise à jour des dépendances.

4

Lors de cette nouvelle tentative de mise à jour des dépendances de JeeZigbee (Z2m). On reproduit le même problème.
Daans le log z2m_packages, il y a une erreur « PHP Fatal error » en fin de fichier.
Le log est ci-dessous:

0000|+ echo '*******************Begin of package installation******************'
0001|*******************Begin of package installation******************
0002|+ touch /tmp/jeedom_install_in_progress_z2m
0003|+ echo 1
0004|+ echo 2
0005|+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
0006|+ sudo /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
0007|Launch pre-install of z2m dependancy
0008|+ echo 3
0009|+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
0010|apt: no process found
0011|apt-get: no process found
0012|unattended-upgr: no process found
0013|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0014|Get:1 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB]
0015|Hit:2 http://http.us.debian.org/debian bullseye InRelease
0016|Get:3 http://http.us.debian.org/debian bullseye-updates InRelease [44.1 kB]
0017|Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
0018|Fetched 92.4 kB in 1s (136 kB/s)
0019|Reading package lists...
0020|Building dependency tree...
0021|Reading state information...
0022|14 packages can be upgraded. Run 'apt list --upgradable' to see them.
0023|Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
0024|Hit:2 http://http.us.debian.org/debian bullseye InRelease
0025|Hit:3 http://http.us.debian.org/debian bullseye-updates InRelease
0026|Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
0027|Reading package lists...
0028|Reading package lists...
0029|Building dependency tree...
0030|Reading state information...
0031|apt-utils is already the newest version (2.2.4).
0032|build-essential is already the newest version (12.9).
0033|git is already the newest version (1:2.30.2-1+deb11u2).
0034|lsb-release is already the newest version (11.1.0).
0035|0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
0036|[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
0037|[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
0038|Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
0039|Hit:2 http://http.us.debian.org/debian bullseye InRelease
0040|Hit:3 http://http.us.debian.org/debian bullseye-updates InRelease
0041|Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
0042|Reading package lists...
0043|Reading package lists...
0044|Building dependency tree...
0045|Reading state information...
0046|apt-utils is already the newest version (2.2.4).
0047|build-essential is already the newest version (12.9).
0048|git is already the newest version (1:2.30.2-1+deb11u2).
0049|lsb-release is already the newest version (11.1.0).
0050|0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
0051|[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
0052|[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
0053|Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
0054|Hit:2 http://http.us.debian.org/debian bullseye InRelease
0055|Hit:3 http://http.us.debian.org/debian bullseye-updates InRelease
0056|Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
0057|Reading package lists...
0058|Reading package lists...
0059|Building dependency tree...
0060|Reading state information...
0061|apt-utils is already the newest version (2.2.4).
0062|build-essential is already the newest version (12.9).
0063|git is already the newest version (1:2.30.2-1+deb11u2).
0064|lsb-release is already the newest version (11.1.0).
0065|0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
0066|[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
0067|[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
0068|--2024-05-14 18:05:19--  https://getcomposer.org/installer
0069|Resolving getcomposer.org (getcomposer.org)... 2001:41d0:302:1100::8:104f, 54.36.53.46
0070|Connecting to getcomposer.org (getcomposer.org)|2001:41d0:302:1100::8:104f|:443... connected.
0071|HTTP request sent, awaiting response... 200 OK
0072|Length: 58444 (57K) [application/octet-stream]
0073|Saving to: 'composer-setup.php'
0074|0K .......... .......... .......... .......... .......... 87% 6.56M 0s
0075|50K .......                                               100%  166M=0.007s
0076|2024-05-14 18:05:20 (7.45 MB/s) - 'composer-setup.php' saved [58444/58444]
0077|Begin installation of composer
0078|All settings correct for using Composer
0079|Downloading...
0080|Composer (version 2.7.6) successfully installed to: /var/www/html/core/ajax/composer.phar
0081|Use it: php composer.phar
0082|End installation of composer
0083|added 111 packages, and audited 112 packages in 2s
0084|15 packages are looking for funding
0085|run `npm fund` for details
0086|3 moderate severity vulnerabilities
0087|To address all issues, run:
0088|npm audit fix
0089|Run `npm audit` for details.
0090|+ echo 4
0091|+ sudo killall apt apt-get unattended-upgr
0092|apt: no process found
0093|apt-get: no process found
0094|unattended-upgr: no process found
0095|+ sudo rm /var/lib/apt/lists/lock
0096|+ sudo rm /var/cache/apt/archives/lock
0097|+ sudo rm /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend
0098|+ sudo sudo dpkg --configure -a --force-confdef
0099|+ sudo apt update
0100|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0101|Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
0102|Hit:2 http://http.us.debian.org/debian bullseye InRelease
0103|Hit:3 http://http.us.debian.org/debian bullseye-updates InRelease
0104|Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
0105|Reading package lists...
0106|Building dependency tree...
0107|Reading state information...
0108|14 packages can be upgraded. Run 'apt list --upgradable' to see them.
0109|+ echo 5
0110|+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
0111|+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
0112|Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
0113|Hit:2 http://http.us.debian.org/debian bullseye InRelease
0114|Hit:3 http://http.us.debian.org/debian bullseye-updates InRelease
0115|Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
0116|Reading package lists...
0117|Reading package lists...
0118|Building dependency tree...
0119|Reading state information...
0120|apt-utils is already the newest version (2.2.4).
0121|build-essential is already the newest version (12.9).
0122|git is already the newest version (1:2.30.2-1+deb11u2).
0123|lsb-release is already the newest version (11.1.0).
0124|0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
0125|[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
0126|[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
0127|+ echo 6
0128|+ sudo apt install -o Dpkg::Options::=--force-confdef -y php-yaml
0129|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0130|Reading package lists...
0131|Building dependency tree...
0132|Reading state information...
0133|php-yaml is already the newest version (2.2.1+2.1.0+2.0.4+1.3.2-2).
0134|0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
0135|+ echo 7
0136|+ sudo systemctl restart apache2
0137|+ echo 8
0138|+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
0139|+ sudo /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
0140|+ echo Launch post-install of z2m dependancy
0141|Launch post-install of z2m dependancy
0142|+ realpath /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
0143|+ dirname /var/www/html/plugins/z2m/resources/post-install.sh
0144|+ BASEDIR=/var/www/html/plugins/z2m/resources
0145|+ [ -d /var/www/html/plugins/z2m/resources/zigbee2mqtt ]
0146|+ rm -rf /var/www/html/plugins/z2m/resources/zigbee2mqtt
0147|+ mkdir /var/www/html/plugins/z2m/resources/zigbee2mqtt
0148|+ git clone --depth 1 https://github.com/Koenkk/zigbee2mqtt.git /var/www/html/plugins/z2m/resources/zigbee2mqtt
0149|Cloning into '/var/www/html/plugins/z2m/resources/zigbee2mqtt'...
0150|+ cd /var/www/html/plugins/z2m/resources/zigbee2mqtt
0151|+ [ -f /var/www/html/plugins/z2m/resources/../data/wanted_z2m_version ]
0152|+ npm ci
0153|added 795 packages, and audited 796 packages in 9s
0154|86 packages are looking for funding
0155|run `npm fund` for details
0156|found 0 vulnerabilities
0157|+ npm run build
0158|> zigbee2mqtt@1.37.1 build
0159|> tsc && node index.js writehash
0160|+ chown www-data:www-data -R /var/www/html/plugins/z2m/resources/zigbee2mqtt
0161|+ echo 9
0162|+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end z2m
0163|PHP Fatal error:  Uncaught Exception: Veuillez vérifier la configuration in /var/www/html/plugins/z2m/core/class/z2m.class.php:299
0164|Stack trace:
0165|#0 /var/www/html/plugins/z2m/core/class/z2m.class.php(37): z2m::deamon_start()
0166|#1 /var/www/html/core/php/jeecli.php(61): z2m::dependancy_end()
0167|#2 {main}
0168|thrown in /var/www/html/plugins/z2m/core/class/z2m.class.php on line 299
0169|+ echo 10
0170|+ rm /tmp/jeedom_install_in_progress_z2m
0171|+ echo '*******************End of package installation******************'
0172|*******************End of package installation******************

Contenu de Update

0000|[2024-05-14 18:05:06] ALERT  : Début de la mise à jour de : mqtt2
0001|[2024-05-14 18:05:06] ALERT  : Téléchargement du plugin (source : market)...
0002|[2024-05-14 18:05:06] ALERT  : Téléchargement de mqtt2...
0003|[2024-05-14 18:05:06] ALERT  : URL https://market.jeedom.com/core/php/downloadFile.php?id=4213&version=stable&jeedomversion=4.4.5&hwkey=aaf0a3db9e84d171f9931f662ef46f03f4957a9b&username=hbisteau&password=2095b1a69caf5618235e6509860e7dd9fbfaec6c&password_type=sha1
0004|--2024-05-14 18:05:06--  https://market.jeedom.com/core/php/downloadFile.php?id=4213&version=stable&jeedomversion=4.4.5&hwkey=aaf0a3db9e84d171f9931f662ef46f03f4957a9b&username=hbisteau&password=2095b1a69caf5618235e6509860e7dd9fbfaec6c&password_type=sha1
0005|Resolving market.jeedom.com (market.jeedom.com)... 57.128.120.126
0006|Connecting to market.jeedom.com (market.jeedom.com)|57.128.120.126|:443... connected.
0007|HTTP request sent, awaiting response... 200 OK
0008|Length: unspecified [application/octet-stream]
0009|Saving to: '/tmp/jeedom/market/mqtt2.zip'
0010|0K .......... .......... .......... .......... .......... 3.19M
0011|50K .......... .......... .......... .......... .......... 8.84M
0012|100K .......... .......... .......... .......... .......... 20.5M
0013|150K .......... .......... .......... .......... .......... 10.4M
0014|200K .......... .......... .......... .......... .......... 18.6M
0015|250K .......... .......... .......... .......... .......... 55.8M
0016|300K .......... .......... .......... .......... .......... 71.3M
0017|350K .......... .......... .......... .......... ..........  115M
0018|400K .......... .......... .......... .......... .......... 14.0M
0019|450K .......... .......... .......... .......... .......... 11.4M
0020|500K .......... .......... .......... .......... .......... 93.5M
0021|550K .......... .......... .......... .......... .......... 80.6M
0022|600K ........                                                120M=0.04s
0023|2024-05-14 18:05:06 (14.3 MB/s) - '/tmp/jeedom/market/mqtt2.zip' saved [622620]
0024|[2024-05-14 18:05:06] ALERT  : OK
0025|[2024-05-14 18:05:06] ALERT  : Décompression du zip...
0026|[2024-05-14 18:05:06] ALERT  : OK
0027|[2024-05-14 18:05:07] ALERT  : Action de pré-update...
0028|[2024-05-14 18:05:07] ALERT  : OK
0029|[2024-05-14 18:05:07] ALERT  : Post-installation de mqtt2...
0030|[2024-05-14 18:05:07] ALERT  : Vérification des droits sur les fichiers...
0031|[2024-05-14 18:05:07] ALERT  : OK
0032|[2024-05-14 18:05:07] ALERT  : Suppression des fichiers inutiles...
0033|[2024-05-14 18:05:09] ALERT  : OK
0034|[2024-05-14 18:05:09] ALERT  : END UPDATE SUCCESS
5

Bonjour,

pour info, je rencontre le meme probleme à chaque installation des dependances du plugin Zigwave Mqtt, qui reinstalle Mqtt, et donc qui change les droits du repertoire :/var/www/html/log/mqtt2

root@raspberrypi:/var/www/html/log# ll
-rw-rw-r-- 1 www-data www-data  135582 Sep  8 15:00 chauffage
-rw-rw-r-- 1 www-data www-data     122 Sep  8 03:29 cmd
-rw-rw-r-- 1 www-data www-data     888 Sep  8 09:38 connection
-rw-rw-r-- 1 www-data www-data   51186 Sep  8 15:00 conso
-rw-rw-r-- 1 www-data www-data     678 Sep  8 03:29 cron
-rw-rw-r-- 1 www-data www-data 4817464 Sep  8 15:12 cron_execution
-rw-rw-r-- 1 www-data www-data    1953 Sep  8 04:40 enedis
-rw-rw-r-- 1 www-data www-data 5950898 Sep  8 15:12 event
-rw-rw-r-- 1 www-data www-data       1 Sep  8 03:29 listener_execution
-rw-rw-r-- 1 www-data www-data   12603 Sep  8 15:00 Monitoring
-rw-r--r-- 1 root     root         540 Sep  8 14:44 mqtt2
-rw-rw-r-- 1 www-data www-data       1 Sep  8 03:29 mqtt2d
-rw-rw-r-- 1 www-data www-data       1 Sep  8 03:29 scenario_execution
drwxrwxr-x 2 www-data www-data     520 Sep  5 17:16 scenarioLog
-rw-rw-r-- 1 www-data www-data   16884 Sep  8 13:44 sonos3
-rw-rw-r-- 1 www-data www-data     138 Sep  8 05:29 speedtestByOokla
-rw-rw-r-- 1 www-data www-data 1290925 Sep  8 15:10 teleinfo
-rw-rw-r-- 1 www-data www-data    5546 Sep  8 14:44 update
-rw-rw-r-- 1 www-data www-data     263 Sep  8 14:55 z2m
-rw-rw-r-- 1 www-data www-data 1044263 Sep  8 14:44 z2md
-rw-r--r-- 1 www-data www-data    6957 Sep  8 14:55 z2m_packages
-rw-rw-r-- 1 www-data www-data    3485 Sep  8 15:01 zwavejs
-rw-rw-r-- 1 www-data www-data     938 Sep  8 03:29 zwavejsd

un simple Chown du repertoire résout le probleme, mais c’est dommage que ces droits sautent à chaque reinstall des dépendances JeeZigbee (pour maj Zigbee2MQTT)

# chown www-data:www-data mqtt2

Cdlt,

6

Tu est sur que c’est la version 4.4.5 que tu a en version jeedom

7

Bonjour,
C’est un problème dont on est bien conscient depuis plusieurs mois mais pour le moment on arrive pas a le résoudre car deja on le reproduit systématiquement et ensuite c’est un processus assez complexe les plugins en dépendances.

Pouvez vous quand le soucis survient me donner la log mqtt2 (en gros j’ai besoin de voir les dernières ligne pour savoir ce qui a passé le log en root).

8

j’ai fait une modification en alpha la 4.5 devrait corriger. Sans certitude car je suis pas sur de l’origine du soucis. Je me demande si c’est pas quand le log existe pas, que les dépendances d’un plugin type zwavejs ou jeezigbee sont relancée et que le niveau de log est info ou plus (type debug).

9

Bon ma correction marchait pas mais j’en ai trouvé une autre qui marche ca sera corrigé en 4.4.16

1 « J'aime »
10

Jeedom mis à jour, je vous tiens au courant lors de l’install des prochaines dépendances Zigbee2MQTT.