Installation des dépendances sur plusieurs pluging ko

Bonjour,
depuis hier, il m’est impossible de réaliser l’installation de dépendances sur quelques pluging (GSH - ZigbeeLinker - ATVremote).
Ca a commencé hier par ATV remote et ce matin, en cherchant , les 2 autres ne se lance pas non plus.

voici ma configuration :

Les log de Google Smart Home (GLS)

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_gsh
+ echo 1
+ echo 2
+ 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/debian-security bullseye-security InRelease
Hit:2 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Get:5 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
Err:5 https://deb.nodesource.com/node_20.x nodistro InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
Reading package lists...

W: GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
E: The repository 'https://deb.nodesource.com/node_20.x nodistro InRelease' is not signed.
Reading package lists...
Building dependency tree...

Reading state information...
apt-utils is already the newest version (2.2.4).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v12.22.12 : [  KO  ]
Installation de NodeJS 16
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
Utilisation du dépot officiel

## Installing the NodeSource Node.js 16.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:2 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Hit:3 http://archive.raspberrypi.org/debian buster InRelease
Hit:4 http://security.debian.org/debian-security bullseye-security InRelease
Get:5 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
Err:5 https://deb.nodesource.com/node_20.x nodistro InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
Reading package lists...

W: GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
E: The repository 'https://deb.nodesource.com/node_20.x nodistro InRelease' is not signed.
Error executing command, exiting
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libc-ares2 libjs-highlight.js libnode72 nodejs-doc
Suggested packages:
  npm
