DEMON NOK avec CONBEE3

olnoishi · Mai 30, 2024, 3:12

Bonjour,

Je souhaite utiliser une CONBEE3+JeeZigbee. Mon soucis est que le demon démarre puis s’arrête quelque seconde après. En suivant le sujet ci-dessous j’ai désactivé tous mes plugin afin de voir si le port 8080 n’était pas déjà utilisé mais le problème reste le même.

Auriez-vous une idée?

Voici la config du plugin ainsi que la page Santé, ma CONBEE3 est en firmware 2.27.2 :

Sur la capture le port est 9100, je l’ai changé pour faire un essai mais c’est pareil.

vegeta0911 · Mai 30, 2024, 3:16

Bonjour

Pourquoi vous avez pas laissé le port par défaut (8080) ?
Dans les logs ça dit quoi en mode debug?

olnoishi · Mai 30, 2024, 3:18

Je l’ai laissé en 8080 mais ca ne fonctionne pas, j’ai changer le port en 9100 juste pour un essai mais le demon crash de la meme manière.

vegeta0911 · Mai 30, 2024, 3:19

Ok et pour la deuxième question ?

olnoishi · Mai 30, 2024, 3:40

Voilà ce que j’ai. Je suis novice dans le Game, j’espères ne pas me tromper, c’est bien ce que tu demande?

vegeta0911 · Mai 30, 2024, 4:47

Ok merci pour l’instant je ne voir rien spécial.
Quand tu le mets en mode debug sauvegarde et relance le démon puis redonne moi les logs
Peux-tu me montrer la liste du port du contrôleur :

olnoishi · Mai 30, 2024, 5:25

Voici la liste du port contrôleur :

Ainsi que les logs après avoir mis le mode debug, sauvegarder et redémarrer le Démon :

A chaque fois que ca redémarre, ca me créer cette erreur "Cant find module ‹ semver › " :

vegeta0911 · Mai 30, 2024, 5:52

A tu relancer les dépendances si non fait le.

olnoishi · Mai 30, 2024, 5:56

Je l’ai fait plusieurs fois sur JeeZigbee et MQTT Manager.

vegeta0911 · Mai 30, 2024, 6:20

Peut aller dans vérification des packages.
System->configuration->OS-DB

akenad · Mai 30, 2024, 6:25

Bonjour,

Un module n’est pas trouvé, c’est donc un problème d’installation des dépendances.
Fournir le log complet d’installation des dépendances (Z2m_packages),
et pas sous forme d’image mais copié collé entre balises.

akenad

olnoishi · Mai 30, 2024, 6:47

@vegeta0911 Tout les package sont « OK » dans la vérification des packages

@akenad Voici les logs :

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_z2m
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
+ sudo /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
Launch pre-install of z2m dependancy
+ echo 3
+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
apt: no process found
apt-get: no process found

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:2 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Get:5 http://archive.raspberrypi.org/debian buster/main armhf Packages [400 kB]
Fetched 501 kB in 4s (120 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
338 packages can be upgraded. Run 'apt list --upgradable' to see them.
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Get:3 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Fetched 53.9 kB in 3s (15.8 kB/s)
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).
git is already the newest version (1:2.20.1-2+deb10u8).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 338 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Fetched 53.9 kB in 3s (15.7 kB/s)
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).
git is already the newest version (1:2.20.1-2+deb10u8).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 338 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Get:3 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Fetched 53.9 kB in 4s (13.7 kB/s)
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).
git is already the newest version (1:2.20.1-2+deb10u8).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 338 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
--2024-05-30 17:13:09--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 2001:41d0:302:1100::8:104f, 54.36.53.46
Connecting to getcomposer.org (getcomposer.org)|2001:41d0:302:1100::8:104f|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58444 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'

     0K .......... .......... .......... .......... .......... 87% 2.18M 0s
    50K .......                                               100% 7.71M=0.02s

2024-05-30 17:13:10 (2.39 MB/s) - 'composer-setup.php' saved [58444/58444]

Begin installation of composer
All settings correct for using Composer
Downloading...

Composer (version 2.7.6) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar

End installation of composer
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

added 117 packages, and audited 118 packages in 18s

19 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
Synchronizing state of mosquitto.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mosquitto
+ echo 4
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: no process found
unattended-upgr: no process found
+ sudo rm /var/lib/apt/lists/lock
+ sudo rm /var/cache/apt/archives/lock
+ sudo rm /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend
+ sudo sudo dpkg --configure -a --force-confdef
+ sudo apt update

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Get:3 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Fetched 53.9 kB in 4s (14.1 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
338 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ echo 5
+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Get:3 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Fetched 53.9 kB in 3s (15.9 kB/s)
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).
git is already the newest version (1:2.20.1-2+deb10u8).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 338 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 6
+ sudo apt install -o Dpkg::Options::=--force-confdef -y php-yaml

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
php-yaml is already the newest version (2.0.2+1.3.1-4+b1).
0 upgraded, 0 newly installed, 0 to remove and 338 not upgraded.
+ echo 7
+ sudo systemctl restart apache2
+ echo 8
+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ sudo /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ echo Launch post-install of z2m dependancy
Launch post-install of z2m dependancy
+ realpath /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ dirname /var/www/html/plugins/z2m/resources/post-install.sh
+ BASEDIR=/var/www/html/plugins/z2m/resources
+ [ -d /var/www/html/plugins/z2m/resources/zigbee2mqtt ]
+ rm -rf /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ mkdir /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ git clone --depth 1 https://github.com/Koenkk/zigbee2mqtt.git /var/www/html/plugins/z2m/resources/zigbee2mqtt
Cloning into '/var/www/html/plugins/z2m/resources/zigbee2mqtt'...
+ cd /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ [ -f /var/www/html/plugins/z2m/resources/../data/wanted_z2m_version ]
+ npm ci
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! network request to https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz failed, reason: Client network socket disconnected before secure TLS connection was established
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-05-30T15_15_26_309Z-debug-0.log
+ npm run build

> zigbee2mqtt@1.37.1 build
> tsc && node index.js writehash

sh: 1: tsc: not found
+ chown www-data:www-data -R /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ echo 9
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end z2m
+ echo 10
+ rm /tmp/jeedom_install_in_progress_z2m
+ echo '*******************End of package installation******************'
*******************End of package installation******************

vegeta0911 · Mai 30, 2024, 7:15

olnoishi:

npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! network request to https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz failed, reason: Client network socket disconnected before secure TLS connection was established
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

Je pense que c’est ça qui pose problème.
Est ce que la conf réseau est bien paramètre ?

akenad · Mai 30, 2024, 7:28

Fournir ce log :

akenad

olnoishi · Mai 30, 2024, 8:39

Merci pour votre aide!

Je ne sais pas si c’est la bonne methode mais je me suis connecté en ssh sur mon jeedom, voici ce que j’ai dans le repertoire en question :

jeedom@jeedom:~ $ sudo su -
root@jeedom:~# ls
root@jeedom:~# cd /root/.npm/_logs/
root@jeedom:~/.npm/_logs# ls
2023-12-27T07_26_11_385Z-debug-0.log  2024-04-22T05_30_47_521Z-debug-0.log
2023-12-27T07_26_20_933Z-debug-0.log  2024-04-22T05_33_14_610Z-debug-0.log
2023-12-27T07_26_27_752Z-debug-0.log  2024-04-22T05_33_22_158Z-debug-0.log
2023-12-27T07_27_15_971Z-debug-0.log  2024-04-22T05_33_51_016Z-debug-0.log
2024-04-22T05_29_30_018Z-debug-0.log  2024-05-30T20_35_16_246Z-debug-0.log
2024-04-22T05_29_36_976Z-debug-0.log
root@jeedom:~/.npm/_logs#

Étonnamment je ne vois pas le fichier log en question.

olnoishi · Mai 30, 2024, 9:02

J’ai reinstallé les dependances du coup. Il me dit qu’un fichier log finissant par 525Z a été généré mais idem, pas de 525Z en vue.

0159|npm ERR! code ECONNRESET
0160|npm ERR! network Client network socket disconnected before secure TLS connection was established
0161|npm ERR! network This is a problem related to network connectivity.
0162|npm ERR! network In most cases you are behind a proxy or have bad network settings.
0163|npm ERR! network
0164|npm ERR! network If you are behind a proxy, please make sure that the
0165|npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
0166|npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-05-30T20_53_34_525Z-debug-0.log

root@jeedom:~/.npm/_logs# ls
2023-12-27T07_26_11_385Z-debug-0.log  2024-04-22T05_29_30_018Z-debug-0.log  2024-04-22T05_33_22_158Z-debug-0.log
2023-12-27T07_26_20_933Z-debug-0.log  2024-04-22T05_29_36_976Z-debug-0.log  2024-04-22T05_33_51_016Z-debug-0.log
2023-12-27T07_26_27_752Z-debug-0.log  2024-04-22T05_30_47_521Z-debug-0.log  2024-05-30T20_57_40_931Z-debug-0.log
2023-12-27T07_27_15_971Z-debug-0.log  2024-04-22T05_33_14_610Z-debug-0.log  2024-05-30T20_57_50_297Z-debug-0.log

akenad · Mai 30, 2024, 9:47

Fournir le log :

akenad

olnoishi · Mai 31, 2024, 5:47

Ce matin il n’y avait plus le 297Z

root@jeedom:~/.npm/_logs# ls
2023-12-27T07_26_11_385Z-debug-0.log  2024-04-22T05_29_30_018Z-debug-0.log  2024-04-22T05_33_22_158Z-debug-0.log
2023-12-27T07_26_20_933Z-debug-0.log  2024-04-22T05_29_36_976Z-debug-0.log  2024-04-22T05_33_51_016Z-debug-0.log
2023-12-27T07_26_27_752Z-debug-0.log  2024-04-22T05_30_47_521Z-debug-0.log  2024-05-31T04_40_25_625Z-debug-0.log
2023-12-27T07_27_15_971Z-debug-0.log  2024-04-22T05_33_14_610Z-debug-0.log

J’ai donc affiché le derniers en date que voici :

root@jeedom:~/.npm/_logs# cat 2024-05-31T04_40_25_625Z-debug-0.log
0 verbose cli /usr/bin/node /usr/bin/npm
1 info using npm@10.2.3
2 info using node@v18.19.0
3 timing npm:load:whichnode Completed in 15ms
4 timing config:load:defaults Completed in 30ms
5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 4ms
6 timing config:load:builtin Completed in 7ms
7 timing config:load:cli Completed in 33ms
8 timing config:load:env Completed in 11ms
9 timing config:load:file:/var/www/html/plugins/z2m/resources/zigbee2mqtt/.npmrc Completed in 20ms
10 timing config:load:project Completed in 32ms
11 timing config:load:file:/root/.npmrc Completed in 7ms
12 timing config:load:user Completed in 8ms
13 timing config:load:file:/var/www/html/plugins/z2m/resources/zigbee2mqtt/etc/npmrc Completed in 1ms
14 timing config:load:global Completed in 3ms
15 timing config:load:setEnvs Completed in 13ms
16 timing config:load Completed in 147ms
17 timing npm:load:configload Completed in 149ms
18 timing config:load:flatten Completed in 45ms
19 timing npm:load:mkdirpcache Completed in 24ms
20 timing npm:load:mkdirplogs Completed in 4ms
21 verbose title npm run build
22 verbose argv "run" "build"
23 timing npm:load:setTitle Completed in 25ms
24 timing npm:load:display Completed in 11ms
25 verbose logfile logs-max:10 dir:/root/.npm/_logs/2024-05-31T04_40_25_625Z-
26 verbose logfile /root/.npm/_logs/2024-05-31T04_40_25_625Z-debug-0.log
27 timing npm:load:logFile Completed in 119ms
28 timing npm:load:timers Completed in 1ms
29 timing npm:load:configScope Completed in 1ms
30 timing npm:load Completed in 612ms
31 silly logfile start cleaning logs, removing 1 files
32 silly logfile done cleaning log files
33 timing command:run Completed in 223ms
34 verbose exit 127
35 timing npm Completed in 1618ms
36 verbose code 127

J’ai ensuite réinstallé les dependances afin de voir le fichier generé et j’ai eu cette erreur juste avant que les ligne nmp ERR apparaissent :

Voici le dernier fichier juste après réinstallation des dépendances :

root@jeedom:~/.npm/_logs# cat 2024-05-31T05_45_16_760Z-debug-0.log
0 verbose cli /usr/bin/node /usr/bin/npm
1 info using npm@10.2.3
2 info using node@v18.19.0
3 timing npm:load:whichnode Completed in 14ms
4 timing config:load:defaults Completed in 29ms
5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 5ms
6 timing config:load:builtin Completed in 10ms
7 timing config:load:cli Completed in 44ms
8 timing config:load:env Completed in 3ms
9 timing config:load:file:/var/www/html/plugins/z2m/resources/zigbee2mqtt/.npmrc Completed in 18ms
10 timing config:load:project Completed in 25ms
11 timing config:load:file:/root/.npmrc Completed in 5ms
12 timing config:load:user Completed in 8ms
13 timing config:load:file:/var/www/html/plugins/z2m/resources/zigbee2mqtt/etc/npmrc Completed in 2ms
14 timing config:load:global Completed in 3ms
15 timing config:load:setEnvs Completed in 14ms
16 timing config:load Completed in 148ms
17 timing npm:load:configload Completed in 150ms
18 timing config:load:flatten Completed in 44ms
19 timing npm:load:mkdirpcache Completed in 16ms
20 timing npm:load:mkdirplogs Completed in 20ms
21 verbose title npm start
22 verbose argv "start" "--prefix" "/var/www/html/plugins/z2m/resources/zigbee2mqtt"
23 timing npm:load:setTitle Completed in 17ms
24 timing npm:load:display Completed in 12ms
25 verbose logfile logs-max:10 dir:/root/.npm/_logs/2024-05-31T05_45_16_760Z-
26 verbose logfile /root/.npm/_logs/2024-05-31T05_45_16_760Z-debug-0.log
27 timing npm:load:logFile Completed in 136ms
28 timing npm:load:timers Completed in 1ms
29 timing npm:load:configScope Completed in 1ms
30 timing npm:load Completed in 641ms
31 silly logfile start cleaning logs, removing 1 files
32 silly logfile done cleaning log files
33 timing command:run-script Completed in 1088ms
34 timing command:start Completed in 1186ms
35 verbose exit 1
36 timing npm Completed in 2518ms
37 verbose code 1

akenad · Mai 31, 2024, 2:39

Page configuration réseau ?

akenad

olnoishi · Mai 31, 2024, 3:18

Voici :