Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Dash Button Adapter lässt sich nicht installieren

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Dash Button Adapter lässt sich nicht installieren

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      martin last edited by

      Hallo!

      Ich wollte gerade den Dash-Button Adapter installieren.

      Da bringt er mir folgendes:

      $ ./iobroker url "https://github.com/PArns/ioBroker.amazon-dash/tarball/master" amazon-dash
install https://github.com/PArns/ioBroker.amazon-dash/tarball/master
npm install https://github.com/PArns/ioBroker.amazon-dash/tarball/master --production --prefix "/opt/iobroker" (System call)
npm
 WARN lifecycle iobroker.amazon-dash@0.2.9~preinstall: cannot run in wd %s %s (wd=%s) iobroker.amazon-dash@0.2.9 apt-get install libpcap-dev -y || true /opt/iobroker/node_modules/.staging/iobroker.amazon-dash-eb5038e9
../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden #include <security pam_appl.h="">
                               ^

compilation terminated.
make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
gyp
 ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.9.59-v7+

gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
gyp ERR! node -v v8.11.3

gyp ERR! node-gyp -v v3.6.0gyp ERR! not ok 

In file included from ../src/dns_sd.cpp:1:0:../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
 #include <dns_sd.h>
                    ^

compilation terminated.
make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)

gyp ERR! System Linux 4.9.59-v7+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/mdns
gyp ERR! node -v v8.11.3
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok 

../pcap_binding.cc:2:23: fatal error: pcap/pcap.h: Datei oder Verzeichnis nicht gefunden #include <pcap pcap.h="">
                       ^
compilation terminated.

make: *** [Release/obj.target/pcap_binding/pcap_binding.o] Fehler 1
gyp
 ERR! build error 
gyp
 ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp 
ERR! stack     at ChildProcess.emit (events.js:214:7)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.9.59-v7+
gyp
 ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/pcap
gyp ERR! node -v v8.11.3
gyp ERR! node-gyp -v v3.6.0
gyp
 ERR! not ok 
npm
 WARN
 optional
 SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install: `node-gyp rebuild`
npm WARN 
optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1npm
 WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.4.0 (node_modules/mdns):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.4.0 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

npm
 ERR! code ELIFECYCLEnpm ERR! errno 1

npm ERR! pcap@2.0.0 install: `node-gyp rebuild`npm ERR! Exit status 1
npm 
ERR! npm ERR! Failed at the pcap@2.0.0 install 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/2018-08-01T19_09_43_177Z-debug.log
ERROR: Cannot parse /opt/iobroker/node_modules/iobroker.js-controller/adapter/amazon-dash/io-package.json:Error: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/adapter/amazon-dash/io-package.json'
process exited with code 0</pcap></dns_sd.h></security>

      Was stimmt da nicht und wie kann ich es beheben?

      1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 last edited by

        Mach mal mit sudo.

        Gesendet vom Handy …

        1 Reply Last reply Reply Quote 0
        • M
          martin last edited by

          Was genau meinst du? Ich gehe im iobroker oben auf das Symbol und wähle Amazon-Dash aus, danach installiert er es ja von selbst.

          Was soll ich jetzt genau mit sudo machen?

          1 Reply Last reply Reply Quote 0
          • J
            JR99 last edited by

            Bei mir installiert sich der amazon Dash Adapter ebenfalls nicht.

            Ich habe es sowohl über die normale Installationsfunktion (also "+" und Hinzufügen) getestet, als auch über die "Installation aus eigener URL", dort dann von GitHub.

            Immer dasselbe Ergebnis (s.u.)

            Sogar eine Installation mit

            npm i iobroker.amazon-dash oder

            sudo npm i iobroker.amazon-dash

            schlägt immer fehl.

            Hier die Protokoll-Ausgabe:

            $ ./iobroker add amazon-dash 
