NEWS
Problem beim harmony Installation
-
nicht````
ping auf 8.8.8.8nurping 8.8.8.8
Wird aber gehen und DNS scheint ja auch zu klappen. Kannst du mal das machen:ping github.com
Und hast du mal versucht das LTX zu installieren? Wenn ja bitte log posten in Code und Spoiler. -
root@ioBroker-Pi:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=60 time=13.5 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=60 time=12.7 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=13.1 ms ^C --- 8.8.8.8 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 12.781/13.159/13.517/0.300 msroot@ioBroker-Pi:~# ping github.com ping: github.com: Temporärer Fehler bei der Namensauflösung root@ioBroker-Pi:~#root@ioBroker-Pi:~# sudo npm install ltx /root └── ltx@2.7.1 npm WARN enoent ENOENT: no such file or directory, open '/root/package.json' npm WARN root No description npm WARN root No repository field. npm WARN root No README data npm WARN root No license field.! root@ioBroker-Pi:~# root@ioBroker-Pi:~# sudo npm install ltx
! -bash: root@ioBroker-Pi:~#: Kommando nicht gefunden.
! root@ioBroker-Pi:~# /root
! -bash: /root: Ist ein Verzeichnis
! root@ioBroker-Pi:~# └── ltx@2.7.1
! -bash: └──: Kommando nicht gefunden.
! root@ioBroker-Pi:~#
! root@ioBroker-Pi:~# npm WARN enoent ENOENT: no such file or directory, open '/root/package.json'
! Usage: npm<command></command>
! where <command></command>is one of:
! access, adduser, bin, bugs, c, cache, completion, config,
! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
! explore, get, help, help-search, i, init, install,
! install-test, it, link, list, ln, login, logout, ls,
! outdated, owner, pack, ping, prefix, prune, publish, rb,
! rebuild, repo, restart, root, run, run-script, s, se,
! search, set, shrinkwrap, star, stars, start, stop, t, team,
! test, tst, un, uninstall, unpublish, unstar, up, update, v,
! version, view, whoami
! npm <command></command>-h quick help on<command></command>
! npm -l display full usage info
! npm help <term>search for help on <term>npm help npm involved overview
! Specify configs in the ini-formatted file:
! /root/.npmrc
! or on the command line via: npm <command></command>–key value
! Config info can be viewed via: npm help config
! npm@4.6.1 /usr/local/lib/node_modules/npm
! root@ioBroker-Pi:~# npm WARN root No description
! Usage: npm<command></command>
! where <command></command>is one of:
! access, adduser, bin, bugs, c, cache, completion, config,
! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
! explore, get, help, help-search, i, init, install,
! install-test, it, link, list, ln, login, logout, ls,
! outdated, owner, pack, ping, prefix, prune, publish, rb,
! rebuild, repo, restart, root, run, run-script, s, se,
! search, set, shrinkwrap, star, stars, start, stop, t, team,
! test, tst, un, uninstall, unpublish, unstar, up, update, v,
! version, view, whoami
! npm <command></command>-h quick help on<command></command>
! npm -l display full usage info
! npm help <term>search for help on <term>npm help npm involved overview
! Specify configs in the ini-formatted file:
! /root/.npmrc
! or on the command line via: npm <command></command>--key value
! Config info can be viewed via: npm help config
! npm@4.6.1 /usr/local/lib/node_modules/npm
! root@ioBroker-Pi:~# npm WARN root No repository field.
! Usage: npm<command></command>
! where <command></command>is one of:
! access, adduser, bin, bugs, c, cache, completion, config,
! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
! explore, get, help, help-search, i, init, install,
! install-test, it, link, list, ln, login, logout, ls,
! outdated, owner, pack, ping, prefix, prune, publish, rb,
! rebuild, repo, restart, root, run, run-script, s, se,
! search, set, shrinkwrap, star, stars, start, stop, t, team,
! test, tst, un, uninstall, unpublish, unstar, up, update, v,
! version, view, whoami
! npm <command></command>-h quick help on<command></command>
! npm -l display full usage info
! npm help <term>search for help on <term>npm help npm involved overview
! Specify configs in the ini-formatted file:
! /root/.npmrc
! or on the command line via: npm <command></command>--key value
! Config info can be viewed via: npm help config
! npm@4.6.1 /usr/local/lib/node_modules/npm
! root@ioBroker-Pi:~# npm WARN root No README data
! Usage: npm<command></command>
! where <command></command>is one of:
! access, adduser, bin, bugs, c, cache, completion, config,
! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
! explore, get, help, help-search, i, init, install,
! install-test, it, link, list, ln, login, logout, ls,
! outdated, owner, pack, ping, prefix, prune, publish, rb,
! rebuild, repo, restart, root, run, run-script, s, se,
! search, set, shrinkwrap, star, stars, start, stop, t, team,
! test, tst, un, uninstall, unpublish, unstar, up, update, v,
! version, view, whoami
! npm <command></command>-h quick help on<command></command>
! npm -l display full usage info
! npm help <term>search for help on <term>npm help npm involved overview
! Specify configs in the ini-formatted file:
! /root/.npmrc
! or on the command line via: npm <command></command>--key value
! Config info can be viewed via: npm help config
! npm@4.6.1 /usr/local/lib/node_modules/npm
! root@ioBroker-Pi:~# npm WARN root No license field.
! Usage: npm<command></command>
! where <command></command>is one of:
! access, adduser, bin, bugs, c, cache, completion, config,
! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
! explore, get, help, help-search, i, init, install,
! install-test, it, link, list, ln, login, logout, ls,
! outdated, owner, pack, ping, prefix, prune, publish, rb,
! rebuild, repo, restart, root, run, run-script, s, se,
! search, set, shrinkwrap, star, stars, start, stop, t, team,
! test, tst, un, uninstall, unpublish, unstar, up, update, v,
! version, view, whoami
! npm <command></command>-h quick help on<command></command>
! npm -l display full usage info
! npm help <term>search for help on <term>npm help npm involved overview
! Specify configs in the ini-formatted file:
! /root/.npmrc
! or on the command line via: npm <command></command>--key value
! Config info can be viewed via: npm help config
! npm@4.6.1 /usr/local/lib/node_modules/npm
! root@ioBroker-Pi:~# root@ioBroker-Pi:~#
! -bash: root@ioBroker-Pi:~#: Kommando nicht gefunden.</term></term></term></term></term></term></term></term></term></term>Ich hoffe das ist das was Du wolltest:-)
-
hier nochmal ping Google.de
root@ioBroker-Pi:~# ping google.de PING google.de(fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003)) 56 data bytes 64 bytes from fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003): icmp_seq=1 ttl=56 time=14.6 ms 64 bytes from fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003): icmp_seq=2 ttl=56 time=13.3 ms 64 bytes from fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003): icmp_seq=3 ttl=56 time=13.6 ms 64 bytes from fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003): icmp_seq=4 ttl=56 time=13.4 ms ^C --- google.de ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 13.398/13.797/14.646/0.500 ms -
@dpt:ich musste unter dem Raspi immer für die Harmony erst ein
sudo apt-get install git
machen, dann klappte es `
Du bist ein Schatz! :mrgreen:Ich hatte genau das gleiche Problem wie der TE.
! ````
$ ./iobroker add harmony --host ioBroker-RasPi
NPM version: 4.6.1
npm install iobroker.harmony --production --save --prefix "/opt/iobroker" (System call)
npmWARN addRemoteGit Error: not found: gitnpm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21)
npm WARN addRemoteGit git+https://github.com/swissmanu/ltx.git#cdata-for-ltx-parser resetting remote /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b because of error: { Error: not found: git
npm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16! npm WARN
addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21) code: 'ENOGIT' }
! npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefinednpm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefined
! npm WARN deprecated node-xmpp-stanza@1.1.0: use @xmpp/xml package <https: www.npmjs.com/package/@xmpp/xml="">
npm
ERR! code ENOGIT
npmERR! 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!
A complete log of this run can be found in:npm
ERR!
/root/.npm/_logs/2018-09-19T08_47_13_892Z-debug.log
host.ioBroker-RasPi install adapter harmony
NPM version: 4.6.1
npm install iobroker.harmony --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:13:12)
npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21)
npm WARN addRemoteGit git+https://github.com/swissmanu/ltx.git#cdata-for-ltx-parser resetting remote /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b because of error: { Error: not found: git
npm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
npm
WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21) code: 'ENOGIT' }
! npm
ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefinednpm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefined
! npm
WARN deprecated node-xmpp-stanza@1.1.0: use @xmpp/xml package <https: www.npmjs.com/package/@xmpp/xml="">
npm
ERR! code ENOGIT
npm ERR! not found: gitnpm 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! A complete log of this run can be found in:npm ERR! /root/.npm/_logs/2018-09-19T08_47_39_138Z-debug.log
! host.ioBroker-RasPi install adapter harmony
NPM version: 4.6.1npm install iobroker.harmony --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:13:12)
npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21)
npm WARN addRemoteGit git+https://github.com/swissmanu/ltx.git#cdata-for-ltx-parser resetting remote /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b because of error: { Error: not found: git
npm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21) code: 'ENOGIT' }
! npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefinednpm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefined
! npm WARN deprecated node-xmpp-stanza@1.1.0: use @xmpp/xml package <https: www.npmjs.com/package/@xmpp/xml="">
npm ERR! code ENOGIT
npm ERR! not found: gitnpm 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! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-09-19T08_48_03_605Z-debug.log
! host.ioBroker-RasPi install adapter harmony
ERROR: host.ioBroker-RasPi Cannot install harmony
ERROR: process exited with code 13</https:></https:></https:>Nach deinem ****sudo apt-get install git**** kam bei der Installation dann zwar ne andere Fehlermeldung, aber dann hat er offenbar von einer anderen Alternativquelle installiert und jetzt läufts.
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden