NEWS
Gelöst Multihost
-
Hallo Paul, danke für deine Zeit:
Host:
root@iobroker:~# node -v v6.13.1 root@iobroker:~# nodejs -v v6.13.1 root@iobroker:~# npm -v 3.10.10Slave:
pi@IOBROKER1:/opt/iobroker $ node -v v8.11.3 pi@IOBROKER1:/opt/iobroker $ nodejs -v v8.11.3 pi@IOBROKER1:/opt/iobroker $ npm -v 5.6.0Okay. Soviel dazu :)
Welche Version ist denn "besser"? Ich weis immer nie welche zueinander passen.
Ich gehe auf beiden Systemen nach https://forum.iobroker.net/viewtopic.php?t=1702 Schema weiter vor?
-
Host ist in Ordnung, aber bitte <u>nicht</u> per apt-get update && apt-get upgrade aktualisieren, denn dann passiert Schlimmes.
@Chris76:pi@IOBROKER1:/opt/iobroker $ npm -v 5.6.0 ```` `Die NPM-Version auf dem Slave ist böse. Bitte downgrade (als User root, sonst mit sudo davor)
npm install -g npm@4 -
Na das läuft ja wieder bei mir :(
Wie gesagt, ist das fertige Raspberry Image von der offiziellen Downloadseite.
pi@IOBROKER1:/opt/iobroker $ sudo npm install -g npm@4 npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EAI_AGAIN: request to https://registry.npmjs.org/npm failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443 npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation. npm ERR! code EAI_AGAIN npm ERR! errno EAI_AGAIN npm ERR! request to https://registry.npmjs.org/npm/-/npm-4.6.1.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443 npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2018-07-28T09_20_32_065Z-debug.log0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'install', '-g', 'npm@4' ] 2 info using npm@5.6.0 3 info using node@v8.11.3 4 verbose npm-session 4fb9e04b9984f859 5 silly install loadCurrentTree 6 silly install readGlobalPackageData 7 warn registry Unexpected warning for https://registry.npmjs.org/: Miscellaneo$ 8 warn registry Using stale package data from https://registry.npmjs.org/ due t$ 9 http fetch GET 200 https://registry.npmjs.org/npm 20276ms (from cache) 10 silly pacote range manifest for npm@4 fetched in 20522ms 11 silly install loadIdealTree 12 silly install cloneCurrentTreeToIdealTree 13 silly install loadShrinkwrap 14 silly install loadAllDepsIntoIdealTree 15 silly resolveWithNewModule npm@4.6.1 checking installable status 16 silly pacote trying https://registry.npmjs.org/npm/-/npm-4.6.1.tgz by hash: $ 17 silly pacote data for sha1-+Osa0A3FilUUNjtBylNCgX8L1kY= not present. Using m$ 18 verbose type system -
Das später versuchen machte mit skeptisch. Okay. War ein DNS Problem auf dem Slave.
Downgrade hat funktionier. Reboot.
Anschließend wieder
sudo iobroker multihost browse 1 | 192.168.5.151 | host | 192.168.5.151 | "authentication required" pi@IOBROKER1:~ $ sudo iobroker multihost connect 1 | 192.168.5.151 | host | 192.168.5.151 | "authentication required" Please select host [1]: 1 Enter secret phrase for connection: ******** Config ok. Please restart ioBroker: "iobroker restart" pi@IOBROKER1:~ $ sudo iobroker restart Stopping iobroker controller daemon... iobroker controller daemon stopped. Starting iobroker controller daemon... iobroker controller daemon started. PID: 1472Aber leider erscheint der Slave nach wie vor nicht auf dem Host.
-
Danke Dir trotzdem für die Hilfe.
Hab gerade in https://forum.iobroker.net/viewtopic.php?f=17&t=7650&sid=59a39d18bb0f5860f5d650b42f103bf1&start=20 noch was gefunden:
Master iobroker.json
{ "system": { "memoryLimitMB": 0, "hostname": "" }, "network": { "IPv4": true, "IPv6": true, "bindAddress": null, "useSystemNpm": true }, "objects": { "type": "file", "typeComment": "Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].", "host": "0.0.0.0", "port": 9001, "user": "", "pass": "", "noFileCache": false, "connectTimeout": 2000 }, "states": { "type": "file", "typeComment": "Possible values: 'file' - [port 9000], 'redis' - [port 6379].", "host": "0.0.0.0", "port": 9000, "maxQueue": 1000, "options": { "auth_pass": null, "retry_max_delay": 15000 } }, "log": { "level": "info", "maxDays": 7, "noStdout": true, "transport": { "file1": { "type": "file", "enabled": true, "filename": "log/iobroker", "fileext": ".log", "maxsize": null, "maxFiles": null }, "syslog1": { "type": "syslog", "enabled": false, "host": "localhost", "host_comment": "The host running syslogd, defaults to localhost.", "port_comment": "The port on the host that syslog is running on, defaults to syslogd's default port(514/UDP).", "protocol": "udp4", "protocol_comment": "The network protocol to log over (e.g. tcp4, udp4, unix, unix-connect, etc).", "path_comment": "The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).", "facility_comment": "Syslog facility to use (Default: local0).", "localhost": "iobroker", "localhost_comment": "Host to indicate that log messages are coming from (Default: localhost).", "sysLogType_comment": "The type of the syslog protocol to use (Default: BSD).", "app_name_comment": "The name of the application (Default: process.title).", "eol_comment": "The end of line character to be added to the end of the message (Default: Message without modifications)." } } }, "dataDirComment": "Always relative to iobroker.js-controller/", "dataDir": "../../iobroker-data/", "multihostService": { "enabled": true, "secure": true, "password": "HIERSTEHTEINPW" }node -v v6.13.1 root@iobroker:/opt/iobroker/iobroker-data# nodejs -v v6.13.1 root@iobroker:/opt/iobroker/iobroker-data# npm -v 4.6.1Slave
{ "system": { "memoryLimitMB": 0, "hostname": "" }, "multihostService": { "enabled": false, "secure": true }, "network": { "IPv4": true, "IPv6": true, "bindAddress": null, "useSystemNpm": true }, "objects": { "type": "file", "typeComment": "Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].", "host": "192.168.5.151", "port": 9001, "user": "", "pass": "", "noFileCache": false, "connectTimeout": 2000 }, "states": { "type": "file", "typeComment": "Possible values: 'file' - [port 9000], 'redis' - [port 6379].", "host": "192.168.5.151", "port": 9000, "maxQueue": 1000, "options": { "auth_pass": null, "retry_max_delay": 15000 } }, "log": { "level": "info", "maxDays": 7, "noStdout": true, "transport": { "file1": { "type": "file", "enabled": true, "filename": "log/iobroker", "fileext": ".log", "maxsize": null, "maxFiles": null }, "syslog1": { "type": "syslog", "enabled": false, "host": "localhost", "host_comment": "The host running syslogd, defaults to localhost.", "port_comment": "The port on the host that syslog is running on, defaults to syslogd's default port(514/UDP).", "protocol": "udp4", "protocol_comment": "The network protocol to log over (e.g. tcp4, udp4, unix, unix-connect, etc).", "path_comment": "The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).", "facility_comment": "Syslog facility to use (Default: local0).", "localhost": "iobroker", "localhost_comment": "Host to indicate that log messages are coming from (Default: localhost).", "sysLogType_comment": "The type of the syslog protocol to use (Default: BSD).", "app_name_comment": "The name of the application (Default: process.title).", "eol_comment": "The end of line character to be added to the end of the message (Default: Message without modifications)." } } }, "dataDirComment": "Always relative to iobroker.js-controller/", "dataDir": "../../iobroker-data/"node -v v8.11.3 root@IOBROKER1:/home/pi# nodejs -v v8.11.3 root@IOBROKER1:/home/pi# npm -v 4.6.1Aus lauter Unwissendheit(?) hab ich noch ein bisschen mit den Node-Versionen rumgespielt.
sudo npm cache clean -f sudo npm install -g n sudo n 6.13.1Und jetzt GEHT es.
Stand Slave:
node -v v6.13.1 pi@IOBROKER1:~ $ nodejs -v v8.11.3 pi@IOBROKER1:~ $ npm -v 3.10.10 -
Also Problem gelöst??
Gruß
rainer
-
Hast du nach ändern der Main node Version nochmal das ./reinstall.sh aufgerufen?
Ich sehe aber gerade:
node -v v6.13.1 pi@IOBROKER1:~ $ nodejs -v v8.11.3 pi@IOBROKER1:~ $ npm -v 3.10.10du hast ZWEI verschiedene node-installationen drauf.
Das geht schief!!
Gruß
Rainer
-
Reinstall läuft. (nach chmod +x reinstall.sh)
Und wie bekomm ich die JS runter?
Aalso reinstall ist fertig.
Aber so richtig runf läuft das leider nicht. Hatte BLE und Zigbee nochmal auf dem Master deinstallier und anschließend am Master für den Slave installiert (IOBROKER1 bei mir)
Nachdem war die Instanz trotzdem auf dem Master. Also hab ich die umgeklickt auf Slave.
Aber beide werden einfach nicht grün.
Ähhhhh–- Das muss ich nicht verstehen. Während ich jetzt versucht habe die nodejs auch auf die 6.13.1 downzugraden ging aufeinmal die grüne LED vom Zigbee Stick an.
Stand jetzt:
`node -v v6.13.1 pi@IOBROKER1:~ $ nodejs -v -bash: /usr/bin/nodejs: Datei oder Verzeichnis nicht gefunden pi@IOBROKER1:~ $ npm -v 3.10.10 Und Multihost geht auch noch.` [3825_image_4.png](/assets/uploads/files/3825_image_4.png)
305
Online32.6k
Users82.3k
Topics1.3m
Posts