The following NEW packages will be installed:
  libc-ares2 libjs-highlight.js libnode72 nodejs nodejs-doc
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/10.9 MB of archives.
After this operation, 47.9 MB of additional disk space will be used.
Selecting previously unselected package libc-ares2:arm64.
(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 ... 61311 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.17.1-1+deb11u3_arm64.deb ...
Unpacking libc-ares2:arm64 (1.17.1-1+deb11u3) ...
Selecting previously unselected package libjs-highlight.js.
Preparing to unpack .../libjs-highlight.js_9.18.5+dfsg1-1_all.deb ...
Unpacking libjs-highlight.js (9.18.5+dfsg1-1) ...
Selecting previously unselected package libnode72:arm64.
Preparing to unpack .../libnode72_12.22.12~dfsg-1~deb11u4_arm64.deb ...
Unpacking libnode72:arm64 (12.22.12~dfsg-1~deb11u4) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_12.22.12~dfsg-1~deb11u4_arm64.deb ...
Unpacking nodejs (12.22.12~dfsg-1~deb11u4) ...
Selecting previously unselected package nodejs-doc.
Preparing to unpack .../nodejs-doc_12.22.12~dfsg-1~deb11u4_all.deb ...
Unpacking nodejs-doc (12.22.12~dfsg-1~deb11u4) ...
Setting up libc-ares2:arm64 (1.17.1-1+deb11u3) ...
Setting up libnode72:arm64 (12.22.12~dfsg-1~deb11u4) ...
Setting up libjs-highlight.js (9.18.5+dfsg1-1) ...
Setting up nodejs (12.22.12~dfsg-1~deb11u4) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Setting up nodejs-doc (12.22.12~dfsg-1~deb11u4) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u6) ...
[Check Version NodeJS après install : v12.22.12 : [  KO  ] -> relancez les dépendances
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
[Check Prefix :  and sudo prefix :  and www-data prefix :  : [  KO  ]
Reset prefix (/usr) pour npm root
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
+ echo 3
+ 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/debian-security bullseye-security InRelease
Hit:2 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Get:5 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
Err:5 https://deb.nodesource.com/node_20.x nodistro InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
Reading package lists...
W: GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
E: The repository 'https://deb.nodesource.com/node_20.x nodistro InRelease' is not signed.
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v12.22.12 : [  KO  ]
Installation de NodeJS 16
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
Utilisation du dépot officiel

## Installing the NodeSource Node.js 16.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:4 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Get:5 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
Err:5 https://deb.nodesource.com/node_20.x nodistro InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
Reading package lists...
W: GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
E: The repository 'https://deb.nodesource.com/node_20.x nodistro InRelease' is not signed.
Error executing command, exiting
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libc-ares2 libjs-highlight.js libnode72 nodejs-doc
Suggested packages:
  npm
The following NEW packages will be installed:
  libc-ares2 libjs-highlight.js libnode72 nodejs nodejs-doc
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/10.9 MB of archives.
After this operation, 47.9 MB of additional disk space will be used.
Selecting previously unselected package libc-ares2:arm64.
(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 ... 61311 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.17.1-1+deb11u3_arm64.deb ...
Unpacking libc-ares2:arm64 (1.17.1-1+deb11u3) ...
Selecting previously unselected package libjs-highlight.js.
Preparing to unpack .../libjs-highlight.js_9.18.5+dfsg1-1_all.deb ...
Unpacking libjs-highlight.js (9.18.5+dfsg1-1) ...
Selecting previously unselected package libnode72:arm64.
Preparing to unpack .../libnode72_12.22.12~dfsg-1~deb11u4_arm64.deb ...
Unpacking libnode72:arm64 (12.22.12~dfsg-1~deb11u4) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_12.22.12~dfsg-1~deb11u4_arm64.deb ...
Unpacking nodejs (12.22.12~dfsg-1~deb11u4) ...
Selecting previously unselected package nodejs-doc.
Preparing to unpack .../nodejs-doc_12.22.12~dfsg-1~deb11u4_all.deb ...
Unpacking nodejs-doc (12.22.12~dfsg-1~deb11u4) ...
Setting up libc-ares2:arm64 (1.17.1-1+deb11u3) ...
Setting up libnode72:arm64 (12.22.12~dfsg-1~deb11u4) ...
Setting up libjs-highlight.js (9.18.5+dfsg1-1) ...
Setting up nodejs (12.22.12~dfsg-1~deb11u4) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Setting up nodejs-doc (12.22.12~dfsg-1~deb11u4) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u6) ...
[Check Version NodeJS après install : v12.22.12 : [  KO  ] -> relancez les dépendances
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
[Check Prefix :  and sudo prefix :  and www-data prefix :  : [  KO  ]
Reset prefix (/usr) pour npm root
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
+ echo 4
+ cd /var/www/html/core/class/../../plugins/gsh/resources/gshd
+ rm -rf node_modules
+ sudo npm install
ERROR: npm v9.8.1 is known not to run on Node.js v12.22.12.  This version of npm supports the following node versions: `^14.17.0 || ^16.13.0 || >=18.0.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/usr/local/lib/node_modules/npm/lib/utils/exit-handler.js:19
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:15:23)
    at module.exports (/usr/local/lib/node_modules/npm/lib/es6/validate-engines.js:39:10)
    at module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:4:31)
+ chown -R www-data:www-data gshd.js package-lock.json package.json
+ echo 5
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end gsh
+ rm /tmp/jeedom_install_in_progress_gsh
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Les log d’ATVremote :

== Jeedom 4.3.17 sur Debian GNU/Linux 11 (bullseye)/arm64/aarch64/64bits aka 'rpi' avec nodeJS v12.22.12 et jsonrpc:enable et aTVremote (beta) 2023-08-04 07:13:59 (avant:beta/2023-08-04 07:13:59)
======================================================================
== 30/08/2023 11:57:13 == Installation des dépendances de aTVremote
======================================================================

[  0% ] : Vérification des droits...
[  4% ] : Vérification des droits : [0sec] : [  OK  ]
[  5% ] : Mise à jour APT et installation des packages nécessaires...
[ 99% ] : Mise à jour APT et installation des packages nécessaires : [6sec] : [Erreur]
[100% ] : Terminé !

======================================================================
== KO == Erreur d'Installation [6sec]
======================================================================
== ANALYSE DES ERREURS...
== AUCUNE ERREUR CONNUE DÉTECTÉE
== Erreur à l'étape : Mise à jour APT et installation des packages nécessaires
== Ligne 160
== La commande `sudo apt-get update' pose problème
== Le code de retour est 100
== Le message d'erreur :
Hit:1 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:2 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Get:5 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
Err:5 https://deb.nodesource.com/node_20.x nodistro InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
Reading package lists...
W: GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
E: The repository 'https://deb.nodesource.com/node_20.x nodistro InRelease' is not signed.

======================================================================

Et enfin ceux de ZigbeeLinker :

#######################################################
#    INSTALL : Zigbee2mqtt                            #
#######################################################
#######################################################
##### apt-get update in progress
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:3 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Get:5 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
Err:5 https://deb.nodesource.com/node_20.x nodistro InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
Reading package lists...

W: GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
E: The repository 'https://deb.nodesource.com/node_20.x nodistro InRelease' is not signed.
#######################################################
##### Install or update Git
Reading package lists...
Building dependency tree...

Reading state information...
g++ is already the newest version (4:10.2.1-1).
gcc is already the newest version (4:10.2.1-1).
git is already the newest version (1:2.30.2-1+deb11u2).
make is already the newest version (4.3-4.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
#######################################################
##### Install or update NodeJs

## Installing the NodeSource Node.js 16.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://ftp.fr.debian.org/debian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian buster InRelease
Hit:4 http://ftp.fr.debian.org/debian bullseye-updates InRelease
Get:5 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
Err:5 https://deb.nodesource.com/node_20.x nodistro InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
Reading package lists...

W: GPG error: https://deb.nodesource.com/node_20.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
E: The repository 'https://deb.nodesource.com/node_20.x nodistro InRelease' is not signed.
Error executing command, exiting
Reading package lists...
Building dependency tree...

Reading state information...
nodejs is already the newest version (12.22.12~dfsg-1~deb11u4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
##### WARNING : NodeJS 12 installed. This plugin need 16 minimal version
#######################################################
#    INSTALLING : Mosquitto (server)                  #
#######################################################
Reading package lists...
Building dependency tree...

Reading state information...
mosquitto is already the newest version (2.0.11-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
#######################################################
#    INSTALLING : Mosquitto for Php                   #
#######################################################
Mosquitto for Php is already installed, nothing to do
#######################################################
##### Install Socat
Socat is already installed, nothing to do
#######################################################
##### Install yaml php and restart apache
Yaml is already installed, nothing to do
#######################################################
#####    Stopping Zigbee2mqtt deamon                  #
Removed /etc/systemd/system/multi-user.target.wants/zigbee2mqtt.service.
#######################################################
##### Update : Download update from Zigbee2mqtt git
##### up to date
#######################################################
##### Configure deamon and start it
Created symlink /etc/systemd/system/multi-user.target.wants/zigbee2mqtt.service -> /etc/systemd/system/zigbee2mqtt.service.
#######################################################
#                         END                         #
#######################################################

Je vois bien qu’il y a une erreur de clé publique qui n’est pas disponible lorsque j’exécute la commande « sudo apt-get update » en SSH sur mon rasberry.
Après avoir parcouru le forum, je suis tomber sur ce fil : « Problème d’installation de dépendance ». J’ai donc exécuté les commandes suivantes :

« sudo apt install ca-certificates » pour mettre à jour mes certificats

j’ai ensuite modifier le fichier sources.list en ajoutant les [trusted=yes]

# deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Official Snapshot amd64 LIVE/INSTALL Binary 20230602-06:28]/ buster main

#deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Official Snapshot amd64 LIVE/INSTALL Binary 20230602-06:28]/ buster main

deb [trusted=yes] http://ftp.fr.debian.org/debian bullseye main non-free contrib
deb-src [trusted=yes] http://ftp.fr.debian.org/debian bullseye main non-free contrib

# Line commented out by installer because it failed to verify:
deb [trusted=yes] http://security.debian.org/debian-security bullseye-security main contrib non-free
# Line commented out by installer because it failed to verify:
deb-src [trusted=yes] http://security.debian.org/debian-security bullseye-security main contrib non-free

# bullseye-updates, previously known as 'volatile'
deb [trusted=yes] http://ftp.fr.debian.org/debian bullseye-updates main contrib non-free
deb-src [trusted=yes] http://ftp.fr.debian.org/debian bullseye-updates main contrib non-free

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,



Rien y fait, je n’arrive pas à résoudre mon problème et l’installation des dépendances ne se fait pas.

Merci pour votre aide.

Bonjour,

Vous avez un mix de bullseye & buster dans vos repos
comment avez-vous installé bullseye?

Refaites une installation propre.

Bonjour Mips,
J’avais fait une mise à jour (début d’année je crois) de debian 10 vers 11 faisant un « Full Upgrade »… Ca fonctionnait bien jusque là :frowning:
Je vais donc refaire une installation propre… merci.

vous utilisez aussi probablement un plugin en beta qui utilise déjà node 20… hors support donc en théorie.

tapez ceci :

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 2F59B5F99B1BE0B4

en effet, mauvaise procédure pour faire la mise à jour, même si la commande que je vous ai donné va résoudre votre problème immédiat, il y a ce problème latent … je vous conseille une réinstallation propre d’une debian 11 plutot qu’un full upgrade fait à moitié (et restauration backup)

Merci pour ton aide également nebz.
J’ai aussi essayer la commande sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 2F59B5F99B1BE0B4 mais sans résultat.

Je vais suivre vos précieux conseil et refaire une installation propre :slight_smile:

aucun message d’erreur ni rien ? il ne se passe rien et le log est exactement le même ?

jeedom@jeedom:~ $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 2F59B5F99B1BE0B4
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.JCu4pFVG51/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 2F59B5F99B1BE0B4
gpg: clef 2F59B5F99B1BE0B4 : « NSolid <nsolid-gpg@nodesource.com> » n'est pas modifiée
gpg:       Quantité totale traitée : 1
gpg:                 non modifiées : 1

voici ce que cela avait donné

la clé est donc bonne, donc le problème vient de votre système en effet

En tout les cas, merci pour la réactivité ! :slight_smile:
:+1:

1 « J'aime »

Bon he bien installation faite mais les dépendances ne s’installe toujours pas . voici les log de GSH si vous avez une idée ???

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_gsh
+ echo 1
+ echo 2
+ sudo apt update

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

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
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists...
E: Problem renaming the file /var/cache/apt/pkgcache.bin.9THvMR to /var/cache/apt/pkgcache.bin - rename (2: No such file or directory)
W: You may want to run apt-get update to correct these problems
E: The package cache file is corrupted
+ echo 3
+ 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://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.nodesource.com/node_16.x bullseye InRelease
Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease
Reading package lists...
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 187144 (apt-get)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
[Check Version NodeJS actuelle : Aucune : [  KO  ]
Installation de NodeJS 16
Utilisation du dépot officiel

## Installing the NodeSource Node.js 16.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists...

## Confirming "bullseye" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_16.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 16.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.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_16.x bullseye main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Reading package lists...
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 187660 (apt-get)
E: Unable to lock directory /var/lib/apt/lists/
Error executing command, exiting
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 26.6 MB of archives.
After this operation, 128 MB of additional disk space will be used.
Err:1 https://deb.nodesource.com/node_16.x bullseye/main arm64 nodejs arm64 16.20.2-deb-1nodesource1
  404  Not Found [IP: 2606:4700:10::6816:51a 443]
E: Failed to fetch https://deb.nodesource.com/node_16.x/pool/main/n/nodejs/nodejs_16.20.2-deb-1nodesource1_arm64.deb  404  Not Found [IP: 2606:4700:10::6816:51a 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 141: 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:
 libnode72 : Conflicts: nodejs-legacy
 nodejs : Conflicts: npm
E: Unable to correct problems, you have held broken packages.
sudo: npm: command not found
+ echo 4
+ 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/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists...
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 188600 (apt-get)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
[Check Version NodeJS actuelle : Aucune : [  KO  ]
Installation de NodeJS 16
Utilisation du dépot officiel

## Installing the NodeSource Node.js 16.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 http://security.debian.org/debian-security bullseye-security InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists...

## Confirming "bullseye" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_16.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 16.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.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_16.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
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists...

## Run `sudo apt-get install -y nodejs` to install Node.js 16.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 26.6 MB of archives.
After this operation, 128 MB of additional disk space will be used.
Err:1 https://deb.nodesource.com/node_16.x bullseye/main arm64 nodejs arm64 16.20.2-deb-1nodesource1
  404  Not Found [IP: 2606:4700:10::6816:51a 443]
E: Failed to fetch https://deb.nodesource.com/node_16.x/pool/main/n/nodejs/nodejs_16.20.2-deb-1nodesource1_arm64.deb  404  Not Found [IP: 2606:4700:10::6816:51a 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 141: nodejs: command not found
[Check Version NodeJS après install :  : [  KO  ] -> relancez les dépendances
Reading package lists...
E: Problem renaming the file /var/cache/apt/pkgcache.bin.G5gPf9 to /var/cache/apt/pkgcache.bin - rename (2: No such file or directory)
W: You may want to run apt-get update to correct these problems
E: The package cache file is corrupted
sudo: npm: command not found
+ 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://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : Aucune : [  KO  ]
Installation de NodeJS 16
Utilisation du dépot officiel

## Installing the NodeSource Node.js 16.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists...

## Confirming "bullseye" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_16.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 16.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.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_16.x bullseye main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists...

## Run `sudo apt-get install -y nodejs` to install Node.js 16.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 26.6 MB of archives.
After this operation, 128 MB of additional disk space will be used.
Err:1 https://deb.nodesource.com/node_16.x bullseye/main arm64 nodejs arm64 16.20.2-deb-1nodesource1
  404  Not Found [IP: 2606:4700:10::6816:51a 443]
E: Failed to fetch https://deb.nodesource.com/node_16.x/pool/main/n/nodejs/nodejs_16.20.2-deb-1nodesource1_arm64.deb  404  Not Found [IP: 2606:4700:10::6816:51a 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 141: 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:
 libnode72 : Conflicts: nodejs-legacy
 nodejs : Conflicts: npm
E: Unable to correct problems, you have held broken packages.
sudo: npm: command not found
+ echo 6
+ cd /var/www/html/core/class/../../plugins/gsh/resources/gshd
+ rm -rf node_modules
+ sudo npm install
sudo: npm: command not found
+ chown -R www-data:www-data gshd.js package.json package-lock.json
+ echo 7
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end gsh
+ rm /tmp/jeedom_install_in_progress_gsh
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Je dois m’absenter un peu donc je vois les réponses après :slight_smile:

encore merci

vous avez installé un debian avec l’interface non ? car il dit que c’est le frontend dpgk qui le bloque et le cache est corrompu il vous demande de lancer une commande.

(il faut installer debian sans interface !)

j’ai fait l’installation sans interface (lite)

Il y a autre chose qui utilisait dpkg à ce moment là, redémarrez et ressayez

Ou attendre la fin de l’installation d’autres dépendances.

J’ai eu cela lors de ma dernière restauration. Du coup j’ai supprimé l’installation automatique des dépendances pour l’ensemble des plugins et je les lances manuellement les unes après les autres.

en théorie c’est pas sensé arriver… le core doit le gérer… si une autre dépendance tourne, il n’autorise pas de la lancer.

Je t’assure que j’ai constaté plusieurs fois le même problème.

Bonsoir,
Bon du coup, tout est installé… J’ai juste ZigbeeLinker qui ne fonctionne car le service zigbee2mqtt s’arrête et redémarre sans arrêt…

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