Dépendances KO suite à maj des dépendances

Plugins Protocole domotique
1

Hello tout le monde. Ne hurlez pas :wink: le matos est vieux.
Je suis sur un rpi2B sous buster en version 4.4 de Jeedom.
J’avais réussi après bien des difficultés à installer zwaveJS voici quelques mois. C’était fonctionnel, j’avais synchro quelques équipements zwave. En reprenant le chantier pour finir la migration, j’ai vu une invite à mettre à jour zwaveJS UI, naïvement j’ai relancé l’installation des dépendances et… échec. A présent je ne peux meme plus lancer le démon du plugin :sweat_smile:
Voici le log de l’install des dépendances.
zwavejs_packages.txt (15,2 Ko)

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_zwavejs
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
+ echo 'Pre installation de l'\''installation/mise à jour des dépendances zwavejs'
Pre installation de l'installation/mise à jour des dépendances zwavejs
+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
++ pwd
+ BASEDIR=/var/www/html/plugins/zwavejs/resources
+ cd /var/www/html/plugins/zwavejs/resources
+ source ../core/config/zwavejs.config.ini
+ echo 'Wanted Version: 9.12.0'
Wanted Version: 9.12.0
+ rm -R zwave-js-ui
+ git clone --branch v9.12.0 --depth 1 https://github.com/zwave-js/zwave-js-ui
Cloning into 'zwave-js-ui'...
Note: checking out '96eeb76b110f27d3ce16cfb4b3992cb8f8dc34d8'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

Checking out files:  40% (108/265)   
Checking out files:  41% (109/265)   
Checking out files:  42% (112/265)   
Checking out files:  43% (114/265)   
Checking out files:  44% (117/265)   
Checking out files:  45% (120/265)   
Checking out files:  46% (122/265)   
Checking out files:  47% (125/265)   
Checking out files:  48% (128/265)   
Checking out files:  49% (130/265)   
Checking out files:  50% (133/265)   
Checking out files:  51% (136/265)   
Checking out files:  52% (138/265)   
Checking out files:  53% (141/265)   
Checking out files:  54% (144/265)   
Checking out files:  55% (146/265)   
Checking out files:  56% (149/265)   
Checking out files:  57% (152/265)   
Checking out files:  58% (154/265)   
Checking out files:  59% (157/265)   
Checking out files:  60% (159/265)   
Checking out files:  61% (162/265)   
Checking out files:  62% (165/265)   
Checking out files:  63% (167/265)   
Checking out files:  64% (170/265)   
Checking out files:  65% (173/265)   
Checking out files:  66% (175/265)   
Checking out files:  67% (178/265)   
Checking out files:  68% (181/265)   
Checking out files:  69% (183/265)   
Checking out files:  70% (186/265)   
Checking out files:  71% (189/265)   
Checking out files:  72% (191/265)   
Checking out files:  73% (194/265)   
Checking out files:  74% (197/265)   
Checking out files:  75% (199/265)   
Checking out files:  76% (202/265)   
Checking out files:  77% (205/265)   
Checking out files:  78% (207/265)   
Checking out files:  79% (210/265)   
Checking out files:  80% (212/265)   
Checking out files:  81% (215/265)   
Checking out files:  82% (218/265)   
Checking out files:  83% (220/265)   
Checking out files:  84% (223/265)   
Checking out files:  85% (226/265)   
Checking out files:  86% (228/265)   
Checking out files:  87% (231/265)   
Checking out files:  88% (234/265)   
Checking out files:  89% (236/265)   
Checking out files:  90% (239/265)   
Checking out files:  91% (242/265)   
Checking out files:  92% (244/265)   
Checking out files:  93% (247/265)   
Checking out files:  94% (250/265)   
Checking out files:  95% (252/265)   
Checking out files:  96% (255/265)   
Checking out files:  97% (258/265)   
Checking out files:  98% (260/265)   
Checking out files:  99% (263/265)   
Checking out files: 100% (265/265)   
Checking out files: 100% (265/265), done.
+ echo 'Pre install finished'
Pre install finished
+ echo 3
+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
PHP Fatal error:  Uncaught Exception: Code : 0<br/>Message : Vous avez un trop grand nombre de systeme jeedom déclaré ou plus de 2 ips externe differentes pour vos jeedoms, veuillez en réduire le nombre en allant sur votre page profils du market et en supprimant des jeedoms, n'oubliez pas de sauvegarder in /var/www/html/core/repo/market.repo.php:836
Stack trace:
#0 /var/www/html/core/repo/market.repo.php(193): repo_market::byLogicalIdAndType('mqtt2', 'plugin')
#1 /var/www/html/core/class/update.class.php(305): repo_market::downloadObject(Object(update))
#2 /var/www/html/core/php/jeecli.php(47): update->doUpdate()
#3 {main}
  thrown in /var/www/html/core/repo/market.repo.php on line 836
+ echo 4
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: 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
Hit:3 https://deb.nodesource.com/node_18.x buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:5 https://repo.z-wave.me/z-way/raspbian buster InRelease
Fetched 53.9 kB in 19s (2840 B/s)
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
+ 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
Hit:3 https://repo.z-wave.me/z-way/raspbian buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:5 https://deb.nodesource.com/node_18.x buster InRelease
Fetched 53.9 kB in 9s (5929 B/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+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 6
+ 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 buster InRelease
Hit:5 https://repo.z-wave.me/z-way/raspbian buster InRelease
Fetched 53.9 kB in 6s (9449 B/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+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 7
+ 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://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://repo.z-wave.me/z-way/raspbian buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:5 https://deb.nodesource.com/node_18.x buster InRelease
Fetched 53.9 kB in 9s (6036 B/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+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 8
+ sudo chmod +x /var/www/html/core/class/../../resources/install_composer.sh
+ sudo /var/www/html/core/class/../../resources/install_composer.sh
Begin installation of composer
--2024-08-25 17:07:47--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 54.36.53.46, 2001:41d0:302:1100::8:104f
Connecting to getcomposer.org (getcomposer.org)|54.36.53.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58444 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'

     0K .......... .......... .......... .......... .......... 87% 2.10M 0s
    50K .......                                               100% 6.78M=0.02s

2024-08-25 17:07:48 (2.30 MB/s) - 'composer-setup.php' saved [58444/58444]

All settings correct for using Composer
Downloading...

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

End installation of composer
+ echo 9
+ sudo NODE_OPTIONS=--dns-result-order=ipv4first npm install --force -g yarn
npm WARN using --force Recommended protections disabled.

changed 1 package in 25s
+ echo 10
+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
+ echo 'Post installation de l'\''installation/mise à jour des dépendances zwavejs'
Post installation de l'installation/mise à jour des dépendances zwavejs
+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
++ pwd
+ BASEDIR=/var/www/html/plugins/zwavejs/resources
+ cd /var/www/html/plugins/zwavejs/resources
+ cd zwave-js-ui
+ sudo yarn install
yarn install v1.22.22
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/5] Validating package.json...
[2/5] Resolving packages...
warning archiver > archiver-utils > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning archiver > archiver-utils > glob > 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.
warning csurf@1.11.0: Please use another csrf package
warning native-url > querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning vue@2.7.16: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
warning @types/extract-zip@2.0.1: This is a stub types definition. extract-zip provides its own type definitions, so you do not need this installed.
warning c8 > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning c8 > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning c8 > rimraf > glob > 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.
warning c8 > test-exclude > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning docsify-cli > docsify-server-renderer@4.13.1: docsify-server-renderer 4.x and below is no longer supported while we investigate the future of SSR and SSG for Docsify
warning eslint > @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning mocha > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning release-it > shelljs > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning vite-plugin-pwa > workbox-build > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning vite-plugin-pwa > workbox-build > @rollup/plugin-replace > magic-string > sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
[3/5] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error Error: https://registry.yarnpkg.com/moment/-/moment-2.30.1.tgz: ESOCKETTIMEDOUT
    at ClientRequest.<anonymous> (/usr/lib/node_modules/yarn/lib/cli.js:142037:19)
    at Object.onceWrapper (node:events:628:28)
    at ClientRequest.emit (node:events:514:28)
    at TLSSocket.emitRequestTimeout (node:_http_client:847:9)
    at Object.onceWrapper (node:events:628:28)
    at TLSSocket.emit (node:events:526:35)
    at Socket._onTimeout (node:net:571:8)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...

Impossible d’afficher la page santé, ça fait planter jeedom, on dirait qu’il tire la langue ^^
Concernant le socket timeout j’ai vu sur le github du projet qu’il ne s’agissait probablement pas d’un souci réseau mais vraisemblablement d’un souci I/O lié à la lenteur du disque (dans mon cas une carte micro sd).

2

Bonjour,

As-tu vu çà dans ton log ?

Message : Vous avez un trop grand nombre de systeme jeedom déclaré ou plus de 2 ips externe differentes pour vos jeedoms, veuillez en réduire le nombre en allant sur votre page profils du market et en supprimant des jeedoms, n’oubliez pas de sauvegarder in /var/www/html/core/repo/market.repo.php:836

3

hello oui, c’est résolu, j’avais monté un jeedom de test en plus pour faire la migration sur un nouveau matériel et en profiter pour faire le switch d’open zwave vers zwaveJS , j’ignorais qu’il y avait une limitation sur le nombre d’installation jeedom. ça ne change en rien le souci, je l’avais déjà.

4

Pas d’autre idée de mon côté…

5

Bonjour,

Sans la page santé de Jeedom et sans log copié entre balises vous avez peu de chance d’avoir de l’aide.

Moi le premier je vais pas chercher à voir vos logs.

Je veux bien aider mais à condition que la personne qui en fait la demande respecte à minima les règles d’une communauté bénévole qui prend sur son temps pour aider.

Je comprends la frustration d’être bloqué, mais cela ne doit pas déboucher sur une foire à la saucisse.

Chaque souci doit être détaillé afin de permettre a la communauté de gonfler la base de connaissance sur un souci une solution en fonction d’un cadre.

Luis

6

Pas de souci, j’'ai modifié le post initial pour inclure le contenu du fichier qui était en pièce jointe. En revanche, comme je l’ai déjà indiqué, malheureusement je n’ai pas la possibilité d’afficher la page santé, elle fait planter jeedom. Je le précise car je savais que c’est réclamé, et je ne peux pas… Je ne vais pas l’inventer.

7

Mais nous donner la version de Jeedom, la machine, la version de linux cela doit rester du possible ?

8

Vu le message le souci n’est pas jeedom.

9

Curieusement la réinstallation ne donne pas le même résultat

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_zwavejs
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
+ echo 'Pre installation de l'\''installation/mise à jour des dépendances zwavejs'
Pre installation de l'installation/mise à jour des dépendances zwavejs
+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
++ pwd
+ BASEDIR=/var/www/html/plugins/zwavejs/resources
+ cd /var/www/html/plugins/zwavejs/resources
+ source ../core/config/zwavejs.config.ini
+ echo 'Wanted Version: 9.12.0'
Wanted Version: 9.12.0
+ rm -R zwave-js-ui
+ git clone --branch v9.12.0 --depth 1 https://github.com/zwave-js/zwave-js-ui
Cloning into 'zwave-js-ui'...
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
+ echo 'Pre install finished'
Pre install finished
+ echo 3
+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
+ 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
Get:2 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:3 https://deb.nodesource.com/node_18.x buster InRelease
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Hit:5 https://repo.z-wave.me/z-way/raspbian buster InRelease
Fetched 53.9 kB in 7s (7928 B/s)
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
+ 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://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://repo.z-wave.me/z-way/raspbian buster InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Get:5 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Fetched 53.9 kB in 9s (5988 B/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+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 6
+ 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
Hit:3 https://repo.z-wave.me/z-way/raspbian buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:5 https://deb.nodesource.com/node_18.x buster InRelease
Fetched 53.9 kB in 7s (8038 B/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+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 7
+ 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://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://repo.z-wave.me/z-way/raspbian buster InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Get:5 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Fetched 53.9 kB in 6s (9683 B/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+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 8
+ sudo chmod +x /var/www/html/core/class/../../resources/install_composer.sh
+ sudo /var/www/html/core/class/../../resources/install_composer.sh
Begin installation of composer
--2024-08-25 20:24:27--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 54.36.53.46, 2001:41d0:302:1100::8:104f
Connecting to getcomposer.org (getcomposer.org)|54.36.53.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58444 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'
0K .......... .......... .......... .......... .......... 87% 2.34M 0s
50K .......                                               100% 11.9M=0.02s
2024-08-25 20:24:27 (2.60 MB/s) - 'composer-setup.php' saved [58444/58444]
All settings correct for using Composer
Downloading...
Composer (version 2.7.8) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar
End installation of composer
+ echo 9
+ sudo NODE_OPTIONS=--dns-result-order=ipv4first npm install --force -g yarn
npm WARN using --force Recommended protections disabled.
changed 1 package in 19s
+ echo 10
+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
+ echo 'Post installation de l'\''installation/mise à jour des dépendances zwavejs'
Post installation de l'installation/mise à jour des dépendances zwavejs
+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
++ pwd
+ BASEDIR=/var/www/html/plugins/zwavejs/resources
+ cd /var/www/html/plugins/zwavejs/resources
+ cd zwave-js-ui
/var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh: line 9: cd: zwave-js-ui: No such file or directory
+ sudo yarn install
yarn install v1.22.22
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.54s.
+ sudo NODE_OPTIONS=--max_old_space_size=2048
usage: sudo -h | -K | -k | -V
usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
[command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
prompt] [-T timeout] [-u user] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
prompt] [-T timeout] [-u user] file ...
+ sudo yarn run build
yarn run v1.22.22
error Couldn't find a package.json file in "/var/www/html/plugins/zwavejs/resources"
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
+ chown -R www-data:www-data node_modules post_install.sh pre_install.sh rename_files.py transform_command.py yarn.lock
+ '[' -e /dev/ttyAMA0 ']'
+ sudo sed -i 's/console=ttyAMA0,115200//; s/kgdboc=ttyAMA0,115200//' /boot/cmdline.txt
+ sudo sed -i 's|[^:]*:[^:]*:respawn:/sbin/getty[^:]*ttyAMA0[^:]*||' /etc/inittab
sed: can't read /etc/inittab: No such file or directory
+ '[' -e /dev/ttymxc0 ']'
+ '[' -e /dev/ttyAMA0 ']'
+ sudo systemctl mask serial-getty@ttyAMA0.service
+ sudo systemctl stop serial-getty@ttyAMA0.service
++ cut -d: -f2
++ tr -d ' '
++ grep Revision /proc/cpuinfo
+ RPI_BOARD_REVISION=a01041
+ [[ a01041 == \a\0\2\0\8\2 ]]
+ [[ a01041 == \a\2\2\0\8\2 ]]
+ [[ a01041 == \a\0\2\0\d\3 ]]
+ echo 'Everything is successfully installed!'
Everything is successfully installed!
+ echo 11
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end zwavejs
+ echo 12
+ rm /tmp/jeedom_install_in_progress_zwavejs
+ echo '*******************End of package installation******************'
*******************End of package installation******************
10

Déjà dans le premier post. Mes excuses je n’ai pas précisé que je suis en 4.4, la dernière version de jeedom.

11

Tout cela sur un raspi has been.

Ou la carte Sd part en sucette ou l’OS est bon pour être réinstallé

12

C’était pour prévenir de ce type de message que j’ai commencé mon post par « Ne hurlez pas », je voulais éviter ce type de message pas très constructif. Je vous présente mes excuses de ne pas avoir pris le temps de réinstaller le système sur un raspi récent vec un ssd. Mon métier ne me laisse pas forcément beaucoup de temps pour tout cela.
Le systeme fonctionne bien en dehors de ça aujourd’hui :slight_smile:
Bon a priori je comprends que c’est un souci sur la librairie téléchargée qui ne contient pas tous les fichiers ?

13

je pense surtout a un système qui part en sucette sur une carte sd qui lache

14

Bigre, voilà qui ne m’arrange pas. Je vais essayer de changer de carte sd et de restaurer un backup en ce cas, merci pour le diagnostic.

15

j’ai flashé une nouvelle carte sd avec jeedom, je tenterai un restore du backup demain ou après demain. Dans le même laps de temps j’ai tenté de modifier le fichier post_install :
sudo nano /var/www/html/plugins/zwavejs/resources/post_install.sh
sur un billet de blog j’ai vu que quelqu’un avait grandement permis le timeout, donc j’ai tenté - ne sachant trop quel était le nom du module - avec zwavejs et zwave-js-ui, et de grossir le NODE_OPTIONS (j’ai perdu le lien où je l’ai vu, de mémoire c’était sur community.jeedom.com) :

sudo yarn add zwavejs --network-timeout 300000
sudo yarn add zwave-js-ui --network-timeout 300000
sudo yarn install
sudo NODE_OPTIONS="--max_old_space_size=2048"

curieusement, j’ai encore un autre résultat sur les dépendances, qui s’installent lentement… mais qui progressent. step 4/5 à l’heure où j’écris ces lignes. Je vous partagerai le log demain… Bonne soirée et merci à ceux qui m’ont aidé.

16

le NODE_OPTIONS=« –max_old_space_size=2048 » fonctionne sur un RPI3, cf dependances-js-heap-out-of-memory-raspberry-pi-3
Par contre les erreurs dans votre log n’ont pas l’air de concerner un problème de manque de mémoire, mais plutôt des erreurs au niveau filesystem ? carte ssd ?

17

oui je tentais en parallèle du changement de carte sd autre chose (modification des options de l’installation des dépendances), mais j’ai préparé une autre carte sd, je fais ça ce soir. A ton avis, je fais un restore du backup sur la nouvelle carte avec un fresh jeedom dessus ou je clone directement la carte sd actuelle ?

18

On repart de 0, on ne clone pas une source qui n’est pas sûre.

1 « J'aime »
19

Je crois que vous aviez tous raison. J’ai réimporté un backup de la veille sur une fresh install de jeedom sur un raspi3 que j’avais de dispo, après avoir augmenté la swap de 100 Mo à 1 Go + la customization du

Et évidemment, avec une carte sd toute neuve (sinon je crois que @lperenna m’arrachait les yeux :wink: )
les dépendances se sont installées, tout est à OK.
A priori j’ai un « fail to initialize the driver » à résoudre à présent mais c’est de l’ordre du driver, pas de la librairie, j’ai pu aller sur la page de ZwaveJS UI. un grand merci à vous tous !
EDIT : fausse alerte, ce n’était pas le bon controleur de sélectionné dans la liste déroulante, la faute au backup de jeedom (sur la source, c’était le razberry sur les ports GPIO)

1 « J'aime »
20

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.