NPM version: 3.10.10
npm install iobroker.amazon-dash --production --save --prefix "/opt/iobroker" (System call)
npm 
WARN addRemoteGit Error: not found: gitnpm WARN addRemoteGit     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
npm WARN addRemoteGit     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
npm WARN addRemoteGit     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
npm WARN addRemoteGit     at FSReqWrap.oncomplete (fs.js:123:15)
npm WARN addRemoteGit  git+https://github.com/bytzdev/node-socketwatcher.git resetting remote /root/.npm/_git-remotes/git-https-github-com-bytzdev-node-socketwatcher-git-e2de02de because of error: { Error: not found: git
npm WARN addRemoteGit     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
npm WARN addRemoteGit     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
npm WARN addRemoteGit     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
npm WARN addRemoteGit     at FSReqWrap.oncomplete (fs.js:123:15) code: 'ENOGIT' }
npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/bytzdev/node-socketwatcher.git /root/.npm/_git-remotes/git-https-github-com-bytzdev-node-socketwatcher-git-e2de02de: undefined
npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/bytzdev/node-socketwatcher.git /root/.npm/_git-remotes/git-https-github-com-bytzdev-node-socketwatcher-git-e2de02de: undefined
npm ERR! Linux 4.9.0-6-amd64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.amazon-dash" "--production" "--save" "--prefix" "/opt/iobroker"
npm ERR! node v6.12.3
npm ERR! npm  v3.10.10
npm ERR! code ENOGIT

npm ERR! not found: git
npm 
ERR! npm ERR!
 Failed using git.npm ERR! This is most likely not a problem with npm itself.
npm ERR! Please check if you have git installed and in your PATH.

npm ERR! Please include the following file with any support request:npm ERR!     /opt/npm-debug.log

            Irgendwie scheint es ein Problem mit git zu geben.

            Irgendwelce Tipps?

            Andere Adapter lassen sich völlig problemlos installieren und aktualisieren, nur der Dash eben nicht.

            Gruß

            Ralf

            1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators last edited by

              @JR99:

              Irgendwie scheint es ein Problem mit git zu geben. `
              Korrekt: Not found!

              @JR99:

              Irgendwelce Tipps? `
              Yepp:

              sudo apt install git

              Gruß

              Rainer

              1 Reply Last reply Reply Quote 0
              • M
                martin last edited by 

                /opt/iobroker$ sudo apt install git

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

Paketlisten werden gelesen...

Abhängigkeitsbaum wird aufgebaut....

Statusinformationen werden eingelesen....

git ist schon die neueste Version (1:2.11.0-3+deb9u3).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 264 nicht aktualisiert.
/opt/iobroker$  

                $ ./iobroker url "https://github.com/PArns/ioBroker.amazon-dash/tarball/master" amazon-dash
install https://github.com/PArns/ioBroker.amazon-dash/tarball/master
npm install https://github.com/PArns/ioBroker.amazon-dash/tarball/master --production --prefix "/opt/iobroker" (System call)
npm WARN lifecycle iobroker.amazon-dash@0.2.9~preinstall: cannot run in wd %s %s (wd=%s) iobroker.amazon-dash@0.2.9 apt-get install libpcap-dev -y || true /opt/iobroker/node_modules/.staging/iobroker.amazon-dash-eb5038e9
../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden #include <security pam_appl.h="">
                               ^

compilation terminated.
make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
gyp
 ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)

gyp ERR! System Linux 4.9.59-v7+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
gyp ERR! node -v v8.11.3
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok 

In file included from ../src/dns_sd.cpp:1:0:../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
 #include <dns_sd.h>
                    ^
compilation terminated.

make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
gyp
 ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.9.59-v7+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/mdns
gyp ERR! node -v v8.11.3
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok 

../pcap_binding.cc:2:23: fatal error: pcap/pcap.h: Datei oder Verzeichnis nicht gefunden #include <pcap pcap.h="">
                       ^
compilation terminated.

make: *** [Release/obj.target/pcap_binding/pcap_binding.o] Fehler 1
gyp
 ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp
 ERR!
 System
 Linux 4.9.59-v7+gyp

ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/pcap
gyp ERR! node -v v8.11.3
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok 

npm
 WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

npm
 WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.4.0 (node_modules/mdns):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.4.0 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

npm
 ERR! code ELIFECYCLEnpm ERR! errno 1
npm

ERR! pcap@2.0.0 install: `node-gyp rebuild`npm ERR! Exit status 1

npm
 ERR! npm ERR! Failed at the pcap@2.0.0 install 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/2018-08-04T18_32_34_614Z-debug.log

ERROR: Cannot parse /opt/iobroker/node_modules/iobroker.js-controller/adapter/amazon-dash/io-package.json:Error: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/adapter/amazon-dash/io-package.json'
process exited with code 0</pcap></dns_sd.h></security>
                1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 last edited by

                  Das muss mit —unsafe-perm installiert werden in dem Fall.

                  Bitte manuell per npm installieren und nicht per Admin und den genannten Parameter mit angeben. Und issue bei js-controller anlegen das der Adapter das braucht. Dann kommt er auf die Liste.

                  Gesendet vom Handy …

                  1 Reply Last reply Reply Quote 0
                  • M
                    martin last edited by

                    Und wie genau mache ich das? Kenne mich da leider nicht so gut aus.

                    1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 last edited by 

                      npm install https://github.com/PArns/ioBroker.amazon-dash/tarball/master --production --prefix "/opt/iobroker" --unsafe-perm
                      1 Reply Last reply Reply Quote 0
                      • apollon77
                        apollon77 last edited by

                        js-controller 1.5.0 macht das dann später automatisch.

                        1 Reply Last reply Reply Quote 0
                        • M
                          martin last edited by

                          Klappt leider immer noch nicht.

                          > iobroker.amazon-dash@0.2.9 preinstall /opt/iobroker/node_modules/.staging/iobroker.amazon-dash-eb5038e9
> apt-get install libpcap-dev -y || true

Paketlisten werden gelesen...

Abhängigkeitsbaum wird aufgebaut....

Statusinformationen werden eingelesen....

The following additional packages will be installed:
  libpcap0.8 libpcap0.8-dev
Die folgenden NEUEN Pakete werden installiert:
  libpcap-dev libpcap0.8 libpcap0.8-dev
0 aktualisiert, 3 neu installiert, 0 zu entfernen und 264 nicht aktualisiert.
Es müssen 369 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 916 kB Plattenplatz zusätzlich benutzt.
Holen:1 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf libpcap0.8 armhf 1.8.1-3 [123 kB]
Holen:2 http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian stretch/main armhf libpcap0.8-dev armhf 1.8.1-3 [220 kB]
Holen:3 http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian stretch/main armhf libpcap-dev all 1.8.1-3 [25,4 kB]
debconf: kann Oberfläche nicht initialisieren: Dialog
debconf: (Die Dialog-Oberfläche funktioniert nicht auf einem Dumb-Terminal, einem Emacs-Shellbuffer oder ohne ein steuerndes Terminal.)
debconf: greife zurück auf die Oberfläche: Readline
debconf: kann Oberfläche nicht initialisieren: Readline
debconf: (Diese Oberfläche bedarf eines steuernden Terminals.)
debconf: greife zurück auf die Oberfläche: Teletype
dpkg-preconfigure: kann Stdin nicht wieder öffnen: 
Es wurden 369 kB in 0 s geholt (385 kB/s).
Vormals nicht ausgewähltes Paket libpcap0.8:armhf wird gewählt.
(Lese Datenbank ...
(Lese Datenbank ... 5% (Lese Datenbank ... 10%
(Lese Datenbank ... 15% (Lese Datenbank ... 20% (Lese Datenbank ... 25% (Lese Datenbank ... 30% (Lese Datenbank ... 35% (Lese Datenbank ... 40% (Lese Datenbank ... 45% (Lese Datenbank ... 50% (Lese Datenbank ... 55%
(Lese Datenbank ... 60%
(Lese Datenbank ... 65%
(Lese Datenbank ... 70%
(Lese Datenbank ... 75%
(Lese Datenbank ... 80%
(Lese Datenbank ... 85%
(Lese Datenbank ... 90%
(Lese Datenbank ... 95%
(Lese Datenbank ... 100% (Lese Datenbank ...
120689 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libpcap0.8_1.8.1-3_armhf.deb ...
Entpacken von libpcap0.8:armhf (1.8.1-3) ...
Vormals nicht ausgewähltes Paket libpcap0.8-dev wird gewählt.

Vorbereitung zum Entpacken von .../libpcap0.8-dev_1.8.1-3_armhf.deb ...

Entpacken von libpcap0.8-dev (1.8.1-3) ...

Vormals nicht ausgewähltes Paket libpcap-dev wird gewählt.
Vorbereitung zum Entpacken von .../libpcap-dev_1.8.1-3_all.deb ...
Entpacken von libpcap-dev (1.8.1-3) ...
Trigger für libc-bin (2.24-11+deb9u1) werden verarbeitet ...
Trigger für man-db (2.7.6.1-2) werden verarbeitet ...
libpcap0.8:armhf (1.8.1-3) wird eingerichtet ...
libpcap0.8-dev (1.8.1-3) wird eingerichtet ...
libpcap-dev (1.8.1-3) wird eingerichtet ...
Trigger für libc-bin (2.24-11+deb9u1) werden verarbeitet ...

> socketwatcher@0.3.0 install /opt/iobroker/node_modules/socketwatcher
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/socketwatcher/build“ wird betreten
  CXX(target) Release/obj.target/socketwatcher/socket_watcher.o
  SOLINK_MODULE(target) Release/obj.target/socketwatcher.node
  COPY Release/socketwatcher.node
make: Verzeichnis „/opt/iobroker/node_modules/socketwatcher/build“ wird verlassen

> authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird betreten
  CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o
../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden
#include <security pam_appl.h="">^
compilation terminated.
authenticate_pam.target.mk:93: die Regel für Ziel „Release/obj.target/authenticate_pam/authenticate_pam.o“ scheiterte
make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird verlassen
make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
gyp ERR! build error 
gyp
ERR!
stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.9.59-v7+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
gyp ERR! node -v v8.11.3
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok 

> mdns@2.4.0 install /opt/iobroker/node_modules/mdns
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/mdns/build“ wird betreten
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
In file included from ../src/dns_sd.cpp:1:0:
../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
#include <dns_sd.h>^
compilation terminated.
dns_sd_bindings.target.mk:150: die Regel für Ziel „Release/obj.target/dns_sd_bindings/src/dns_sd.o“ scheiterte
make: Verzeichnis „/opt/iobroker/node_modules/mdns/build“ wird verlassen
make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
gyp
ERR! build error 
gyp
ERR! stack Error: `make` failed with exit code: 2
gyp ERR!
stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp
ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp
ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp
ERR! System Linux 4.9.59-v7+
gyp
ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp
ERR! cwd /opt/iobroker/node_modules/mdns
gyp ERR! node -v v8.11.3
gyp ERR! node-gyp -v
v3.6.0
gyp ERR!
not ok 

> pcap@2.0.0 install /opt/iobroker/node_modules/pcap
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/pcap/build“ wird betreten
  CXX(target) Release/obj.target/pcap_binding/pcap_binding.o
  CXX(target) Release/obj.target/pcap_binding/pcap_session.o
  SOLINK_MODULE(target) Release/obj.target/pcap_binding.node
  COPY Release/pcap_binding.node
make: Verzeichnis „/opt/iobroker/node_modules/pcap/build“ wird verlassen
iobroker@1.0.0 /opt/iobroker
└─┬ iobroker.amazon-dash@0.2.9 
  └─┬ pcap@2.0.0 
    └── socketwatcher@0.3.0  (git+https://github.com/bytzdev/node-socketwatcher.git#d252d3f8c45f565a0a48ebd155d4f9e4666798d9)

npm
WARN
optional
SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam):
npm
WARN
optional
SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install: `node-gyp rebuild`
npm
WARN
optional
SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm
WARN
optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.4.0 (node_modules/mdns):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.4.0 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
connection lost .................................
/opt/iobroker$</dns_sd.h></security>
                          1 Reply Last reply Reply Quote 0
                          • apollon77
                            apollon77 last edited by

                            Installatiion ist aber erfolgreich durch. Die Fehler kommen von optionalen Paketen.

                            Probier mal

                            1 Reply Last reply Reply Quote 0
                            • M
                              martin last edited by

                              Inzwischen ist der Dash-Button-Adapter auch da. Nach der Installation war er noch nicht da.

                              Vielen Dank für eure Hilfe.

                              Ich werde es die nächsten Tage mal testen.

                              Eine Frage noch zum Dash-Button. Soll man mit dem 1 Bestellung bei Amazon tätigen um den Kaufpreis gutgeschrieben zu kriegen oder gleich im iobroker integrieren?

                              1 Reply Last reply Reply Quote 0
                              • Chaot
                                Chaot last edited by

                                Ich habe mehrere Fehlermeldungen bei der Installation, aber am Ende kommt immer die Meldung Adapter installiert mit Code 0 - also sollte das erfolgreich gewesen sein.

                                Der Adapter startet, wird ganz kurz grün und dann rot.

                                Log:

                                host.haus	2018-08-11 23:33:58.158	info	Restart adapter system.adapter.amazon-dash.0 because enabled
host.haus	2018-08-11 23:33:58.158	error	instance system.adapter.amazon-dash.0 terminated with code 0 (OK)
Caught	2018-08-11 23:33:58.158	error	by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)
Caught	2018-08-11 23:33:58.158	error	by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
Caught	2018-08-11 23:33:58.157	error	by controller[0]: at Socket. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)
Caught	2018-08-11 23:33:58.157	error	by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4659:18)
Caught	2018-08-11 23:33:58.157	error	by controller[0]: at Adapter.emit (events.js:208:7)
Caught	2018-08-11 23:33:58.157	error	by controller[0]: at emitNone (events.js:106:13)
Caught	2018-08-11 23:33:58.157	error	by controller[0]: at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.amazon-dash/main.js:42:5)
Caught	2018-08-11 23:33:58.157	error	by controller[0]: at main (/opt/iobroker/node_modules/iobroker.amazon-dash/main.js:78:29)
Caught	2018-08-11 23:33:58.157	error	by controller[0]: at Object.exports.createSession (/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/pcap.js:123:12)
Caught	2018-08-11 23:33:58.157	error	by controller[0]: at new PcapSession (/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/pcap.js:49:39)
Caught	2018-08-11 23:33:58.156	error	by controller[0]: Error: socket: Operation not permitted
amazon-dash.0	2018-08-11 23:33:58.137	info	terminating
amazon-dash.0	2018-08-11 23:33:58.124	info	cleaned everything up...
amazon-dash.0	2018-08-11 23:33:58.123	error	at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)
amazon-dash.0	2018-08-11 23:33:58.123	error	at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
amazon-dash.0	2018-08-11 23:33:58.123	error	at Socket. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:710:25)
amazon-dash.0	2018-08-11 23:33:58.123	error	at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4659:18)
amazon-dash.0	2018-08-11 23:33:58.123	error	at Adapter.emit (events.js:208:7)
amazon-dash.0	2018-08-11 23:33:58.123	error	at emitNone (events.js:106:13)
amazon-dash.0	2018-08-11 23:33:58.123	error	at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.amazon-dash/main.js:42:5)
amazon-dash.0	2018-08-11 23:33:58.123	error	at main (/opt/iobroker/node_modules/iobroker.amazon-dash/main.js:78:29)
amazon-dash.0	2018-08-11 23:33:58.123	error	at Object.exports.createSession (/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/pcap.js:123:12)
amazon-dash.0	2018-08-11 23:33:58.123	error	at new PcapSession (/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/pcap.js:49:39)
amazon-dash.0	2018-08-11 23:33:58.123	error	Error: socket: Operation not permitted
amazon-dash.0	2018-08-11 23:33:58.123	error	uncaught exception: socket: Operation not permitted
amazon-dash.0	2018-08-11 23:33:58.116	info	starting pcap session on default interface
amazon-dash.0	2018-08-11 23:33:58.111	info	starting. Version 0.2.9 in /opt/iobroker/node_modules/iobroker.amazon-dash, node: v8.11.3
amazon-dash.0	2018-08-11 23:33:58.083	info	States connected to redis: 127.0.0.1:6379</anonymous></anonymous></anonymous></anonymous>
                                1 Reply Last reply Reply Quote 0
                                • apollon77
                                  apollon77 last edited by

                                  Unter welchem User läuft denn drin ioBroker?

                                  Operation not permitted weißt an sich auf User/rechte Themen hin.

                                  Gesendet vom Handy …

                                  1 Reply Last reply Reply Quote 0
                                  • Chaot
                                    Chaot last edited by

                                    Der läuft als Admin.

                                    Kann ich die Rechte ändern? Wie funktioniert das?

                                    1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 last edited by

                                      Admin? Du meinst root?

                                      Gesendet vom Handy …

                                      1 Reply Last reply Reply Quote 0
                                      • Chaot
                                        Chaot last edited by

                                        Ok, jetzt wird es vermutlich kompliziert

                                        Der im Adapter eingesetzte Nutzer nennt sich Admin.

                                        Allerdings scheint der keine Root-Rechte zu haben wenn ich m ir die Fehlermeldungen bei der Adapterinstallation so anschaue. "…missing permission..."

                                        Wie bekomme ich den Adapter bzw. ioBroker dazu das er rootRechte hat?

                                        Braucht er die zwingend?

                                        ...

                                        Ach, und warum hat der Adapter vorher funktioniert?

                                        1 Reply Last reply Reply Quote 0
                                        • Chaot
                                          Chaot last edited by

                                          :roll: :roll: :roll:

                                          Ich vergesse das immer wieder :roll: :roll: :roll: :roll:

                                          Update des JS Controler und der Dash läuft. :idea:

                                          1 Reply Last reply Reply Quote 0
                                          • Chaot
                                            Chaot last edited by

                                            Nach dem letzten Update des JS-Controlers auf 1.5.3

                                            funktionieren die blöden Dash Button wieder mal nicht:

                                            host.haus	2018-09-15 22:37:51.275	error	instance system.adapter.amazon-dash.0 terminated with code 0 (OK)
Caught	2018-09-15 22:37:51.275	error	by controller[0]: at Socket.that.getForeignObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:869:25)
Caught	2018-09-15 22:37:51.275	error	by controller[0]: at createInstancesObjects (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:830:13)
Caught	2018-09-15 22:37:51.275	error	by controller[0]: at createInstancesObjects (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:869:54)
Caught	2018-09-15 22:37:51.275	error	by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5290:18)
Caught	2018-09-15 22:37:51.275	error	by controller[0]: at Adapter.emit (events.js:208:7)
Caught	2018-09-15 22:37:51.275	error	by controller[0]: at emitNone (events.js:106:13)
Caught	2018-09-15 22:37:51.275	error	by controller[0]: at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.amazon-dash/main.js:42:5)
Caught	2018-09-15 22:37:51.275	error	by controller[0]: at main (/opt/iobroker/node_modules/iobroker.amazon-dash/main.js:78:29)
Caught	2018-09-15 22:37:51.274	error	by controller[0]: at Object.exports.createSession (/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/pcap.js:123:12)
Caught	2018-09-15 22:37:51.274	error	by controller[0]: at new PcapSession (/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/pcap.js:49:39)
Caught	2018-09-15 22:37:51.274	error	by controller[0]: Error: socket: Operation not permitted
host.haus	2018-09-15 22:37:50.499	info	instance system.adapter.amazon-dash.0 started with pid 2380</anonymous>
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            455
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            6
                                            23
                                            2852
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo