Avant toute chose merci de (re)prendre connaissance de la charte et de la respecter.
Pour résumer :
- Avant de poser une question, je cherche si la réponse existe
- Je suis poli, courtois et je respecte tout un chacun sur le forum
- Si un post m'agace : je m'en éloigne plutôt que de répondre d'une façon qui pourrait être mal interprétée


Il n'est jamais du luxe que de rappeler des choses simples :
Courtoisie, amabilité, politesse et bonne humeur sont les maîtres mots pour un forum sympathique, bienveillant et accueillant :)

Toute la communauté vous remercie

dépendance et daemon NOK

matthieu51
Timide
Messages : 14
Inscription : 10 déc. 2017, 09:21
Contact :

dépendance et daemon NOK

Message par matthieu51 » 10 déc. 2017, 09:34

Bonjour,
Je suis un jeune Jeedomien, je vient d'acheter le plugin zibasedom, mais n'arrive pas à récuperer tous les périphériques de ma zibase (multi)
Etant actuellement en tests de compatibilités jeedom et zibase, j'évolue sur un environnement Raspberry en VM.

Actuellement j'ai récupéré 9 périphériques sur une quinzaine.
Apres avoir configuré le plugin, (réseau, ID zibase, token ), j'ai un message d'erreur : "Impossible de lancer le démon Zibasedom"
De plus "DÉPENDANCE" et "DAEMON" sont en NOK. Du coup j'ai mis mon JEEDOM en DMZ histoire de voir sir le problème venait de du port 17100 mais sans résultat.

Quelqu’un aurait une solution ?

matthieu51
Timide
Messages : 14
Inscription : 10 déc. 2017, 09:21
Contact :

Re: dépendance et daemon NOK

Message par matthieu51 » 10 déc. 2017, 09:57

j'ai ce message d'erreur dans mon log :

[2017-12-10 09:49:32][ERROR] : {{Impossible de lancer le démon Zibasedom}}
[2017-12-10 09:50:02][INFO] : {{Lancement démon Zibasedom}} : node /var/www/html/plugins/Zibasedom/node/Zibasedom.js 192.168.0.38 80 /core/api/jeeApi.php?api=XeO5Bmwtnc9MFHrKk6dig7fPDcbRiEwP 192.168.0.253 600000 400
nohup: impossible d'exécuter la commande 'node': Aucun fichier ou dossier de ce type
[2017-12-10 09:50:02][INFO] : Installation des dépendances nodejs
[2017-12-10 09:50:12][INFO] : {{Lancement démon Zibasedom}} : node /var/www/html/plugins/Zibasedom/node/Zibasedom.js 192.168.0.38 80 /core/api/jeeApi.php?api=XeO5Bmwtnc9MFHrKk6dig7fPDcbRiEwP 192.168.0.253 600000 400
nohup: impossible d'exécuter la commande 'node': Aucun fichier ou dossier de ce type

matthieu51
Timide
Messages : 14
Inscription : 10 déc. 2017, 09:21
Contact :

Re: dépendance et daemon NOK

Message par matthieu51 » 10 déc. 2017, 15:02

ok j'ai réussi à récupérer mes périphériques mais impossible de les actionner via jeedom ou le plugin alors qu'avec zibase multi cela fonctionne
Je vais arreter la mon monologue ....

Avatar de l’utilisateur
Bosquetia
Actif
Messages : 5833
Inscription : 10 mai 2016, 07:54

Re: dépendance et daemon NOK

Message par Bosquetia » 10 déc. 2017, 15:28

Hello,

Tu dis : "De plus "DÉPENDANCE" et "DAEMON" sont en NOK."

Sans les dépendances OK, le deamon ne pourra jamais démarrer !

Néanmoins pourquoi les dépendances sont NOK ben on n'en sait rien car en 3 posts de monologues tu n'as donné aucune information exploitable pour qu'on puisse t'aider...

matthieu51
Timide
Messages : 14
Inscription : 10 déc. 2017, 09:21
Contact :

Re: dépendance et daemon NOK

Message par matthieu51 » 10 déc. 2017, 17:21

j'ai bien mes peripheriques, mais ils ne communiquent pas lors des tests soit en configuration ds le plugin ni dans le dashboard
ex: j'appuie sur "On" rien ne ce passe. Je n'y conniais pas grand chose je découvre alors au lieu de me dire que je ne donne pas les bonnes informations, dit moi ce qu'il faut que je donne pour pouvoir m'aider. Je m'attendais a une aide plus constructive, c'est dommmage.

Avatar de l’utilisateur
Bosquetia
Actif
Messages : 5833
Inscription : 10 mai 2016, 07:54

Re: dépendance et daemon NOK

Message par Bosquetia » 10 déc. 2017, 17:27

SI tes dépendances sont NOK donner le log d'installation des dépendances serait deja bien !
La page santé de jeedom aussi peut aider.

Tu veux de l'aide et en plus tu critiques la main que l'on te tends... sans faire d'effort toi même pour nous donner ne fut ce que la version de jeedom, du plugin etc...

matthieu51
Timide
Messages : 14
Inscription : 10 déc. 2017, 09:21
Contact :

Re: dépendance et daemon NOK

Message par matthieu51 » 20 déc. 2017, 20:37

Moche la réactivité et réactions des membres soit disant actifs : merci Scanab

Avatar de l’utilisateur
Bosquetia
Actif
Messages : 5833
Inscription : 10 mai 2016, 07:54

Re: dépendance et daemon NOK

Message par Bosquetia » 20 déc. 2017, 20:43

Moche le nombre de personnes qui ne font aucun effort sur une solution DYI...

Raler, profiter critiquer.... l’archétype du boulet quoi !

matthieu51
Timide
Messages : 14
Inscription : 10 déc. 2017, 09:21
Contact :

Re: dépendance et daemon NOK

Message par matthieu51 » 21 déc. 2017, 14:19

Hooo l'intelligence à parlé ! On passe aux insultes ? Je ne rentrerais pas dans ton jeu puéril Bosquetia,
Tu as tout appris seul toi personne n'est venu t'aider. Il vaudrais mieux que certaines personnes se souviennent d'ou ils viennent avant de parler.
Raler ? oui quand nécessaire, Je paye pas pour rien
Profiter ? en effet je profite de la connaissance des autres pour approfondir la mienne.
Critiquer ? oui la critique que quand elle est constructive.

Boulet si ça peut te faire plaisir de le penser, ça m’empêchera pas de dormir lol

Au ,final j'ai trouvé tout seul. Donc maintenant je peux aider ( une vrai aide )

PS : il vaut mieux cloturer ce post hors sujet au final : on dit merci qui ?

Non pas J&M :D

Avatar de l’utilisateur
goofytig
Timide
Messages : 4
Inscription : 01 juin 2018, 14:15

Re: dépendance et daemon NOK

Message par goofytig » 30 juil. 2018, 00:25

Bonsoir,

nouveau sur jeedom et utilisateur avancé sur zibase je migre doucement sur jeedom.

je viens d'acheter ton plugin et j'ai bien des remonté de mes modules mais le démon est ok et dépendances non ok

voici le log:
module.js:549
throw err;
^
Error: Cannot find module 'request'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/var/www/html/plugins/Zibasedom/node/Zibasedom.js:24:15)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
[2018-07-30 00:20:03][ERROR] : Attention : l'installation des dépendances a dépassé le temps maximum autorisé : 30min

ainsi que le zibasedom_dep:
Début de l'installation
Version actuelle : v8.11.1
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:
libc-ares2* libhttp-parser2.8* libuv1* nodejs* nodejs-doc*
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
After this operation, 22.2 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 ... 57833 files and directories currently installed.)
Removing nodejs (8.11.1~dfsg-2~bpo9+1) ...
Removing libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Removing libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Removing libuv1:armhf (1.18.0-3~bpo9+1) ...
Removing nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Utilisation du dépot officiel
================================================================================
================================================================================
DEPRECATION WARNING
Node.js 5.x is no longer actively supported!
You will not receive security or critical stability updates for this version.
You should migrate to a supported version of Node.js as soon as possible.
Use the installation script that corresponds to the version of Node.js you
wish to install. e.g.
* https://deb.nodesource.com/setup_8.x — Node.js 8 LTS "Carbon" (recommended)
* https://deb.nodesource.com/setup_10.x — Node.js 10 Current
Please see https://github.com/nodejs/Release for details about which
version may be appropriate for you.
The NodeSource Node.js distributions repository contains
information both about supported versions of Node.js and supported Linux
distributions. To learn more about usage, see the repository:
https://github.com/nodesource/distributions
================================================================================
================================================================================
Continuing in 20 seconds ...
## Installing the NodeSource Node.js 5.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.3 kB]
Fetched 25.3 kB in 1s (25.2 kB/s)
Reading package lists...
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_5.x/dis ... ch/Release'
## Your distribution, identified as "stretch", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1 nodejs-doc
The following NEW packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1 nodejs nodejs-doc
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:
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/5087 kB of archives.
After this operation, 22.2 MB of additional disk space will be used.
Selecting previously unselected package libc-ares2:armhf.
(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 ... 57685 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.14.0-1~bpo9+1_armhf.deb ...
Unpacking libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Selecting previously unselected package libhttp-parser2.8:armhf.
Preparing to unpack .../libhttp-parser2.8_2.8.1-1~bpo9+1_armhf.deb ...
Unpacking libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Selecting previously unselected package libuv1:armhf.
Preparing to unpack .../libuv1_1.18.0-3~bpo9+1_armhf.deb ...
Unpacking libuv1:armhf (1.18.0-3~bpo9+1) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_8.11.1~dfsg-2~bpo9+1_armhf.deb ...
Unpacking nodejs (8.11.1~dfsg-2~bpo9+1) ...
Selecting previously unselected package nodejs-doc.
Preparing to unpack .../nodejs-doc_8.11.1~dfsg-2~bpo9+1_all.deb ...
Unpacking nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Setting up nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Setting up libuv1:armhf (1.18.0-3~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Setting up libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Setting up nodejs (8.11.1~dfsg-2~bpo9+1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Version actuelle : v8.11.1
/var/www/html/plugins/Zibasedom/resources/nodejs.sh: line 59: npm: command not found
sudo: npm: command not found
sudo: npm: command not found
chmod: cannot access 'bridge': No such file or directory
sudo: npm: command not found
sudo: npm: command not found
sudo: npm: command not found
Fin de l'installation

pensez vous pouvoir faire quelque chose pour moi

merci d'avance

Goofy

neololo_2000
Timide
Messages : 43
Inscription : 06 oct. 2016, 21:01

Re: dépendance et daemon NOK

Message par neololo_2000 » 09 août 2018, 22:12

Bonjour,
je viens vers vous car j'ai, je crois le même problème que goofytig.
Voici mon log Zibasedom_dep:

"Début de l'installation
Version actuelle : v8.11.1
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:
libc-ares2* libhttp-parser2.8* libuv1* nodejs* nodejs-doc*
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
After this operation, 22.2 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 ... 57955 files and directories currently installed.)
Removing nodejs (8.11.1~dfsg-2~bpo9+1) ...
Removing libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Removing libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Removing libuv1:armhf (1.18.0-3~bpo9+1) ...
Removing nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Utilisation du dépot officiel
================================================================================
================================================================================
DEPRECATION WARNING
Node.js 5.x is no longer actively supported!
You will not receive security or critical stability updates for this version.
You should migrate to a supported version of Node.js as soon as possible.
Use the installation script that corresponds to the version of Node.js you
wish to install. e.g.
* https://deb.nodesource.com/setup_8.x — Node.js 8 LTS "Carbon" (recommended)
* https://deb.nodesource.com/setup_10.x — Node.js 10 Current
Please see https://github.com/nodejs/Release for details about which
version may be appropriate for you.
The NodeSource Node.js distributions repository contains
information both about supported versions of Node.js and supported Linux
distributions. To learn more about usage, see the repository:
https://github.com/nodesource/distributions
================================================================================
================================================================================
Continuing in 20 seconds ...
## Installing the NodeSource Node.js 5.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Hit:2 http://archive.raspberrypi.org/debian stretch InRelease
Hit:3 https://deb.nodesource.com/node_6.x stretch InRelease
Reading package lists...
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_5.x/dis ... ch/Release'
## Your distribution, identified as "stretch", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1 nodejs-doc
The following NEW packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1 nodejs nodejs-doc
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:
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/5087 kB of archives.
After this operation, 22.2 MB of additional disk space will be used.
Selecting previously unselected package libc-ares2:armhf.
(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 ... 57807 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.14.0-1~bpo9+1_armhf.deb ...
Unpacking libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Selecting previously unselected package libhttp-parser2.8:armhf.
Preparing to unpack .../libhttp-parser2.8_2.8.1-1~bpo9+1_armhf.deb ...
Unpacking libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Selecting previously unselected package libuv1:armhf.
Preparing to unpack .../libuv1_1.18.0-3~bpo9+1_armhf.deb ...
Unpacking libuv1:armhf (1.18.0-3~bpo9+1) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_8.11.1~dfsg-2~bpo9+1_armhf.deb ...
Unpacking nodejs (8.11.1~dfsg-2~bpo9+1) ...
Selecting previously unselected package nodejs-doc.
Preparing to unpack .../nodejs-doc_8.11.1~dfsg-2~bpo9+1_all.deb ...
Unpacking nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Setting up nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Setting up libuv1:armhf (1.18.0-3~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Setting up libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Setting up nodejs (8.11.1~dfsg-2~bpo9+1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Version actuelle : v8.11.1
/var/www/html/plugins/Zibasedom/resources/nodejs.sh: line 59: npm: command not found
sudo: npm: command not found
sudo: npm: command not found
chmod: cannot access 'bridge': No such file or directory
sudo: npm: command not found
sudo: npm: command not found
sudo: npm: command not found
Fin de l'installation"

J'ai essayé cette méthode :
http://byfeel.info/nodejs-v6-plugin-jee ... pendances/

et à part le message comme quoi c'est optionnel, j'ai toujours des messages du genre "sudo: npm: command not found"
Du coup, j'ai remodifié pour revenir comme au début.
Je précise que j'ai planté récemment mon ssd classique que j'ai remplacé par un msata et une sauvegarde de décembre 2017 (tout ce qui me restait...). J'ai utilisé ce tuto pour y arriver, sans carte sd: viewtopic.php?t=27615

Merci d'avance pour votre aide!

Arkan07
Timide
Messages : 4
Inscription : 11 août 2018, 16:40

Re: dépendance et daemon NOK

Message par Arkan07 » 11 août 2018, 16:43

Bonjour,
je viens également vers vous car j'ai problème.
Mon jeedom était installé sur une MicroSD et depuis les dernières mise à jour j'avais ce problème, je suis reparti de zéro avec une nouvelle installation sur un msata en suivant le tuto sans carte sd: viewtopic.php?t=27615
mais sa n'a pas résolu le problème

Voici mon log Zibasedom_dep:

Début de l'installation
Version actuelle : v8.11.1
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:
libc-ares2* libhttp-parser2.8* libuv1* nodejs* nodejs-doc*
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
After this operation, 22.2 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 ... 57004 files and directories currently installed.)
Removing nodejs (8.11.1~dfsg-2~bpo9+1) ...
Removing libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Removing libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Removing libuv1:armhf (1.18.0-3~bpo9+1) ...
Removing nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Utilisation du dépot officiel
================================================================================
================================================================================
DEPRECATION WARNING
Node.js 5.x is no longer actively supported!
You will not receive security or critical stability updates for this version.
You should migrate to a supported version of Node.js as soon as possible.
Use the installation script that corresponds to the version of Node.js you
wish to install. e.g.
* https://deb.nodesource.com/setup_8.x — Node.js 8 LTS "Carbon" (recommended)
* https://deb.nodesource.com/setup_10.x — Node.js 10 Current
Please see https://github.com/nodejs/Release for details about which
version may be appropriate for you.
The NodeSource Node.js distributions repository contains
information both about supported versions of Node.js and supported Linux
distributions. To learn more about usage, see the repository:
https://github.com/nodesource/distributions
================================================================================
================================================================================
Continuing in 20 seconds ...
## Installing the NodeSource Node.js 5.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Hit:2 http://archive.raspberrypi.org/debian stretch InRelease
Hit:3 https://deb.nodesource.com/node_6.x stretch InRelease
Reading package lists...
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_5.x/dis ... ch/Release'
## Your distribution, identified as "stretch", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1 nodejs-doc
The following NEW packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1 nodejs nodejs-doc
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:
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/5087 kB of archives.
After this operation, 22.2 MB of additional disk space will be used.
Selecting previously unselected package libc-ares2:armhf.
(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 ... 56856 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.14.0-1~bpo9+1_armhf.deb ...
Unpacking libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Selecting previously unselected package libhttp-parser2.8:armhf.
Preparing to unpack .../libhttp-parser2.8_2.8.1-1~bpo9+1_armhf.deb ...
Unpacking libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Selecting previously unselected package libuv1:armhf.
Preparing to unpack .../libuv1_1.18.0-3~bpo9+1_armhf.deb ...
Unpacking libuv1:armhf (1.18.0-3~bpo9+1) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_8.11.1~dfsg-2~bpo9+1_armhf.deb ...
Unpacking nodejs (8.11.1~dfsg-2~bpo9+1) ...
Selecting previously unselected package nodejs-doc.
Preparing to unpack .../nodejs-doc_8.11.1~dfsg-2~bpo9+1_all.deb ...
Unpacking nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Setting up nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Setting up libuv1:armhf (1.18.0-3~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Setting up libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Setting up nodejs (8.11.1~dfsg-2~bpo9+1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Version actuelle : v8.11.1
/var/www/html/plugins/Zibasedom/resources/nodejs.sh: line 59: npm: command not found
sudo: npm: command not found
sudo: npm: command not found
chmod: cannot access 'bridge': No such file or directory
sudo: npm: command not found
sudo: npm: command not found
sudo: npm: command not found
Fin de l'installation

Merci d'avance pour votre aide ;)

neololo_2000
Timide
Messages : 43
Inscription : 06 oct. 2016, 21:01

Re: dépendance et daemon NOK

Message par neololo_2000 » 12 août 2018, 14:38

Salut,
Y aurait-il quelqu'un pour nous donner un coup de pouce, une indication? J'ai l'impression que certain ont réussi à déboguer. Je suis bien embêté avec ça, car je ne sais pas encore si je dois tout réinstaller ou si ça peut se réparer...
S'il vous plait, un peu d'aide :)

Arkan07
Timide
Messages : 4
Inscription : 11 août 2018, 16:40

Re: dépendance et daemon NOK

Message par Arkan07 » 14 août 2018, 01:08

je suis également toujours dans la même situation,
@neololo_2000 réinstaller ne servira a rien je l'ai fais je suis avec une installation toute neuve

neurall
Timide
Messages : 469
Inscription : 25 avr. 2016, 11:39

Re: dépendance et daemon NOK

Message par neurall » 14 août 2018, 08:16

dans vos logs on lit :

Code : Tout sélectionner

## Your distribution, identified as "stretch", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
je pense que c'est clair, votre plugin utilise une version de node.js obsolète qui n'est plus supportée sur la version linux 9.5 (code stretch) que vous installez. c'est au développeur du plugin de vous aider et adapter son plugin pour la version 9.5 linux, peut être qu'en installant à la main node.js puis en relançant l'installation des dépendances...

PS: npm c'est le gestionnaire node.js donc comme il ne s'installe pas l'utilitaire npm est introuvable (cqfd) :

Code : Tout sélectionner

/var/www/html/plugins/Zibasedom/resources/nodejs.sh: line 59: npm: command not found
sur la R9.5 de linux pas de node.js R5 :) => essayed l'installe manuelle de node.js :

Code : Tout sélectionner

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
Jeedom mini+ Z-Wave+
Minix Z83 eMMC 32Mo, Stick Zwave Gen 5, quelques dizaines de modules divers et variés

Avatar de l’utilisateur
Nebz
Actif
Messages : 3465
Inscription : 23 avr. 2017, 01:37
Localisation : Belgique

Re: dépendance et daemon NOK

Message par Nebz » 14 août 2018, 08:23

la version à utiliser est la v8 de nodejs, sinon vous pouvez poser problème aux autres plugins utilisant nodejs !!!!

@scanab Vous n'êtes plus venu sur ce forum depuis 1 mois, je vois que votre plugin utilise toujours la version 5 de nodeJS, merci d'upgrader en V8 car cela peut poser problème aux autre plugins !!! Êtes vous toujours actif ?

@neurall Je me suis permis de modifier votre message pour passer de 6 -> 8
Dev plugin Homebridge

- Fournissez les logs, la capture de vos commandes et vos types génériques svp
- Constructif et bonne humeur, on est pas là pour se lancer des périfs z-wave à la figure :-)

Un petit don ça fait toujours plaisir :)

neololo_2000
Timide
Messages : 43
Inscription : 06 oct. 2016, 21:01

Re: dépendance et daemon NOK

Message par neololo_2000 » 14 août 2018, 18:04

Hello et merci beaucoup pour vos réponses!
J'ai essayé la méthode de Neurall, et pour une fois,je suis arrivé à 100% mais rien n'est installé
Par contre le log n'est plus le même mais il y a tjs un probleme aec npm
"
Début de l'installation
Version actuelle : v8.11.3
KO, version obsolète à upgrader
Suppression du Nodejs existant et installation du paquet recommandé
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
gyp* javascript-common* libc-ares2* libhttp-parser2.8* libjs-inherits*
libjs-jquery* libjs-node-uuid* libjs-underscore* libuv1* libuv1-dev*
node-abbrev* node-ansi* node-ansi-color-table* node-archy* node-async*
node-balanced-match* node-block-stream* node-brace-expansion*
node-builtin-modules* node-combined-stream* node-concat-map*
node-cookie-jar* node-delayed-stream* node-forever-agent* node-form-data*
node-fs.realpath* node-fstream* node-fstream-ignore*
node-github-url-from-git* node-glob* node-graceful-fs* node-gyp*
node-hosted-git-info* node-inflight* node-inherits* node-ini*
node-is-builtin-module* node-isexe* node-json-stringify-safe* node-lockfile*
node-lru-cache* node-mime* node-minimatch* node-mkdirp* node-mute-stream*
node-node-uuid* node-nopt* node-normalize-package-data* node-npmlog*
node-once* node-osenv* node-path-is-absolute* node-pseudomap* node-qs*
node-read* node-read-package-json* node-request* node-retry* node-rimraf*
node-semver* node-sha* node-slide* node-spdx-correct*
node-spdx-expression-parse* node-spdx-license-ids* node-tar*
node-tunnel-agent* node-underscore* node-validate-npm-package-license*
node-which* node-wrappy* node-yallist* nodejs* nodejs-doc* npm*
0 upgraded, 0 newly installed, 75 to remove and 0 not upgraded.
After this operation, 68.8 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 ... 66309 files and directories currently installed.)
Removing node-gyp (3.4.0-1) ...
Removing gyp (0.1+20150913git1f374df9-1) ...
Removing javascript-common (11) ...
Conf javascript-common disabled.
apache2_invoke prerm: Disable configuration javascript-common
Removing node-read-package-json (1.2.4-1) ...
Removing node-lru-cache (4.0.2-1) ...
Removing node-yallist (2.0.0-1) ...
Removing node-fstream-ignore (0.0.6-2) ...
Removing libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Removing libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Removing node-tar (2.2.1-1) ...
Removing node-block-stream (0.0.9-1) ...
Removing libjs-jquery (3.1.1-2) ...
Removing node-request (2.26.1-1) ...
Removing node-node-uuid (1.4.0-1) ...
Removing libjs-node-uuid (1.4.0-1) ...
Removing node-underscore (1.8.3~dfsg-1) ...
Removing libjs-underscore (1.8.3~dfsg-1) ...
Removing libuv1-dev:armhf (1.18.0-3~bpo9+1) ...
Removing libuv1:armhf (1.18.0-3~bpo9+1) ...
Removing node-nopt (3.0.6-3) ...
Removing node-abbrev (1.0.9-1) ...
Removing node-ansi-color-table (1.0.0-1) ...
Removing node-npmlog (0.0.4-1) ...
Removing node-ansi (0.3.0-2) ...
Removing node-archy (1.0.0-1) ...
Removing node-form-data (0.1.0-1) ...
Removing node-async (0.8.0-1) ...
Removing node-normalize-package-data (2.3.5-2) ...
Removing node-is-builtin-module (1.0.0-1) ...
Removing node-builtin-modules (1.1.1-1) ...
Removing node-combined-stream (0.0.5-1) ...
Removing node-cookie-jar (0.3.1-1) ...
Removing node-delayed-stream (0.0.5-1) ...
Removing node-forever-agent (0.5.1-1) ...
Removing node-github-url-from-git (1.4.0-1) ...
Removing node-hosted-git-info (2.1.5-1) ...
Removing node-ini (1.1.0-1) ...
Removing node-which (1.2.11-1) ...
Removing node-isexe (1.1.2-1) ...
Removing node-json-stringify-safe (5.0.0-1) ...
Removing node-lockfile (0.4.1-1) ...
Removing node-mime (1.3.4-1) ...
Removing node-read (1.0.7-1) ...
Removing node-mute-stream (0.0.7-1) ...
Removing node-osenv (0.1.0-1) ...
Removing node-pseudomap (1.0.2-1) ...
Removing node-qs (2.2.4-1) ...
Removing node-retry (0.6.0-1) ...
Removing node-semver (5.3.0-1) ...
Removing node-sha (1.2.3-1) ...
Removing node-slide (1.1.4-1) ...
Removing node-validate-npm-package-license (3.0.1-1) ...
Removing node-spdx-correct (1.0.2-1) ...
Removing node-spdx-expression-parse (1.0.4-1) ...
Removing node-spdx-license-ids (1.2.2-1) ...
Removing node-tunnel-agent (0.3.1-1) ...
Removing nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Removing node-fstream (1.0.10-1) ...
Removing node-rimraf (2.5.4-2) ...
Removing node-glob (7.1.1-1) ...
Removing node-inflight (1.0.6-1) ...
Removing node-inherits (2.0.3-1) ...
Removing libjs-inherits (2.0.3-1) ...
Removing node-minimatch (3.0.3-1) ...
Removing node-brace-expansion (1.1.6-1+deb9u1) ...
Removing node-balanced-match (0.4.2-1) ...
Removing node-concat-map (0.0.1-1) ...
Removing node-fs.realpath (1.0.0-1) ...
Removing node-graceful-fs (4.1.11-1) ...
Removing node-mkdirp (0.5.0-1) ...
Removing node-once (1.4.0-2) ...
Removing node-path-is-absolute (1.0.0-1) ...
Removing node-wrappy (1.0.2-1) ...
Removing nodejs (8.11.3-1nodesource1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
(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 ... 60845 files and directories currently installed.)
Purging configuration files for javascript-common (11) ...
apache2_invoke postrm: Purging state for javascript-common
Purging configuration files for npm (1.4.21+ds-2) ...
Utilisation du dépot officiel
================================================================================
================================================================================
DEPRECATION WARNING
Node.js 5.x is no longer actively supported!
You will not receive security or critical stability updates for this version.
You should migrate to a supported version of Node.js as soon as possible.
Use the installation script that corresponds to the version of Node.js you
wish to install. e.g.
* https://deb.nodesource.com/setup_8.x — Node.js 8 LTS "Carbon" (recommended)
* https://deb.nodesource.com/setup_10.x — Node.js 10 Current
Please see https://github.com/nodejs/Release for details about which
version may be appropriate for you.
The NodeSource Node.js distributions repository contains
information both about supported versions of Node.js and supported Linux
distributions. To learn more about usage, see the repository:
https://github.com/nodesource/distributions
================================================================================
================================================================================
Continuing in 20 seconds ...
## Installing the NodeSource Node.js 5.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.3 kB]
Hit:3 https://deb.nodesource.com/node_8.x stretch InRelease
Fetched 25.3 kB in 1s (18.2 kB/s)
Reading package lists...
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_5.x/dis ... ch/Release'
## Your distribution, identified as "stretch", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
nodejs
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:
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/11.3 MB of archives.
After this operation, 57.5 MB of additional disk space will be used.
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 ... 60840 files and directories currently installed.)
Preparing to unpack .../nodejs_8.11.3-1nodesource1_armhf.deb ...
Unpacking nodejs (8.11.3-1nodesource1) ...
Setting up nodejs (8.11.3-1nodesource1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Version actuelle : v8.11.3
npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead.
npm ERR!
npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
npm ERR! A complete log of this run can be found in:
npm ERR! /var/www/.npm/_logs/2018-08-14T15_57_20_399Z-debug.log
npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead.
npm ERR!
npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-08-14T15_57_22_237Z-debug.log
npm WARN saveError ENOENT: no such file or directory, open '/var/www/html/plugins/Zibasedom/node/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/var/www/html/plugins/Zibasedom/node/package.json'
npm WARN node No description
npm WARN node No repository field.
npm WARN node No README data
npm WARN node No license field.
up to date in 0.272s
chmod: cannot access 'bridge': No such file or directory
npm WARN notice [SECURITY] string has the following vulnerability: 1 high. Go here for more details: https://nodesecurity.io/advisories?sear ... sion=3.3.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
npm WARN saveError ENOENT: no such file or directory, open '/var/www/html/plugins/Zibasedom/node/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/var/www/html/plugins/Zibasedom/node/package.json'
npm WARN node No description
npm WARN node No repository field.
npm WARN node No README data
npm WARN node No license field.
+ string@3.3.3
added 1 package in 1.991s
npm WARN saveError ENOENT: no such file or directory, open '/var/www/html/plugins/Zibasedom/node/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/var/www/html/plugins/Zibasedom/node/package.json'
npm WARN node No description
npm WARN node No repository field.
npm WARN node No README data
npm WARN node No license field.
+ request@2.88.0
added 47 packages in 11.568s
npm WARN saveError ENOENT: no such file or directory, open '/var/www/html/plugins/Zibasedom/node/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/var/www/html/plugins/Zibasedom/node/package.json'
npm WARN node No description
npm WARN node No repository field.
npm WARN node No README data
npm WARN node No license field.
+ xml2js@0.4.19
added 3 packages in 4.741s
Fin de l'installation
"

La solution est elle plus proche qu'avant? J’espère, je croise les doigts! D’Après ce que dit Nebz, notre probleme n'est pas réglable sans le dev ou j'ai mal compris? merci

Avatar de l’utilisateur
Nebz
Actif
Messages : 3465
Inscription : 23 avr. 2017, 01:37
Localisation : Belgique

Re: dépendance et daemon NOK

Message par Nebz » 14 août 2018, 18:06

Tu as bien compris :-)


Envoyé de mon iPhone en utilisant Tapatalk
Dev plugin Homebridge

- Fournissez les logs, la capture de vos commandes et vos types génériques svp
- Constructif et bonne humeur, on est pas là pour se lancer des périfs z-wave à la figure :-)

Un petit don ça fait toujours plaisir :)

neololo_2000
Timide
Messages : 43
Inscription : 06 oct. 2016, 21:01

Re: dépendance et daemon NOK

Message par neololo_2000 » 14 août 2018, 21:29

C'est marrant, mais même si il est mal installé, et statut en Nok, j'ai mes capteurs qui semblent remarcher. Je n'ai plus non plus le popup orange jeedom qui me dit que les dependances ne sera sont pas installé...

neololo_2000
Timide
Messages : 43
Inscription : 06 oct. 2016, 21:01

Re: dépendance et daemon NOK

Message par neololo_2000 » 15 août 2018, 23:24

Arkan07, je pense que tu peux faire la méthode de neurall, l installation des dépendances est en nok mais tout ré fonctionne. On attend maintenant des News du développeur ^^

Répondre

Revenir vers « [Plugin Tiers] Zibasedom »

Qui est en ligne ?

Utilisateurs parcourant ce forum : Aucun utilisateur inscrit et 1 invité