Dépendance : Mise à jour gsh d’aujourd’hui 29042020

frixo · Mai 5, 2020, 5:08

Idem, j’ai le même soucis sur rpi3 jeedom v4

JAG · Mai 5, 2020, 5:11

Il manque la version de Debian
Tu as l info dans la page santé de jeedom

Salvialf · Mai 5, 2020, 5:11

Même erreur que ce post ?

Quelle est la version de jeedom et debian ?

sACLe · Mai 5, 2020, 5:49

Même erreur pour moi.
Debian 64 dans une VM.

J’ai relancé l’installation des dépendances : KO
Supprimé et réinstallé le plugin (après redémarrage) : KO

Debian 9.12 (VM Proxmox)
Jeedom 3.3.49
Version du plugin gsh : 05/05/2020

c.lebansais · Mai 5, 2020, 6:13

Bonjour pour ma part j’ai toujours le soucis maigres la mise jour de ce jour, mais effectivement pas de problème d’utilisation de plugin, donc pas d’urgence.
J’ai redémarré désactivé/activé toujours le problèmes.
Merci pour votre réactivité
log:

gsh-jeedom-local-discover@0.0.1 start /var/www/html/plugins/gsh/resources/gshd
ts-node server.ts « –udp_discovery_port » « 3311 » « –udp_discovery_packet » « 4A6565646F6D » « –pid » « /tmp/jeedom/gsh/deamon.pid » « –loglevel » « error »
sh: 1: ts-node: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! gsh-jeedom-local-discover@0.0.1 start: ts-node server.ts "--udp_discovery_port" "3311" "--udp_discovery_packet" "4A6565646F6D" "--pid" "/tmp/jeedom/gsh/deamon.pid" "--loglevel" "error"
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the gsh-jeedom-local-discover@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-05-05T18_09_51_583Z-debug.log

JAG · Mai 5, 2020, 6:17

Il y a 2 sujets en cours sur ce pb c’est difficile de suivre
Il manque

Le matériel
Version debian a priori debian 10
Version jeedom

choupfamily63 · Mai 5, 2020, 6:05

Bonjour à tous,

Et bien moi depuis la dernière mise à jour (il y a moins d’une heure), le deamon ne veut plus démarrer.
Log Gshd

> gsh-jeedom-local-discover@0.0.1 start /var/www/html/plugins/gsh/resources/gshd
> ts-node server.ts "--udp_discovery_port" "3311" "--udp_discovery_packet" "4A6565646F6D" "--pid" "/tmp/jeedom/gsh/deamon.pid" "--loglevel" "error"
Error: bind EADDRINUSE 0.0.0.0:3311
at dgram.js:338:20
at processTicksAndRejections (internal/process/task_queues.js:85:21)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! gsh-jeedom-local-discover@0.0.1 start: `ts-node server.ts "--udp_discovery_port" "3311" "--udp_discovery_packet" "4A6565646F6D" "--pid" "/tmp/jeedom/gsh/deamon.pid" "--loglevel" "error"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the gsh-jeedom-local-discover@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-05-05T18_01_59_743Z-debug.log

Log installation des dépendances :



********************************************************
*             Installation des dépendances             *
********************************************************
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:2 http://deb.debian.org/debian buster InRelease
Get:3 http://deb.debian.org/debian buster-updates InRelease [49.3 kB]
Get:4 http://security.debian.org/debian-security buster/updates/main Sources [116 kB]
Get:5 http://security.debian.org/debian-security buster/updates/main amd64 Packages [194 kB]
Get:6 http://security.debian.org/debian-security buster/updates/main Translation-en [104 kB]
Hit:7 https://deb.nodesource.com/node_13.x buster InRelease
Fetched 528 kB in 6s (91.8 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
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.
npm WARN eslint-config-standard@12.0.0 requires a peer of eslint@>=5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-standard-jsx@6.0.2 requires a peer of eslint@>=5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-plugin-es@1.4.0 requires a peer of eslint@>=4.19.1 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-plugin-import@2.14.0 requires a peer of eslint@2.x - 5.x but none is installed. You must install peer dependencies yourself.
npm WARN eslint-plugin-node@7.0.1 requires a peer of eslint@>=4.19.1 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-plugin-react@7.11.1 requires a peer of eslint@^3.0.0 || ^4.0.0 || ^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-plugin-standard@4.0.0 requires a peer of eslint@>=5.0.0 but none is installed. You must install peer dependencies yourself.
audited 499 packages in 5.973s
found 13 vulnerabilities (5 low, 1 moderate, 4 high, 3 critical)
run `npm audit fix` to fix them, or `npm audit` for details
********************************************************
*             Installation terminée                    *
********************************************************

résultat commande « npm audit fix » en SSH

jeedom@JeedomMaison:~$ sudo npm audit fix
[sudo] Mot de passe de jeedom : 
npm ERR! code EAUDITNOPJSON
npm ERR! audit No package.json found: Cannot audit a project without a package.json

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-05-05T18_07_02_997Z-debug.log
jeedom@JeedomMaison:~$

JAG · Mai 5, 2020, 6:09

Il manque

Le matériel
Version debian a priori debian 10
Version jeedom

choupfamily63 · Mai 5, 2020, 6:12

Désolé,

VM PROXMOX DEBIAN 10, jeedom V4.0.54
Mais cela marchait très bien avant cette mise à jour.

J’ai complété mon message ci-dessus.

choupfamily63 · Mai 5, 2020, 6:29

Je confirmes, cela semble fonctionner malgré tout.
Comme quoi il faudrait jamais ce précipiter à faire une mise à jour…mais c’est plus fort que nous.

Salvialf · Mai 5, 2020, 6:31

L’un de vous peut-il ouvrir un ticket afin que @Loic puisse regarder s’il vous plait ?

Greg · Mai 5, 2020, 6:34

Je tente à ouvrir

c.lebansais · Mai 5, 2020, 6:40

Effectivement j’ai oublier les versions

Rpi 3
raspbian stretch release 9.11
jeedom V4.0.54

choupfamily63 · Mai 5, 2020, 7:45

Ticket ouvert.

romaingi · Mai 5, 2020, 8:41

Moi aussi toujours des erreurs et le plugin ne fonctionne pas à la voix. mes scénarios ne fonctionnent plus.
Jeedom v4.0.54 sur DIY Debian Buster

voici log GHSD

gsh-jeedom-local-discover@0.0.1 start /var/www/html/plugins/gsh/resources/gshd
> ts-node server.ts "--udp_discovery_port" "3311" "--udp_discovery_packet" "4A6565646F6D" "--pid" "/tmp/jeedom/gsh/deamon.pid" "--loglevel" "debug"

sh: 1: ts-node: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! gsh-jeedom-local-discover@0.0.1 start: `ts-node server.ts "--udp_discovery_port" "3311" "--udp_discovery_packet" "4A6565646F6D" "--pid" "/tmp/jeedom/gsh/deamon.pid" "--loglevel" "debug"`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the gsh-jeedom-local-discover@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-05-05T20_37_27_380Z-debug.log

tektek · Mai 5, 2020, 10:19

Bonjour à tous,

De mon côté j’ai le même soucis mais il ne fonctionne plus non plus à la main (« Pas de réponse » sur l’app Home). Le hic c’est que je ne sais pas exactement depuis quel moment.

Debian 10 sur Proxmox, Jeedom 4.0.54

test https : ok
test « reconnexion » sur l’app Home : ok
envoi configuration sur le market : ok (fonctionne car à mise à jour les appareils que j’ai supprimé de la config)
test réinstallation des dépendances : même message qu’au dessus (même si pas gênant)

Bon courage et merci d’avance!

PS : les liens des images sur la doc du plugin sont HS (https://doc.jeedom.com/fr_FR/plugins/communication/gsh/)

synthol67 · Mai 6, 2020, 7:34

Salut
moi j’ai un RPI 3b avec stretch 9.6 en 32 bit et Jeedom 3.3.49.
Erreur lors de l’installation des dépendances

Erreur : Processing triggers for libc-bin (2.24-11+deb9u3) ...
(node:8602) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
npm ERR! Error: Method Not Allowed
npm ERR!     at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
npm ERR!     at /usr/share/npm/lib/cache/add-named.js:203:12
npm ERR!     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
npm ERR!     at FSReqWrap.oncomplete (fs.js:135:15)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>
npm ERR! System Linux 4.14.90-v7+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /var/www/html/plugins/gsh/resources/gshd
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code E405
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /var/www/html/plugins/gsh/resources/gshd/npm-debug.log
npm ERR! not ok code 0

axel · Mai 6, 2020, 7:48

Bonjour,
Pareil que @synthol67
Merci

Salvialf · Mai 6, 2020, 7:51

@synthol67 et @axel,

J’ai déjà répondu un peu plus haut concernant ce message d’erreur qui est lié à votre installation.

@guipom a confirmé la résolution de la même erreur sur ce sujet:

Idaho947 · Mai 6, 2020, 8:56

BOnjour,

Je ne sais pas si j’aide ou pas… Avec la maj de ce matin j’ai moins d’erreur mais j’ai toujours :

Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! gsh-jeedom-local-discover@0.0.1 start: `ts-node server.ts "--udp_discovery_port" "3311" "--udp_discovery_packet" "4A6565646F6D" "--pid" "/tmp/jeedom/gsh/deamon.pid" "--loglevel" "info"`
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the gsh-jeedom-local-discover@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-05-06T08_44_10_861Z-debug.log
> gsh-jeedom-local-discover@0.0.1 start /var/www/html/plugins/gsh/resources/gshd
> ts-node server.ts "--udp_discovery_port" "3311" "--udp_discovery_packet" "4A6565646F6D" "--pid" "/tmp/jeedom/gsh/deamon.pid" "--loglevel" "info"

dans le log Gshd. Tout semble fonctionner pour moi sinon

Je suis en 3.3.49 sur une vm debian 9 sur proxmox