Dependance zwavejs KO suite passage d'un emc 8g à 16g sur smart

Bonjour,

Suite au remplacement de ma memoir 8g par une 16g sur ma smart, j’ai reinstallé la sauvegarde et ca c’est bien passé.
Par contre les dependance de 15 plugin etaient KO.
J’ai fait*s un « apt-get update --allow-releaseinfo-change » et ca a resolut la situiation sur 13 plugin.
Par contre pour ZWAVEJS je n’y arrive pas.

Je suis sur SMART en 4.3.17

Dernier version du ZWAVE

Les log des dependance de ZWAVEJS :

+ 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: 8.13.1'
Wanted Version: 8.13.1
+ rm -R zwave-js-ui
+ git clone --branch v8.13.1 --depth 1 https://github.com/zwave-js/zwave-js-ui
Cloning into 'zwave-js-ui'...
Note: checking out '33a6f577acfcadab71121712914e87008395b53b'.
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 
+ echo 'Pre install finished'
Pre install finished
+ echo 3
+ 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
internal/modules/cjs/loader.js:638
throw err;
^
Error: Cannot find module 'worker_threads'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at /var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:428:2642
at Object. (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:741:8846)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
+ sudo yarn run build
internal/modules/cjs/loader.js:638
throw err;
^
Error: Cannot find module 'worker_threads'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at /var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:428:2642
at Object. (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:741:8846)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
+ chown -R www-data:www-data CHANGELOG.md LICENSE README.md SECURITY.md app.ts bin build config docker docs genereteDocs.ts hass kubernetes kustomization.yaml lib nodemon.json package.json package.sh pkg snippets src static store test tsconfig.eslint.json tsconfig.json views wallaby.js yarn.lock
+ '[' -e /dev/ttyAMA0 ']'
+ '[' -e /dev/ttymxc0 ']'
+ '[' -e /dev/ttyAMA0 ']'
++ grep Revision /proc/cpuinfo
++ tr -d ' '
++ cut -d: -f2
+ RPI_BOARD_REVISION=020c
+ [[ 020c == a\8 ]]
+ [[ 020c == a\8 ]]
+ [[ 020c == a\d ]]
+ echo 'Everything is successfully installed!'
Everything is successfully installed!
+ echo 4
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end zwavejs
+ rm /tmp/jeedom_install_in_progress_zwavejs
+ echo '*******************End of package installation******************'
*******************End of package installation******************

J’utilise MQTT manager avec un mosquito distant ( jmqtt)


et les log des dependances:

