Ich bin sehr besorgt: Adapter : bearbeite…
-
Probiert: gleiche Resultat!
ist nicht instabil aber Frustrirend!!
stek
-
Hallo,
plözlich wenn ich in Adapter Tab gehe haie ci das folgende:
filename="Immagine 212.png" index="1">~~Ich habe probiert zu machen was ich gelesen habe:
npm cache clean
./iobroker upgrade
aber ich habe jmmer noch das Problem!
ich kan aich nich mehr in die Eigenschaft zu gehen:
filename="Immagine 213.png" index="0">~~Mein IoBroker lauft auf Synology of wird langsam unverzichtbar, so brauche ich ein zuverlässig System..
Ich habe natürlich shon mit Chrome, Firefox und IE probiert.
Danke für die Hilfe!
Stek `
Es war heute Morgen das Problem, dass repository online beschädigt war. Ungefähr um 12:00 habe ich das repariert. -
na, das Problem ist immer noch da..
Stek
-
Hast du irgendeinen Adapter oder den Controller upgedatet als es zu dem "bearbeite" Screen kam?
Gruß
Rainer
-
nei nich besondere, ich habe gewisse vis adapters ausprobiert.
in log habe ich
node-red.0 2016-08-28 11:17:55.365 info node-red.0 Starting node-red: --max-old-space-size=128 /volume1/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /volume1/iobroker/iobroker-data/node-red/settings.js node-red.0 2016-08-28 11:17:53.936 info node-red.0 node-red exited with 1 node-red.0 2016-08-28 11:17:53.931 error node-red.0 28 Aug 11:17:53 - [error] Error: port in use node-red.0 2016-08-28 11:17:53.931 error node-red.0 28 Aug 11:17:53 - [error] Unable to listen on http://127.0.0.1:1880/ node-red.0 2016-08-28 11:17:53.931 warn node-red.0 28 Aug 11:17:53 - [warn] Communication server error: Error: listen EADDRINUSE node-red.0 2016-08-28 11:17:53.921 warn node-red.0 28 Aug 11:17:53 - [warn] ------------------------------------------------------ node-red.0 2016-08-28 11:17:53.920 warn node-red.0 28 Aug 11:17:53 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node node-red.0 2016-08-28 11:17:53.920 warn node-red.0 28 Aug 11:17:53 - [warn] ------------------------------------------------------ node-red.0 2016-08-28 11:17:52.702 info node-red.0 Starting node-red: --max-old-space-size=128 /volume1/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /volume1/iobroker/iobroker-data/node-red/settings.js node-red.0 2016-08-28 11:17:50.357 info node-red.0 node-red exited with 1 node-red.0 2016-08-28 11:17:50.354 error node-red.0 28 Aug 11:17:50 - [error] Error: port in use node-red.0 2016-08-28 11:17:50.354 error node-red.0 28 Aug 11:17:50 - [error] Unable to listen on http://127.0.0.1:1880/ node-red.0 2016-08-28 11:17:50.353 warn node-red.0 28 Aug 11:17:50 - [warn] Communication server error: Error: listen EADDRINUSE node-red.0 2016-08-28 11:17:50.344 warn node-red.0 28 Aug 11:17:50 - [warn] ------------------------------------------------------ node-red.0 2016-08-28 11:17:50.344 warn node-red.0 28 Aug 11:17:50 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node node-red.0 2016-08-28 11:17:50.343 warn node-red.0 28 Aug 11:17:50 - [warn] ------------------------------------------------------ nas02 2016-08-28 11:17:49.783 warn host.nas02 instance system.adapter.text2command.0 already running with pid 26383 node-red.0 2016-08-28 11:17:49.130 info node-red.0 Starting node-red: --max-old-space-size=128 /volume1/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /volume1/iobroker/iobroker-data/node-red/settings.js node-red.0 2016-08-28 11:17:47.694 info node-red.0 node-red exited with 1 node-red.0 2016-08-28 11:17:47.690 error node-red.0 28 Aug 11:17:47 - [error] Unable to listen on http://127.0.0.1:1880/ 28 Aug 11:17:47 - [error] Error: port in use node-red.0 2016-08-28 11:17:47.690 warn node-red.0 28 Aug 11:17:47 - [warn] Communication server error: Error: listen EADDRINUSE node-red.0 2016-08-28 11:17:47.682 warn node-red.0 28 Aug 11:17:47 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node 28 Aug 11:17:47 - [warn] ------------------------------------------------------ 28 Aug 11:17:47 - [info] Setti node-red.0 2016-08-28 11:17:47.681 warn node-red.0 28 Aug 11:17:47 - [warn] ------------------------------------------------------ nas02 2016-08-28 11:17:47.564 warn host.nas02 instance system.adapter.hm-rpc.0 already running with pid 26395 nas02 2016-08-28 11:17:47.162 info host.nas02 Restart adapter system.adapter.hm-rega.0 because enabled nas02 2016-08-28 11:17:47.162 error host.nas02 instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running) nas02 2016-08-28 11:17:46.880 info host.nas02 instance system.adapter.hm-rega.0 started with pid 26521 node-red.0 2016-08-28 11:17:46.468 info node-red.0 Starting node-red: --max-old-space-size=128 /volume1/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /volume1/iobroker/iobroker-data/node-red/settings.js node-red.0 2016-08-28 11:17:44.122 info node-red.0 node-red exited with 1 node-red.0 2016-08-28 11:17:44.118 error node-red.0 28 Aug 11:17:44 - [error] Error: port in use node-red.0 2016-08-28 11:17:44.118 error node-red.0 28 Aug 11:17:44 - [error] Unable to listen on http://127.0.0.1:1880/ node-red.0 2016-08-28 11:17:44.118 warn node-red.0 28 Aug 11:17:44 - [warn] Communication server error: Error: listen EADDRINUSE node-red.0 2016-08-28 11:17:44.108 warn node-red.0 28 Aug 11:17:44 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node 28 Aug 11:17:44 - [warn] ------------------------------------------------------ 28 Aug 11:17:44 - [info] Setti node-red.0 2016-08-28 11:17:44.107 warn node-red.0 28 Aug 11:17:44 - [warn] ------------------------------------------------------ node-red.0 2016-08-28 11:17:42.886 info node-red.0 Starting node-red: --max-old-space-size=128 /volume1/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /volume1/iobroker/iobroker-data/node-red/settings.js node-red.0 2016-08-28 11:17:41.461 info node-red.0 node-red exited with 1 node-red.0 2016-08-28 11:17:41.461 error node-red.0 28 Aug 11:17:41 - [error] Unable to listen on http://127.0.0.1:1880/ 28 Aug 11:17:41 - [error] Error: port in use node-red.0 2016-08-28 11:17:41.457 warn node-red.0 28 Aug 11:17:41 - [warn] Communication server error: Error: listen EADDRINUSE node-red.0 2016-08-28 11:17:41.450 warn node-red.0 28 Aug 11:17:41 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node 28 Aug 11:17:41 - [warn] ------------------------------------------------------ 28 Aug 11:17:41 - [info] Setti node-red.0 2016-08-28 11:17:41.449 warn node-red.0 28 Aug 11:17:41 - [warn] ------------------------------------------------------ node-red.0 2016-08-28 11:17:40.263 info node-red.0 Starting node-red: --max-old-space-size=128 /volume1/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /volume1/iobroker/iobroker-data/node-red/settings.js nas02 2016-08-28 11:17:39.537 info host.nas02 Restart adapter system.adapter.scenes.0 because enabled nas02 2016-08-28 11:17:39.537 error host.nas02 instance system.adapter.scenes.0 terminated with code 7 (Adapter already running) nas02 2016-08-28 11:17:39.298 info host.nas02 instance system.adapter.scenes.0 started with pid 26482 node-red.0 2016-08-28 11:17:37.883 info node-red.0 node-red exited with 1 node-red.0 2016-08-28 11:17:37.879 error node-red.0 28 Aug 11:17:37 - [error] Unable to listen on http://127.0.0.1:1880/ 28 Aug 11:17:37 - [error] Error: port in use node-red.0 2016-08-28 11:17:37.879 warn node-red.0 28 Aug 11:17:37 - [warn] Communication server error: Error: listen EADDRINUSE node-red.0 2016-08-28 11:17:37.872 warn node-red.0 28 Aug 11:17:37 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node 28 Aug 11:17:37 - [warn] ------------------------------------------------------ 28 Aug 11:17:37 - [info] Setti node-red.0 2016-08-28 11:17:37.870 warn node-red.0 28 Aug 11:17:37 - [warn] ------------------------------------------------------ nas02 2016-08-28 11:17:36.873 info host.nas02 Restart adapter system.adapter.hmm.0 because enabled nas02 2016-08-28 11:17:36.873 error host.nas02 instance system.adapter.hmm.0 terminated with code 7 (Adapter already running) node-red.0 2016-08-28 11:17:36.644 info node-red.0 Starting node-red: --max-old-space-size=128 /volume1/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /volume1/iobroker/iobroker-data/node-red/settings.js nas02 2016-08-28 11:17:36.641 info host.nas02 instance system.adapter.hmm.0 started with pid 26466 node-red.0 2016-08-28 11:17:35.260 info node-red.0 node-red exited with 1 node-red.0 2016-08-28 11:17:35.259 error node-red.0 28 Aug 11:17:35 - [error] Error: port in use -
Wie ist denn jetzt der Zustand.
Im anderen Thread schreibst du, dass node-red neu gestartet wurde.
Ist damit der Fehler mit dem belegten Port erledigt?
Ansonsten sieh mal hier
https://www.synology.com/de-de/knowledg … y_services
Gruß
Rainer
-
der code-red problem habe ich gelöst.
Der handere problem aber nicht!
nas02> node -v v0.12.6 nas02> npm -v 2.11.2ich habe zu verstehen, ob ich kann eine neuere Version von node für synology intel (unofficial) installieren kan..
Stek
-
der code-red problem habe ich gelöst.
Der handere problem aber nicht!
nas02> node -v v0.12.6 nas02> npm -v 2.11.2ich habe zu verstehen, ob ich kann eine neuere Version von node für synology intel (unofficial) installieren kan..
Stek `
Hast du versucht timeout zu erhöhen? Have you tried to increase the timeout? -
habe ich auf 10000 gesezt.
gleiche ergebniss.
enteder starte ich von vorne oder kaufe ich mir ein rasperrypi…
keine anung wie kan ich auf Synology enine neue release von Nodejs installieren kan, jch habe gesehen das möglich is (villeicht) mit Docker...
ich bin da blockiert
stek
-
von vorne neu installiert!
Skript erholte !
es ist wirklich traurig, dass niemand wisse, wie.
Das beunruhigt mich sehr.
Stek
