Erreur lors de l'activation du plugin

Tags: #<Tag:0x00007fa7bea42d70>

Lors de l’activation le plugin se met en NOK.
Le log est le suivant :

internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module 'request'
Require stack:
- /var/www/html/plugins/espeasy/resources/espeasy.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/var/www/html/plugins/espeasy/resources/espeasy.js:3:15)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    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 Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/var/www/html/plugins/espeasy/resources/espeasy.js' ]
}

Pouvez-vous m’aider à résoudre ce problème ?
Merci de votre réponse.

Vous devez mettre ici le journal de l’installation des dépendances du plugin.

Sinon, testez ce qui suit en SSH :
sudo pip3 install requests

Si cela ne fonctionne pas mieux, faites cela :
sudo pip install requests

Merci de votre réponse.
Il m’est impossible de joindre ce que vous me demandez car j’ai un message m’indiquant que je ne peux pas joindre plus de deux liens par message.

Et voici les résultats des commandes :

pierre@jeedom:~$ sudo pip3 install requests
[sudo] Mot de passe de pierre : 
Requirement already satisfied: requests in /usr/lib/python3/dist-packages (2.21.0)
pierre@jeedom:~$ sudo pip install requests
Requirement already satisfied: requests in /usr/lib/python2.7/dist-packages (2.21.0)
pierre@jeedom:~$

Merci.

Le journal ce place dans un bloc code </>

Comme je viens de le faire pour votre message.

Comment faut-il faire un bloc code </> ?

Quand vous éditez / écrivez un message, il y a une petite barre d’outils, ce bloc y est présent.

[TUTORIEL] Comment inclure des log ou textes long dans un post - Discussions Générales - Communauté Jeedom

1 J'aime

bloc code

Merci voilà le log :

Début de l'installation
--2021-03-30 11:12:55--  https://raw.githubusercontent.com/lunarok/jeedom_nodejs/master/nodejs.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.109.133, 185.199.111.133, 185.199.108.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.109.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1491 (1.5K) [text/plain]
Saving to: 'dependencies.sh'

     0K .                                                     100% 2.23M=0.001s

2021-03-30 11:12:55 (2.23 MB/s) - 'dependencies.sh' saved [1491/1491]

dependencies.sh: 3: [: espeasy: unexpected operator
Version actuelle : 12
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:2 http://ftp.de.debian.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_12.x buster InRelease
Get:4 http://security.debian.org/debian-security buster/updates/main Sources [179 kB]
Get:5 http://security.debian.org/debian-security buster/updates/main amd64 Packages [269 kB]
Fetched 513 kB in 2s (332 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (10.2019051400).
0 upgraded, 0 newly installed, 0 to remove and 80 not upgraded.
Ok, version suffisante
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
added 48 packages from 58 contributors and audited 48 packages in 6.019s

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

found 0 vulnerabilities

Fin de l'installation

EDITE:

Hello,
En cherchant sur github, j’ai trouvé que « request » n’était en effet plus maintenu. On peut le remplacer par « got ».
Qui peut me dire comment prendre contact avec l’auteur de ESPeasy pour lui demander de faire la modification ?
Merci de votre réponse.

1 J'aime

Pour le plugin tu regarde qui est l’auteur dans sa configuration.

C’est Lunarok, merci.

Comment puis-je contacter Lunarok ?

Attendre qu’il passe par ici son MP n’est pas ouvert il me semble.

Ou peut-être via son github …

1 J'aime

Relance les dépendances.
Tu devrais avoir la v14 depuis le 01 avril.

je viens de relancer l’installation et ensuite les dépendances.
Même résultat.

Les logs stp.

EspEasy-dep :

Début de l'installation
--2021-04-07 10:26:29--  https://raw.githubusercontent.com/lunarok/jeedom_nodejs/master/nodejs.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.108.133, 185.199.109.133, 185.199.110.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.108.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1510 (1.5K) [text/plain]
Saving to: 'dependencies.sh'

     0K .                                                     100%  578K=0.003s

2021-04-07 10:26:30 (578 KB/s) - 'dependencies.sh' saved [1510/1510]

dependencies.sh: 3: [: espeasy: unexpected operator
Version actuelle : 12
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:2 https://deb.nodesource.com/node_12.x buster InRelease [4584 B]
Hit:3 http://ftp.de.debian.org/debian buster InRelease
Get:4 http://security.debian.org/debian-security buster/updates/main Sources [180 kB]
Get:5 http://security.debian.org/debian-security buster/updates/main amd64 Packages [271 kB]
Get:6 https://deb.nodesource.com/node_12.x buster/main amd64 Packages [766 B]
Get:7 http://security.debian.org/debian-security buster/updates/main Translation-en [145 kB]
Fetched 667 kB in 2s (389 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (10.2019051400).
0 upgraded, 0 newly installed, 0 to remove and 88 not upgraded.
dependencies.sh: 29: dependencies.sh: [[: not found
KO, version obsolète à upgrader
Suppression du Nodejs existant et installation du paquet recommandé
Reading package lists...
Building dependency tree...
Reading state information...
Package 'npm' is not installed, so not removed
The following packages will be REMOVED:
  nodejs*
0 upgraded, 0 newly installed, 1 to remove and 87 not upgraded.
After this operation, 93.5 MB disk space will be freed.
(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 ... 122630 files and directories currently installed.)
Removing nodejs (12.21.0-1nodesource1) ...
dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules' not empty so not removed
Processing triggers for man-db (2.8.5-2) ...
dependencies.sh: 38: [: x86_64: unexpected operator
Utilisation du dépot officiel

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


## Populating apt-get cache...

+ apt-get update
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 http://ftp.de.debian.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_12.x buster InRelease
Reading package lists...

## Confirming "buster" is supported...

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

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.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_14.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/debian-security buster/updates InRelease
Hit:2 http://ftp.de.debian.org/debian buster InRelease
Get:3 https://deb.nodesource.com/node_14.x buster InRelease [4584 B]
Get:4 https://deb.nodesource.com/node_14.x buster/main amd64 Packages [767 B]
Fetched 5351 B in 2s (3377 B/s)
Reading package lists...

## Run `sudo apt-get install -y nodejs` to install Node.js 14.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 87 not upgraded.
Need to get 24.7 MB of archives.
After this operation, 119 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_14.x buster/main amd64 nodejs amd64 14.16.1-1nodesource1 [24.7 MB]
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin: 
Fetched 24.7 MB in 32s (775 kB/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 ... 117745 files and directories currently installed.)
Preparing to unpack .../nodejs_14.16.1-1nodesource1_amd64.deb ...
Unpacking nodejs (14.16.1-1nodesource1) ...
Setting up nodejs (14.16.1-1nodesource1) ...
Processing triggers for man-db (2.8.5-2) ...
Version actuelle : v14.16.1
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm notice created a lockfile as package-lock.json. You should commit this file.
added 48 packages from 58 contributors and audited 48 packages in 6.059s

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

found 0 vulnerabilities

Fin de l'installation

EspEasy-node :

internal/modules/cjs/loader.js:818
throw err;
^

Error: Cannot find module 'request'
Require stack:
- /var/www/html/plugins/espeasy/resources/espeasy.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/var/www/html/plugins/espeasy/resources/espeasy.js:3:15)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    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 Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/var/www/html/plugins/espeasy/resources/espeasy.js' ]
}

J’ai résolu le problème :
J’ai désinstallé le plugin et rebooté le système.
J’ai réinstallé ESPeasy et le daemon s’est correctement réinitialisé.
Je remercie chaleureusement ceux qui m’ont aidé.
On peut clore le sujet.
Peyo33

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