Setting up node-brace-expansion (1.1.8-1) ...
Setting up node-is-object (1.0.1-1) ...
Setting up node-is-stream (1.1.0-1) ...
Setting up node-deep-extend (0.4.1-2) ...
Setting up node-p-finally (1.0.0-2) ...
Setting up node-get-stream (3.0.0-1) ...
Setting up node-strip-ansi (4.0.0-1) ...
Setting up node-set-blocking (2.0.0-1) ...
Setting up node-prr (1.0.1-1) ...
Setting up node-tunnel-agent (0.6.1-1) ...
Setting up node-uid-number (0.0.6-1) ...
Setting up node-signal-exit (3.0.2-1) ...
Setting up node-spdx-expression-parse (1.0.4-1) ...
Setting up node-cyclist (1.0.1-2) ...
Setting up node-which (1.3.0-2) ...
Setting up node-lcid (1.0.0-1) ...
Setting up node-wrappy (1.0.2-1) ...
Setting up node-text-table (0.2.0-2) ...
Setting up node-asynckit (0.4.0-2) ...
Setting up node-proto-list (1.2.4-1) ...
Setting up node-require-directory (2.1.1-1) ...
Setting up node-punycode (2.1.1-2) ...
Setting up node-concat-stream (1.6.2-1) ...
Setting up node-defaults (1.0.3-1) ...
Setting up node-mute-stream (0.0.8-1) ...
Setting up node-mimic-response (1.0.0-1) ...
Setting up node-duplexer3 (0.1.4-4) ...
Setting up node-stream-iterate (1.2.0-4) ...
Setting up node-graceful-fs (4.1.11-1) ...
Setting up node-node-uuid (3.3.2-2) ...
Setting up node-jsonify (0.0.0-1) ...
Setting up node-json-stable-stringify (1.0.1-1) ...
Setting up node-hosted-git-info (2.7.1-1+deb10u1) ...
Setting up node-aproba (1.2.0-1) ...
Setting up node-tough-cookie (2.3.4+dfsg-1) ...
Setting up node-mimic-fn (1.1.0-1) ...
Setting up node-rc (1.1.6-2) ...
Setting up node-spdx-license-ids (1.2.2-1) ...
Setting up node-string-decoder (1.2.0-1) ...
Setting up node-mkdirp (0.5.1-1) ...
Setting up node-run-queue (1.0.3-1) ...
Setting up node-call-limit (1.1.0-1) ...
Setting up node-core-util-is (1.0.2-1) ...
Setting up node-json-schema (0.2.3-1+deb10u1) ...
Setting up node-minimatch (3.0.4-3+deb10u1) ...
Setting up node-is-builtin-module (2.0.0-1) ...
Setting up node-cli-boxes (1.0.0-1) ...
Setting up node-opener (1.4.3-1) ...
Setting up node-archy (1.0.0-2) ...
Setting up node-caseless (0.12.0-1) ...
Setting up node-imurmurhash (0.1.4-1) ...
Setting up node-xtend (4.0.1-2) ...
Setting up node-p-timeout (1.2.0-1) ...
Setting up node-verror (1.10.0-1) ...
Setting up node-getpass (0.1.7-1) ...
Setting up node-encoding (0.1.12-2) ...
Setting up node-config-chain (1.1.11-1) ...
Setting up node-read (1.0.7-1) ...
Setting up node-detect-indent (5.0.0-1) ...
Setting up node-nopt (3.0.6-3) ...
Setting up node-npm-run-path (2.0.2-2) ...
Setting up node-asn1 (0.2.3-1) ...
Setting up node-has-symbol-support-x (1.4.1+dfsg-1) ...
Setting up node-sorted-object (2.0.1-1) ...
Setting up node-color-convert (1.9.0-3) ...
Setting up node-isarray (2.0.4-1) ...
Setting up node-osenv (0.1.5-1) ...
Setting up node-is-plain-obj (1.1.0-1) ...
Setting up node-shebang-command (1.2.0-1) ...
Setting up libjs-is-typedarray (1.0.0-2) ...
Setting up node-lowercase-keys (1.0.0-2) ...
Setting up node-decompress-response (3.3.0-1) ...
Setting up node-strip-eof (1.0.0-2) ...
Setting up node-process-nextick-args (2.0.0-1) ...
Setting up node-semver (5.5.1-1) ...
Setting up node-has-unicode (2.0.1-2) ...
Setting up node-fs-write-stream-atomic (1.0.10-4) ...
Setting up gyp (0.1+20180428git4d467626-3) ...
Setting up node-readable-stream (2.3.6-1) ...
Setting up node-ssri (5.2.4-2) ...
Setting up node-through2 (2.0.5-2) ...
Setting up node-lru-cache (5.1.1-4) ...
Setting up node-bcrypt-pbkdf (1.0.1-1) ...
Setting up node-mem (1.1.0-1) ...
Setting up node-supports-color (4.4.0-2) ...
Setting up node-once (1.4.0-3) ...
Setting up node-write-file-atomic (2.3.0-1) ...
Setting up node-jsprim (1.4.0-1) ...
Setting up node-sha (2.0.1-1) ...
Setting up node-url-parse-lax (1.0.0-1) ...
Setting up node-flush-write-stream (1.0.3-1) ...
Setting up node-ajv (5.0.0-1) ...
Setting up node-errno (0.1.4-1) ...
Setting up node-find-up (2.1.0-1) ...
Setting up node-semver-diff (2.1.0-2) ...
Setting up node-from2 (2.3.0-1) ...
Setting up node-promzard (0.3.0-1) ...
Setting up node-wcwidth.js (1.0.0-1) ...
Setting up node-spdx-correct (1.0.2-1) ...
Setting up node-unique-filename (1.1.0+ds-2) ...
Setting up node-cross-spawn (5.1.0-2) ...
Setting up node-ansi-styles (3.2.1-1) ...
Setting up node-form-data (2.3.2-2) ...
Setting up node-lockfile (1.0.4-1) ...
Setting up node-chalk (2.3.0-2) ...
Setting up node-parallel-transform (1.1.0-2) ...
Setting up node-registry-url (3.1.0-1) ...
Setting up node-is-typedarray (1.0.0-2) ...
Setting up node-registry-auth-token (3.3.1-1) ...
Setting up node-tar (4.4.6+ds1-3+deb10u2) ...
Setting up node-inflight (1.0.6-1) ...
Setting up node-has-to-string-tag-x (1.4.1+dfsg-1) ...
Setting up node-npm-package-arg (6.0.0-2) ...
Setting up node-isurl (1.0.0-1) ...
Setting up node-string-width (2.1.1-1) ...
Setting up node-sshpk (1.13.1+dfsg-2) ...
Setting up node-har-validator (5.1.0-1) ...
Setting up node-validate-npm-package-license (3.0.1-1) ...
Setting up node-end-of-stream (1.4.1-1+deb10u1) ...
Setting up node-execa (0.10.0+dfsg-1) ...
Setting up node-pump (3.0.0-1) ...
Setting up node-term-size (1.2.0+dfsg-2) ...
Setting up node-os-locale (2.0.0-1) ...
Setting up node-http-signature (1.2.0-1) ...
Setting up node-duplexify (3.6.1-1) ...
Setting up node-wrap-ansi (4.0.0-1) ...
Setting up node-normalize-package-data (2.4.0-1) ...
Setting up node-glob (7.1.3-2) ...
Setting up node-pumpify (1.5.1-1) ...
Setting up node-widest-line (1.2.2-1) ...
Setting up node-got (7.1.0-1) ...
Setting up node-package-json (4.0.1-1) ...
Setting up node-latest-version (3.1.0-1) ...
Setting up node-wide-align (1.1.0-1) ...
Setting up node-ansi-align (2.0.0-1) ...
Setting up node-request (2.88.1-2) ...
Setting up node-cliui (4.1.0-1) ...
Setting up node-rimraf (2.6.2-1) ...
Setting up node-stream-each (1.2.2-2) ...
Setting up node-yargs (10.0.3-2) ...
Setting up node-mississippi (3.0.0-1) ...
Setting up node-read-package-json (2.0.13-1) ...
Setting up node-copy-concurrently (1.0.5-4) ...
Setting up node-move-concurrently (1.0.1-2) ...
Setting up node-fs-vacuum (1.2.10-2) ...
Setting up node-gauge (2.7.4-1) ...
Setting up node-boxen (1.2.2-1) ...
Setting up node-libnpx (10.2.0+repack-1) ...
Setting up node-npmlog (4.1.2-1) ...
Setting up node-cacache (11.3.2-2) ...
Setting up node-gyp (3.8.0-6) ...
Setting up npm (5.8.0+ds6-4+deb10u2) ...
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
npm WARN npm@9.6.7 had bundled packages that do not match the required version(s). They have been replaced with non-bundled versions.
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "npm:": npm:string-width@^4.2.0
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-05-21T09_28_43_478Z-debug.log
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
[Check Prefix : /usr/local and sudo prefix : /usr/local and www-data prefix : /usr/local : [  OK  ]
+ echo 4
+ cd /var/www/html/core/class/../../plugins/mqtt2/resources/mqtt2d
+ rm -rf node_modules
+ sudo npm install
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
npm WARN mqtt2@1.0.0 No repository field.
npm WARN mqtt2@1.0.0 No license field.
added 147 packages from 117 contributors in 24.669s
+ chown -R www-data:www-data jeedom mqtt2d.js node_modules package.json package-lock.json
+ echo 5
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end mqtt2
+ rm /tmp/jeedom_install_in_progress_mqtt2
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Et j’utilise jmqtt avec un mosquito local


et les log des dependances :

======================================================================
== 21/05/2023 12:53:07 == Dependencies installation for jMQTT
======================================================================
[  0% ] : Checking parameters...
== System: Linux Jeedom 3.16.85+ #1 SMP PREEMPT Mon Jul 13 14:40:04 UTC 2020 aarch64 GNU/Linux
== Jeedom version: 4.3.17
== jMQTT version: 2023-04-15
[  9% ] : Checking parameters : [  OK  ]
[ 10% ] : Synchronize the package index...
[ 19% ] : Synchronize the package index : ERROR
[ 20% ] : Install Composer...
[ 29% ] : Install Composer : [  OK  ]
[ 30% ] : Install JsonPath-PHP library...
[ 39% ] : Install JsonPath-PHP library : [  OK  ]
[ 40% ] : Remove Composer...
[ 49% ] : Remove Composer : [  OK  ]
[ 50% ] : Install python3 venv and pip debian packages...
[ 59% ] : Install python3 venv and pip debian packages : [  OK  ]
[ 60% ] : Create a python3 Virtual Environment...
[ 69% ] : Create a python3 Virtual Environment : [  OK  ]
[ 70% ] : Install required python3 libraries in venv...
[ 99% ] : Install required python3 libraries in venv : [  OK  ]
[100% ] : Finished !
======================================================================
== KO == Installation Error
======================================================================
== ANALYSING ERRORS...
== NO KNOWN ERROR DETECTED
== Error in step : Synchronize the package index
== Line 24
== Command `sudo apt-get update' have an issue
== Return code is 100
== Error message :
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Get:2 http://ftp.uk.debian.org/debian buster InRelease [122 kB]
Get:3 http://ftp.uk.debian.org/debian buster-updates InRelease [56.6 kB]
Ign:4 https://oph.mdrjr.net/meveric all InRelease
Ign:5 https://oph.mdrjr.net/meveric buster InRelease
Err:7 https://oph.mdrjr.net/meveric all Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 216.155.132.189 443]
Err:8 https://oph.mdrjr.net/meveric buster Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 216.155.132.189 443]
Hit:6 https://packagecloud.io/ookla/speedtest-cli/debian buster InRelease
Reading package lists...
E: The repository 'https://oph.mdrjr.net/meveric all Release' no longer has a Release file.
E: The repository 'https://oph.mdrjr.net/meveric buster Release' no longer has a Release file.
======================================================================

jmqtt semble fonctionner avec mon SPA intex.

Sur mon emc 8giga je n’avais aucun probleme, et la je n’y arrive plus trop

Je n’ai pas trouvé la reponse sur le forum avec « error: cannot find module ‹ worker_threads › »

Merci d’avance,

As-tu tenté de reinstales dépendances ?

Bonjour,

Oui des 3 plugin dans l’ordre jmqtt, mqtt manager et zwavejs , redémarrage de la box.
toujour la meme chose, les dépendances sont ok mais il semble y avoir des erreurs, et le demon ne demare pas avec le message

error: cannot find module ‹ worker_threads.

il y a aussi ce message lors de l’installation des dépendances

Salut,
Peut être :
Aller dans Réglages > Système > Configuration > OS/DB > rétablissement des droits des dossiers et fichiers > Vérifier

Il y a visiblement un repository inaccessible dans tes sources Apt.

Il faut trouver d’où ça vient avant d’aller plus loin, sinon tu ne pourras pas mettre à jour ton système (et peut être installer de nouveaux packages).

Tu as aussi un souci de version NodeJs

Bad

Ok mais je fais quoi?

J’ai juste réinstallé lemc 16g avec jeedom pré-installé et réinstallé mon backup.

Je n’ai pas trop de compétences unix,linux, ca ne me parle pas. je me débrouille un peut

Je testerai un recovery de la smart ce soir sinon

Je n’ai pas trop de temps aujourd’hui pour regarder ça de plus près.

Par contre, il y a pleins de sujets qui en parlent déjà sur Community, notamment :

1 « J'aime »

Je ne cherchais pas avec ce message je pense, quoiqu’il en soit merci je regarde ca. ca semble être le même problème …

je pensais que le passage d’un emc 8g a 16 serait plus simple !

Je suis en cour de restor avec la procédure en lien

Apres le recovery + MAJ de openvpn + le core + ZwaveJS puis de l’installation de la sauvegarde les demons et dependances semblent OK

Mais le plus important Zwaves est OK

Merci beaucoup pour l’aide Bad

1 « J'aime »

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