NEWS
Node Red startet in IO Broker nicht "Verbindung verweigert"
-
pi@iobroker-pi:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null pi@iobroker-pi:~ $ uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs armv7l Kein Docker /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.18.1 v16.18.1 8.19.2 4.0.23 pi pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker tty /home/pi OK:1 http://archive.raspberrypi.org/debian buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 https://deb.nodesource.com/node_16.x buster InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Alle Pakete sind aktuell. nodejs: Installiert: 16.18.1-deb-1nodesource1 Installationskandidat: 16.18.1-deb-1nodesource1 Versionstabelle: *** 16.18.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@iobroker-pi:~ $ pi@iobroker-pi:~ $ iobroker uodate iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean]iobroker updateDein Betriebssystem möchte in Gänze auf eine aktuelle Version aktualisiert werden. Buster hat das Ende of Life im September erreicht.
-
pi@iobroker-pi:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null pi@iobroker-pi:~ $ uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs armv7l Kein Docker /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.18.1 v16.18.1 8.19.2 4.0.23 pi pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker tty /home/pi OK:1 http://archive.raspberrypi.org/debian buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 https://deb.nodesource.com/node_16.x buster InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Alle Pakete sind aktuell. nodejs: Installiert: 16.18.1-deb-1nodesource1 Installationskandidat: 16.18.1-deb-1nodesource1 Versionstabelle: *** 16.18.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@iobroker-pi:~ $ pi@iobroker-pi:~ $ iobroker uodate iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean]@heinloth streiche o setze p
-
iobroker updateDein Betriebssystem möchte in Gänze auf eine aktuelle Version aktualisiert werden. Buster hat das Ende of Life im September erreicht.
@thomas-braun alle aktualisiert
läuft trotzdem noch nicht -
@heinloth sagte in Node Red startet in IO Broker nicht "Verbindung verweigert":
@homoran wo
bei uodate
@heinloth sagte in Node Red startet in IO Broker nicht "Verbindung verweigert":
alle aktualisiert
was und warum?
-
iobroker updateDein Betriebssystem möchte in Gänze auf eine aktuelle Version aktualisiert werden. Buster hat das Ende of Life im September erreicht.
pi@iobroker-pi:~ $ iobroker update Used repository: stable Adapter "admin" : 6.2.23 , installed 6.2.23 Adapter "alexa2" : 3.21.0 , installed 3.21.0 Adapter "backitup" : 2.5.4 , installed 2.5.4 Adapter "discovery" : 3.0.5 , installed 3.0.5 Adapter "fronius" : 1.1.3 , installed 1.1.3 Adapter "fronius-solarweb": 0.0.3 , installed 0.0.3 Adapter "iot" : 1.11.9 , installed 1.11.9 Adapter "javascript" : 6.0.3 , installed 6.0.3 Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "lgtv" : 1.1.10 , installed 1.1.10 Adapter "loxone" : 3.0.0 , installed 3.0.0 Adapter "mihome-plug" : 0.2.1 , installed 0.2.1 Adapter "node-red" : 4.0.0 , installed 4.0.0 Adapter "simple-api" : 2.7.0 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonos" : 2.2.3 , installed 2.2.3 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0 -
pi@iobroker-pi:~ $ iobroker update Used repository: stable Adapter "admin" : 6.2.23 , installed 6.2.23 Adapter "alexa2" : 3.21.0 , installed 3.21.0 Adapter "backitup" : 2.5.4 , installed 2.5.4 Adapter "discovery" : 3.0.5 , installed 3.0.5 Adapter "fronius" : 1.1.3 , installed 1.1.3 Adapter "fronius-solarweb": 0.0.3 , installed 0.0.3 Adapter "iot" : 1.11.9 , installed 1.11.9 Adapter "javascript" : 6.0.3 , installed 6.0.3 Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "lgtv" : 1.1.10 , installed 1.1.10 Adapter "loxone" : 3.0.0 , installed 3.0.0 Adapter "mihome-plug" : 0.2.1 , installed 0.2.1 Adapter "node-red" : 4.0.0 , installed 4.0.0 Adapter "simple-api" : 2.7.0 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonos" : 2.2.3 , installed 2.2.3 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0Und im LogFile steht was?
-
Und im LogFile steht was?
@thomas-braun ```
node-red.1
2022-12-02 20:03:29.385 error 2 Dec 20:03:29 - [error] Error: listen EADDRINUSE: address already in use 192.168.178.38:8081 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at doListen (node:net:1660:7) at processTicksAndRejections (node:internal/process/task_queues:84:21)node-red.1
2022-12-02 20:03:29.382 error 2 Dec 20:03:29 - [error] Nicht abgefangene Ausnahmebedingung:node-red.1
2022-12-02 20:03:13.803 error 2 Dec 20:03:13 - [error] Error: listen EADDRINUSE: address already in use 192.168.178.38:8081 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at doListen (node:net:1660:7) at processTicksAndRejections (node:internal/process/task_queues:84:21)node-red.1
2022-12-02 20:03:13.801 error 2 Dec 20:03:13 - [error] Nicht abgefangene Ausnahmebedingung: -
@thomas-braun ```
node-red.1
2022-12-02 20:03:29.385 error 2 Dec 20:03:29 - [error] Error: listen EADDRINUSE: address already in use 192.168.178.38:8081 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at doListen (node:net:1660:7) at processTicksAndRejections (node:internal/process/task_queues:84:21)node-red.1
2022-12-02 20:03:29.382 error 2 Dec 20:03:29 - [error] Nicht abgefangene Ausnahmebedingung:node-red.1
2022-12-02 20:03:13.803 error 2 Dec 20:03:13 - [error] Error: listen EADDRINUSE: address already in use 192.168.178.38:8081 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at doListen (node:net:1660:7) at processTicksAndRejections (node:internal/process/task_queues:84:21)node-red.1
2022-12-02 20:03:13.801 error 2 Dec 20:03:13 - [error] Nicht abgefangene Ausnahmebedingung:Da läuft schon was anderes. Vermutlich die Instanz node-red.0
Warum hantierst du mit zwei Instanzen?
iobroker list instancessagt?
-
@thomas-braun ```
pi@iobroker-pi:~ $ iobroker list instances-
system.adapter.admin.0 : admin : iobroker-pi - enabled, port: 8081, bind: 0.0.0.0, run as: admin
-
system.adapter.alexa2.0 : alexa2 : iobroker-pi - enabled
-
system.adapter.backitup.0 : backitup : iobroker-pi - enabled
system.adapter.discovery.0 : discovery : iobroker-pi - disabled
system.adapter.fronius-solarweb.0 : fronius-solarweb : iobroker-pi - disabled
system.adapter.fronius.0 : fronius : iobroker-pi - disabled
system.adapter.iot.0 : iot : iobroker-pi - disabled
system.adapter.javascript.0 : javascript : iobroker-pi - disabled
system.adapter.lgtv.1 : lgtv : iobroker-pi - disabled -
system.adapter.loxone.0 : loxone : iobroker-pi - enabled, port: 80
-
system.adapter.node-red.5 : node-red : iobroker-pi - enabled, port: 1880, bind: 0.0.0.0
-
system.adapter.sonos.0 : sonos : iobroker-pi - enabled
-
system.adapter.web.0 : web : iobroker-pi - enabled, port: 8082, bind: 0.0.0.0, run as: admin
-
instance is alive
pi@iobroker-pi:~ $
-
-
@thomas-braun ```
pi@iobroker-pi:~ $ iobroker list instances-
system.adapter.admin.0 : admin : iobroker-pi - enabled, port: 8081, bind: 0.0.0.0, run as: admin
-
system.adapter.alexa2.0 : alexa2 : iobroker-pi - enabled
-
system.adapter.backitup.0 : backitup : iobroker-pi - enabled
system.adapter.discovery.0 : discovery : iobroker-pi - disabled
system.adapter.fronius-solarweb.0 : fronius-solarweb : iobroker-pi - disabled
system.adapter.fronius.0 : fronius : iobroker-pi - disabled
system.adapter.iot.0 : iot : iobroker-pi - disabled
system.adapter.javascript.0 : javascript : iobroker-pi - disabled
system.adapter.lgtv.1 : lgtv : iobroker-pi - disabled -
system.adapter.loxone.0 : loxone : iobroker-pi - enabled, port: 80
-
system.adapter.node-red.5 : node-red : iobroker-pi - enabled, port: 1880, bind: 0.0.0.0
-
system.adapter.sonos.0 : sonos : iobroker-pi - enabled
-
system.adapter.web.0 : web : iobroker-pi - enabled, port: 8082, bind: 0.0.0.0, run as: admin
-
instance is alive
pi@iobroker-pi:~ $
@heinloth das kann nicht sein!
hast du was herausgeschnitten? -
-
Da läuft schon was anderes. Vermutlich die Instanz node-red.0
Warum hantierst du mit zwei Instanzen?
iobroker list instancessagt?
@thomas-braun habe ein paar mal gelöscht und neu gestartet
-
Es nur eine Randnotiz. Bei mir Läuft NodeRed 4.x auch nicht. Alle Nodes sind deaktiviert.
Vieleicht die Version 3.x Probieren. -
@homoran ```
pi@iobroker-pi:~ $ iobroker list instances-
system.adapter.admin.0 : admin : iobroker-pi - enabled, port: 8081, bind: 0.0.0.0, run as: admin
-
system.adapter.alexa2.0 : alexa2 : iobroker-pi - enabled
-
system.adapter.backitup.0 : backitup : iobroker-pi - enabled
system.adapter.discovery.0 : discovery : iobroker-pi - disabled
system.adapter.fronius-solarweb.0 : fronius-solarweb : iobroker-pi - disabled
system.adapter.fronius.0 : fronius : iobroker-pi - disabled
system.adapter.iot.0 : iot : iobroker-pi - disabled
system.adapter.javascript.0 : javascript : iobroker-pi - disabled
system.adapter.lgtv.1 : lgtv : iobroker-pi - disabled -
system.adapter.loxone.0 : loxone : iobroker-pi - enabled, port: 80
-
system.adapter.node-red.5 : node-red : iobroker-pi - enabled, port: 1880, bind: 0.0.0.0
-
system.adapter.sonos.0 : sonos : iobroker-pi - enabled
-
system.adapter.web.0 : web : iobroker-pi - enabled, port: 8082, bind: 0.0.0.0, run as: admin
-
instance is alive
-
-
@thomas-braun ```
node-red.1
2022-12-02 20:03:29.385 error 2 Dec 20:03:29 - [error] Error: listen EADDRINUSE: address already in use 192.168.178.38:8081 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at doListen (node:net:1660:7) at processTicksAndRejections (node:internal/process/task_queues:84:21)node-red.1
2022-12-02 20:03:29.382 error 2 Dec 20:03:29 - [error] Nicht abgefangene Ausnahmebedingung:node-red.1
2022-12-02 20:03:13.803 error 2 Dec 20:03:13 - [error] Error: listen EADDRINUSE: address already in use 192.168.178.38:8081 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at doListen (node:net:1660:7) at processTicksAndRejections (node:internal/process/task_queues:84:21)node-red.1
2022-12-02 20:03:13.801 error 2 Dec 20:03:13 - [error] Nicht abgefangene Ausnahmebedingung:@heinloth sagte in Node Red startet in IO Broker nicht "Verbindung verweigert":
node-red.1
wo ist das?
-
@homoran ```
pi@iobroker-pi:~ $ iobroker list instances-
system.adapter.admin.0 : admin : iobroker-pi - enabled, port: 8081, bind: 0.0.0.0, run as: admin
-
system.adapter.alexa2.0 : alexa2 : iobroker-pi - enabled
-
system.adapter.backitup.0 : backitup : iobroker-pi - enabled
system.adapter.discovery.0 : discovery : iobroker-pi - disabled
system.adapter.fronius-solarweb.0 : fronius-solarweb : iobroker-pi - disabled
system.adapter.fronius.0 : fronius : iobroker-pi - disabled
system.adapter.iot.0 : iot : iobroker-pi - disabled
system.adapter.javascript.0 : javascript : iobroker-pi - disabled
system.adapter.lgtv.1 : lgtv : iobroker-pi - disabled -
system.adapter.loxone.0 : loxone : iobroker-pi - enabled, port: 80
-
system.adapter.node-red.5 : node-red : iobroker-pi - enabled, port: 1880, bind: 0.0.0.0
-
system.adapter.sonos.0 : sonos : iobroker-pi - enabled
-
system.adapter.web.0 : web : iobroker-pi - enabled, port: 8082, bind: 0.0.0.0, run as: admin
-
instance is alive
@heinloth sagte in Node Red startet in IO Broker nicht "Verbindung verweigert":
node-red.5
Was machst du da?
Und bitte die CodeTags in einer neuen Zeile setzen, dann funktioniert es auch richtig. -
-
@homoran ```
pi@iobroker-pi:~ $ iobroker list instances-
system.adapter.admin.0 : admin : iobroker-pi - enabled, port: 8081, bind: 0.0.0.0, run as: admin
-
system.adapter.alexa2.0 : alexa2 : iobroker-pi - enabled
-
system.adapter.backitup.0 : backitup : iobroker-pi - enabled
system.adapter.discovery.0 : discovery : iobroker-pi - disabled
system.adapter.fronius-solarweb.0 : fronius-solarweb : iobroker-pi - disabled
system.adapter.fronius.0 : fronius : iobroker-pi - disabled
system.adapter.iot.0 : iot : iobroker-pi - disabled
system.adapter.javascript.0 : javascript : iobroker-pi - disabled
system.adapter.lgtv.1 : lgtv : iobroker-pi - disabled -
system.adapter.loxone.0 : loxone : iobroker-pi - enabled, port: 80
-
system.adapter.node-red.5 : node-red : iobroker-pi - enabled, port: 1880, bind: 0.0.0.0
-
system.adapter.sonos.0 : sonos : iobroker-pi - enabled
-
system.adapter.web.0 : web : iobroker-pi - enabled, port: 8082, bind: 0.0.0.0, run as: admin
-
instance is alive
-
-
@heinloth sagte in Node Red startet in IO Broker nicht "Verbindung verweigert":
node-red.1
wo ist das?
-
@homoran die nummer kann man doch frei wählen
ich habe einfach verschiedenes probiert die 1 wurde wieder gelöscht genauso wie die 0 -
@homoran die nummer kann man doch frei wählen
ich habe einfach verschiedenes probiert die 1 wurde wieder gelöscht genauso wie die 0@heinloth sagte in Node Red startet in IO Broker nicht "Verbindung verweigert":
ich habe einfach verschiedenes probiert die 1 wurde wieder gelöscht genauso wie die 0
wie sollen wir dir helfen, wenn du die Rahmenbedingungen änderst?
wieso zeigst du uns ein (altes) Log mit .1 wenn du jetzt .5 hast?
gibt es da den Fehler nicht mehr?
342
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge