idem c’est pas normal, je pense que le core lance un autre script que celui dans resources…
en 4.4 j’ai vu que le script consistency a été mis à jour pour relancer le script install_nodejs.sh, tu peux lancer consistency pour voir ?
oui pour toi ça doit être bon
je viens de voir que le core en branche beta avait une erreur corrigée pourtant en alpha semaine passée, j’ai fait le PR @loic tu peux merger ? donc ceux qui sont en beta ça explique le problème, mais pas les autres
vm deb11, core beta v4.4
Via onglet os db je viens de lancer consistency
je reprécise que j’ai lancé la mise a jour du core 2 fois d’affilée avant…
donc y a bien anguille sous roche concernant nodejs qui reste en v16
@loic je vois qu’il y a une branche revert-2307-beta qui indique v15 aussi, et que tu l’as mergée en beta, je la corrige ? c’est peut-etre elle qui a remis la v15 en beta
non j’ai expliqué plus haut (ya un PR j’attend que loic le valide) mais c’est hors sujet car beta et @leojeedom est en stable
Ah ok autant pour moi alors
Désolé j’ai du mal a suivre sur nodejs je crois que mes soucis perso n’y sont pas pour rien…
Je vais prendre du recul plutot que faire perdre du temps a la communauté
Bha non grace a toi j’ai vu que en beta c’était toujours un Check sur v15
Mais juste pour @leojeedom ca change rien, son script est correct avec la bonne version comme il le signale plus haut… donc je me demande si c’est pas le core qui lancerait le mauvais script…
J’ai fait le merge et monté l’alpha en beta normalement tout est bon
OK merci Loic, je teste et je reviens vers vous
Je viens de faire l’upgrade du core en beta 4.4
Tout à l’air ok, nodejs upgradé.
Voici le log au cas ou
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
[Check Version NodeJS actuelle : v16.20.2 : [ KO ]
Installation de NodeJS 18
Utilisation du dépot officiel
================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================
SCRIPT DEPRECATION WARNING
This script, located at https://deb.nodesource.com/setup_X, used to
install Node.js is deprecated now and will eventually be made inactive.
Please visit the NodeSource distributions Github and follow the
instructions to migrate your repo.
https://github.com/nodesource/distributions
The NodeSource Node.js Linux distributions GitHub repository contains
information about which versions of Node.js and which Linux distributions
are supported and how to install it.
https://github.com/nodesource/distributions
SCRIPT DEPRECATION WARNING
================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================
TO AVOID THIS WAIT MIGRATE THE SCRIPT
Continuing in 60 seconds (press Ctrl-C to abort)
## Installing the NodeSource Node.js 18.x repo
## Populating apt-get cache
+ apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Get:4 https://deb.nodesource.com/node_16.x bullseye InRelease [4586 B]
Fetched 4586 B in 1s (5063 B/s)
Reading package lists
## Confirming "bullseye" is supported
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_18.x/dists/bullseye/Release'
## Adding the NodeSource signing key to your keyring
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null
## Creating apt sources list file for the NodeSource Node.js 18.x repo
+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x bullseye main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x bullseye main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you
+ apt-get update
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Get:4 https://deb.nodesource.com/node_18.x bullseye InRelease [4586 B]
Get:5 https://deb.nodesource.com/node_18.x bullseye/main amd64 Packages [776 B]
Fetched 5362 B in 1s (5174 B/s)
Reading package lists
## Run `sudo apt-get install -y nodejs` to install Node.js 18.x and npm
## You may also need development tools to build native addons:
sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn
Reading package lists
Building dependency tree
Reading state information
The following NEW packages will be installed:
nodejs
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 28.9 MB of archives.
After this operation, 188 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_18.x bullseye/main amd64 nodejs amd64 18.17.1-deb-1nodesource1 [28.9 MB]
Fetched 28.9 MB in 1s (31.9 MB/s)
Selecting previously unselected package nodejs.
(Reading database
(Reading database 5%
(Reading database 10%
(Reading database 15%
(Reading database 20%
(Reading database 25%
(Reading database 30%
(Reading database 35%
(Reading database 40%
(Reading database 45%
(Reading database 50%
(Reading database 55%
(Reading database 60%
(Reading database 65%
(Reading database 70%
(Reading database 75%
(Reading database 80%
(Reading database 85%
(Reading database 90%
(Reading database 95%
(Reading database 100%
(Reading database 124881 files and directories currently installed.)
Preparing to unpack /nodejs_18.17.1-deb-1nodesource1_amd64.deb
Unpacking nodejs (18.17.1-deb-1nodesource1)
Setting up nodejs (18.17.1-deb-1nodesource1)
Processing triggers for man-db (2.9.4-2)
[Check Version NodeJS après install : v18.17.1 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ] | OK
[END CONSISTENCY] | OK
Check update | OK
***************Jeedom is up to date in 4.4.0***************
***************Update plugins***************
[2023-10-19 14:24:06][ALERT] : Vérification des mises à jour, mise à jour et réinstallation désactivées sur Monitoring
[2023-10-19 14:24:06][ALERT] : Vérification des mises à jour, mise à jour et réinstallation désactivées sur zwavejs
***************Update plugin successfully***************
Check update | OK
Enable scenario : | OK
Enable task : | OK
Launch cron dependancy plugins | OK
Send end of update event | OK
Update duration : 165s
[END UPDATE SUCCESS]
Merci @anon53349806 pour tes nombreux tests
je viens faire un PR sur la branche Alpha pour l’instant, avec la nouvelle méthode d’installation de NodeJS. donc ce warning disparaitra.
Sur la version stable 4.4, je viens de procéder à la mise jour de Jmqtt qui lui même relance l’installation du node.js qui ne semble plus s’installer :
package.log (12,2 Ko)
Est-ce que l’on peut faire quelque chose avec APT directement sur le serveur ? Ou le pb vient d’ailleurs ?
Ca part mal, la v4.4 n’est que en beta ou alpha…
Et tu aurais du poster ton log entre balise et montrer la page santé de ton jeedom.
Je dirais bêta car il n’a pas encore le fix pour la dépréciation que j’ai fait
Tu as un problème d’ipv6
err:1%20https%3A//deb.nodesource.com/node_18.x%20buster/main%20arm64%20nodejs%20arm64%2018.17.1-deb-1nodesource1%0A%20%20404%20%20Not%20Found%20%5BIP:%202606:4700:10::ac43:acd%20443%5D%0AE:%20Failed%20to%20fetch%20https://deb.nodesource.com/node_18.x/pool/main/n/nodejs/nodejs_18.17.1-deb-1nodesource1_arm64.deb%20%20404%20%20Not%20Found%20%5BIP:%202606:4700:10::ac43:acd%20443%5D
Arf sur mobile ça donne rien mais c’est l’extrait de ton log
Et autre problème apt.
e:%20Unable%20to%20fetch%20some%20archives,%20maybe%20run%20apt-get%20update%20or%20try%20with%20–fix-missing?
Pardon je suis en 4.3.18, J’étais rester sur la suite du post
+ sudo apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease
Hit:3 http://security.debian.org buster/updates InRelease
Hit:4 http://deb.debian.org/debian buster-backports InRelease
Hit:5 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
+ 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://security.debian.org buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 http://deb.debian.org/debian buster-backports InRelease
Hit:5 https://deb.nodesource.com/node_18.x buster InRelease
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).
git is already the newest version (1:2.20.1-2+deb10u8).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : Aucune : [ KO ]
Installation de NodeJS 18
Utilisation du dépot officiel
================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================
SCRIPT DEPRECATION WARNING
This script, located at https://deb.nodesource.com/setup_X, used to
install Node.js is deprecated now and will eventually be made inactive.
Please visit the NodeSource distributions Github and follow the
instructions to migrate your repo.
https://github.com/nodesource/distributions
The NodeSource Node.js Linux distributions GitHub repository contains
information about which versions of Node.js and which Linux distributions
are supported and how to install it.
https://github.com/nodesource/distributions
SCRIPT DEPRECATION WARNING
================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================
TO AVOID THIS WAIT MIGRATE THE SCRIPT
Continuing in 60 seconds (press Ctrl-C to abort) ...
## Installing the NodeSource Node.js 18.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 http://deb.debian.org/debian buster-backports InRelease
Hit:5 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...
## Confirming "buster" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_18.x/dists/buster/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null
## Creating apt sources list file for the NodeSource Node.js 18.x repo...
+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x buster main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x buster main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 http://deb.debian.org/debian buster-backports InRelease
Hit:5 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...
## Run `sudo apt-get install -y nodejs` to install Node.js 18.x and npm
## You may also need development tools to build native addons:
sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
nodejs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.1 MB of archives.
After this operation, 188 MB of additional disk space will be used.
Err:1 https://deb.nodesource.com/node_18.x buster/main arm64 nodejs arm64 18.17.1-deb-1nodesource1
404 Not Found [IP: 2606:4700:10::ac43:acd 443]
E: Failed to fetch https://deb.nodesource.com/node_18.x/pool/main/n/nodejs/nodejs_18.17.1-deb-1nodesource1_arm64.deb 404 Not Found [IP: 2606:4700:10::ac43:acd 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
/var/www/html/core/class/../../resources/install_nodejs.sh: line 132: nodejs: command not found
[Check Version NodeJS après install : : [ KO ] -> relancez les dépendances
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
npm : Depends: nodejs (>= 6.11~) but it is not going to be installed
Depends: node-abbrev (>= 1.1.1~) but it is not going to be installed
Depends: node-ansi-regex (>= 3.0~) but it is not going to be installed
Depends: node-ansistyles (>= 0.1.3~) but it is not going to be installed
Depends: node-aproba (>= 1.2~) but it is not going to be installed
Depends: node-archy (>= 1.0~) but it is not going to be installed
Depends: node-cacache (>= 10.0.4~) but it is not going to be installed
Depends: node-bluebird (>= 3.5.1~) but it is not going to be installed
Depends: node-call-limit (>= 1.1~) but it is not going to be installed
Depends: node-chownr (>= 1.0.1~) but it is not going to be installed
Depends: node-config-chain (>= 1.1.11~) but it is not going to be installed
Depends: node-detect-indent (>= 5.0~) but it is not going to be installed
Depends: node-detect-newline (>= 2.1~) but it is not going to be installed
Depends: node-editor (>= 1.0~) but it is not going to be installed
Depends: node-fs-vacuum (>= 1.2.10~) but it is not going to be installed
Depends: node-fs-write-stream-atomic (>= 1.0.10~) but it is not going to be installed
Depends: node-glob (>= 7.1.2~) but it is not going to be installed
Depends: node-graceful-fs (>= 4.1.11~) but it is not going to be installed
Depends: node-has-unicode (>= 2.0.1~) but it is not going to be installed
Depends: node-hosted-git-info (>= 2.6~) but it is not going to be installed
Depends: node-iferr (>= 0.1.5~) but it is not going to be installed
Depends: node-inflight (>= 1.0.6~) but it is not going to be installed
Depends: node-inherits (>= 2.0.3~) but it is not going to be installed
Depends: node-ini (>= 1.3.5~) but it is not going to be installed
Depends: node-npm-package-arg but it is not going to be installed
Depends: node-promzard but it is not going to be installed
Depends: node-jsonstream (>= 1.3.2~) but it is not going to be installed
Depends: node-json-parse-better-errors (>= 1.0.1~) but it is not going to be installed
Depends: node-lazy-property (>= 1.0~) but it is not going to be installed
Depends: node-libnpx (>= 10.0.1~) but it is not going to be installed
Depends: node-lockfile (>= 1.0.3~) but it is not going to be installed
Depends: node-lru-cache (>= 4.1.1~) but it is not going to be installed
Depends: node-mississippi (>= 3.0~) but it is not going to be installed
Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
Depends: node-move-concurrently (>= 1.0.1~) but it is not going to be installed
Depends: node-nopt but it is not going to be installed
Depends: node-normalize-package-data (>= 2.4~) but it is not going to be installed
Depends: node-gyp (>= 3.6.2~) but it is not going to be installed
Depends: node-resolve-from (>= 4.0~) but it is not going to be installed
Depends: node-encoding but it is not going to be installed
Depends: node-errno but it is not going to be installed
Depends: node-npmlog (>= 4.1.2~) but it is not going to be installed
Depends: node-once (>= 1.4~) but it is not going to be installed
Depends: node-opener (>= 1.4.3~) but it is not going to be installed
Depends: node-osenv (>= 0.1.5~) but it is not going to be installed
Depends: node-path-is-inside (>= 1.0.2~) but it is not going to be installed
Depends: node-promise-inflight (>= 1.0.1~) but it is not going to be installed
Depends: node-ansi but it is not going to be installed
Depends: node-qw (>= 1.0.1~) but it is not going to be installed
Depends: node-read (>= 1.0.7~) but it is not going to be installed
Depends: node-read-package-json (>= 2.0.13~) but it is not going to be installed
Depends: node-request (>= 2.83~) but it is not going to be installed
Depends: node-retry (>= 0.10.1~) but it is not going to be installed
Depends: node-rimraf (>= 2.6.2~) but it is not going to be installed
Depends: node-safe-buffer (>= 5.1.1~) but it is not going to be installed
Depends: node-semver (>= 5.5~) but it is not going to be installed
Depends: node-sha (>= 2.0.1~) but it is not going to be installed
Depends: node-slide (>= 1.1.6~) but it is not going to be installed
Depends: node-sorted-object (>= 2.0.1~) but it is not going to be installed
Depends: node-from2 but it is not going to be installed
Depends: node-stream-iterate but it is not going to be installed
Depends: node-ssri (>= 5.2.4~) but it is not going to be installed
Depends: node-strip-ansi (>= 4.0~) but it is not going to be installed
Depends: node-tar (>= 4.4~) but it is not going to be installed
Depends: node-text-table (>= 0.2~) but it is not going to be installed
Depends: node-uid-number (>= 0.0.6~) but it is not going to be installed
Depends: node-unique-filename (>= 1.1~) but it is not going to be installed
Depends: node-unpipe (>= 1.0~) but it is not going to be installed
Depends: node-boxen (>= 1.2.1~) but it is not going to be installed
Depends: node-import-lazy but it is not going to be installed
Depends: node-is-npm (>= 1.0~) but it is not going to be installed
Depends: node-latest-version (>= 3.0~) but it is not going to be installed
Depends: node-semver-diff (>= 2.0~) but it is not going to be installed
Depends: node-xdg-basedir (>= 3.0~) but it is not going to be installed
Depends: node-validate-npm-package-name (>= 3.0~) but it is not going to be installed
Depends: node-which (>= 1.3~) but it is not going to be installed
Depends: node-wrappy (>= 1.0.2~) but it is not going to be installed
Depends: node-write-file-atomic (>= 2.3~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
sudo: npm: command not found
Le pb IPV6 c’est cette ligne là ?
Err:1 https://deb.nodesource.com/node_18.x buster/main arm64 nodejs arm64 18.17.1-deb-1nodesource1
404 Not Found [IP: 2606:4700:10::ac43:acd 443]
E: Failed to fetch https://deb.nodesource.com/node_18.x/pool/main/n/nodejs/nodejs_18.17.1-deb-1nodesource1_arm64.deb 404 Not Found [IP: 2606:4700:10::ac43:acd 443]
Tu parles de Mqtt Manager (mqtt2), pas jMQTT, on est d’accord ?
jMQTT n’a aucune raison de lancer l’installation de nodejs, ne l’utilisant pas.