NEWS
Error rpi-gio ?
-
Hallo,
Habe iobroker auf einem cubietruck installiert, nicht das fertige Image verwendet, da es mir immer meldete dass der Speicherplatz voll ist, obwohl er gar nicht voll war… aber dass ist ein anderes Problem.
Also, cubietruck auf debian-server mit iobroker drauf
das log gibt mir alle paar Sekunden folgende Fehlermeldungen und ich würde gerne wissen, warum und wie ich das wegbringe.
Danke im Voraus:
node-red.0 2016-01-21 10:13:15 info node-red.0 Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js node-red.0 2016-01-21 10:13:10 info node-red.0 node-red exited with 1 node-red.0 2016-01-21 10:13:10 error node-red.0 21 Jan 10:13:10 - [error] Error: port in use node-red.0 2016-01-21 10:13:10 error node-red.0 21 Jan 10:13:10 - [error] Unable to listen on http://127.0.0.1:1880/ node-red.0 2016-01-21 10:13:10 warn node-red.0 21 Jan 10:13:10 - [warn] Communication server error: Error: listen EADDRINUSE node-red.0 2016-01-21 10:13:10 warn node-red.0 21 Jan 10:13:10 - [warn] ------------------------------------------ node-red.0 2016-01-21 10:13:10 warn node-red.0 21 Jan 10:13:10 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node node-red.0 2016-01-21 10:13:10 warn node-red.0 21 Jan 10:13:10 - [warn] ------------------------------------------ squeezebox.0 2016-01-21 10:13:09 info squeezebox.0 Got event from b8:27:eb:49:e2:37: duration 0 squeezebox.0 2016-01-21 10:13:09 info squeezebox.0 Got event from b8:27:eb:06:7c:c3: duration 0 squeezebox.0 2016-01-21 10:13:09 info squeezebox.0 Got event from b8:27:eb:ef:c0:24: duration 0 squeezebox.0 2016-01-21 10:13:09 info squeezebox.0 Got event from b8:27:eb:05:44:76: duration 0 node-red.0 2016-01-21 10:12:52 info node-red.0 Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js hm-rega.0 2016-01-21 10:12:49 info hm-rega.0 Got unexpected ID: hm-rpc.1.updated hm-rpc.1 2016-01-21 10:12:49 info hm-rpc.1 xmlrpc -> listDevices 0 node-red.0 2016-01-21 10:12:47 info node-red.0 node-red exited with 1 node-red.0 2016-01-21 10:12:47 error node-red.0 21 Jan 10:12:47 - [error] Unable to listen on http://127.0.0.1:1880/ 21 Jan 10:12:47 - [error] Error: port in use node-red.0 2016-01-21 10:12:47 warn node-red.0 21 Jan 10:12:47 - [warn] Communication server error: Error: listen EADDRINUSE node-red.0 2016-01-21 10:12:47 warn node-red.0 21 Jan 10:12:47 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node 21 Jan 10:12:47 - [warn] ------------------------------------------ 21 Jan 10:12:47 - [info] Settings file : node-red.0 2016-01-21 10:12:47 warn node-red.0 21 Jan 10:12:47 - [warn] ------------------------------------------ squeezebox.0 2016-01-21 10:12:39 info squeezebox.0 Got event from b8:27:eb:49:e2:37: duration 0 squeezebox.0 2016-01-21 10:12:39 info squeezebox.0 Got event from b8:27:eb:06:7c:c3: duration 0 squeezebox.0 2016-01-21 10:12:39 info squeezebox.0 Got event from b8:27:eb:ef:c0:24: duration 0 squeezebox.0 2016-01-21 10:12:39 info squeezebox.0 Got event from b8:27:eb:05:44:76: duration 0 node-red.0 2016-01-21 10:12:29 info node-red.0 Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js node-red.0 2016-01-21 10:12:24 info node-red.0 node-red exited with 1 node-red.0 2016-01-21 10:12:24 error node-red.0 21 Jan 10:12:24 - [error] Error: port in use node-red.0 2016-01-21 10:12:24 error node-red.0 21 Jan 10:12:24 - [error] Unable to listen on http://127.0.0.1:1880/ node-red.0 2016-01-21 10:12:24 warn node-red.0 21 Jan 10:12:24 - [warn] Communication server error: Error: listen EADDRINUSE node-red.0 2016-01-21 10:12:24 warn node-red.0 21 Jan 10:12:24 - [warn] ------------------------------------------ node-red.0 2016-01-21 10:12:24 warn node-red.0 21 Jan 10:12:24 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node node-red.0 2016-01-21 10:12:24 warn node-red.0 21 Jan 10:12:24 - [warn] ------------------------------------------ squeezebox.0 2016-01-21 10:12:09 info squeezebox.0 Got event from b8:27:eb:49:e2:37: duration 0 squeezebox.0 2016-01-21 10:12:09 info squeezebox.0 Got event from b8:27:eb:06:7c:c3: duration 0 squeezebox.0 2016-01-21 10:12:09 info squeezebox.0 Got event from b8:27:eb:ef:c0:24: duration 0 squeezebox.0 2016-01-21 10:12:09 info squeezebox.0 Got event from b8:27:eb:05:44:76: duration 0 -
1.)
[error] Error: port in use
Setz mal ein:
"netstat -tulpen |grep 1880"
in der Console ab und poste mal das Ergebniss.
Vermutlich hängt ein: " io.node-red.0" prozess.
2.)
"[rpi-gpio] Info : Ignoring Raspberry Pi specific node"
ist meiner Meinung normal, da du keine RaspberryPi spezifischen GPIO hast.
Das Loglevel ist da ein wenig unglücklich gewählt:
adapter.log.debug
währe da wohl angebracht….
Gruß
Martin
-
hey,
habe den node-red adapter auf "debug" gesetzt, log sieht jetzt nur mehr so aus:
node-red-0 2016-01-21 11:09:36 debug 21 Jan 11:09:36 - [info] Started flows node-red-0 2016-01-21 11:09:36 debug 21 Jan 11:09:36 - [info] Starting flows node-red-0 2016-01-21 11:09:36 debug 21 Jan 11:09:36 - [info] Server now running at http://127.0.0.1:1880/ node-red-0 2016-01-21 11:09:35 debug 21 Jan 11:09:35 - [info] Flows file : /opt/iobroker/iobroker-data/node-red/flows.json node-red-0 2016-01-21 11:09:35 debug 21 Jan 11:09:35 - [info] User directory : /opt/iobroker/iobroker-data/node-red/ node-red-0 2016-01-21 11:09:35 debug 21 Jan 11:09:35 - [info] Settings file : /opt/iobroker/iobroker-data/node-red/settings.js node-red-0 2016-01-21 11:09:35 warn 21 Jan 11:09:35 - [warn] ------------------------------------------ node-red-0 2016-01-21 11:09:35 warn 21 Jan 11:09:35 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node node-red-0 2016-01-21 11:09:35 warn 21 Jan 11:09:35 - [warn] ------------------------------------------ node-red-0 2016-01-21 11:09:24 debug 21 Jan 11:09:24 - [info] Loading palette nodes node-red-0 2016-01-21 11:09:24 debug 21 Jan 11:09:24 - [info] Node.js version: v0.12.6 node-red-0 2016-01-21 11:09:24 debug 21 Jan 11:09:24 - [info] Node-RED version: v0.12.5 node-red-0 2016-01-21 11:09:24 debug =================== node-red-0 2016-01-21 11:09:24 debug Welcome to Node-RED node-red-0 2016-01-21 11:09:24 debug node-red-0 2016-01-21 11:09:18 info Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js node-red-0 2016-01-21 11:09:16 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.node-red node-red-0 2016-01-21 11:09:16 debug statesDB connectednetstat gibt folgendes zurück:
root@cubietruck:~# netstat -tulpen | grep 1880 tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 0 293741 6621/node-red -
Ja, nein :-)
Nicht du hast den Loglevel unglücklich gewählt, sondern der der den adapter erstellt hat (bzw. der node-red author).
Das Fehlen der GPIOs sollte imho als debug und nicht als warn klassifiziert werden.
Einfach ignorieren.
Der
[error] Error: port in use
ist weg.
Gruß
Support us
669
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge