NEWS
Neue Version von js-controller 0.6.6
-
Ich habe neue Version von js-controller vorbereitet.
Kann jemand ausprobieren?
-
- (bluefox) implement daily rolling files.
* (bluefox) fix addChannelToEnum, deleteChannelFromEnum, deleteChannel if no device name * (bluefox) fix "state set", "message" console commands * (bluefox) fix errors in adapter.js * (bluefox) add default certificates
cs /opt/iobroker npm install https://github.com/ioBroker/ioBroker.js-controller/tarball/master ./iobroker restart
-
-
Installation ist ohne Fehlermeldungen durchgelaufen.
Nach iobroker restart wieder einige code 7
Nach reboot nur noch uncaught exception beim s7 Adapter (wiederholt)
Gruß
Rainer
Gesendet von meinem LIFETAB_S785X mit Tapatalk
-
Nach reboot nur noch uncaught exception beim s7 Adapter (wiederholt) `
Welcher? -
Fehlerfrei durchgelaufen und auch die "already running" Fehler weg! TOP!
-
Nach reboot nur noch uncaught exception beim s7 Adapter (wiederholt)
Welcher?
?????Beim Siemens s7
Edit:
Eben im log gesehen:
host-quad-pi 2015-05-08 09:11:48 error instance system.adapter.s7.0 terminated with code 6 (uncaught exception) TypeError: 2015-05-08 09:11:48 error at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:301:8) TypeError: 2015-05-08 09:11:48 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:134:20) TypeError: 2015-05-08 09:11:48 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15) TypeError: 2015-05-08 09:11:48 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:220:12) TypeError: 2015-05-08 09:11:48 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:295:6) TypeError: 2015-05-08 09:11:48 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:245:29) TypeError: 2015-05-08 09:11:48 error at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2015:14) TypeError: 2015-05-08 09:11:48 error at Adapter.EventEmitter.emit (events.js:92:17) TypeError: 2015-05-08 09:11:48 error at Adapter.pulse_list (/opt/iobroker/node_modules/iobroker.s7/main.js:37:5) TypeError: 2015-05-08 09:11:48 error at main (/opt/iobroker/node_modules/iobroker.s7/main.js:256:21) TypeError: 2015-05-08 09:11:48 error Cannot read property 'round' of undefined uncaught 2015-05-08 09:11:48 error exception: Cannot read property 'round' of undefined s7-0 2015-05-08 09:11:48 info starting. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.s7 host-quad-pi 2015-05-08 09:11:42 info instance system.adapter.s7.0 started with pid 18323 host-quad-pi 2015-05-08 09:11:19 info Update repository "default" under "conf/sources-dist.json" host-quad-pi 2015-05-08 09:11:12 info Restart adapter system.adapter.s7.0 because enabled host-quad-pi 2015-05-08 09:11:12 error instance system.adapter.s7.0 terminated with code 6 (uncaught exception) TypeError: 2015-05-08 09:11:11 error at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:301:8) TypeError: 2015-05-08 09:11:11 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:134:20) TypeError: 2015-05-08 09:11:11 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15) TypeError: 2015-05-08 09:11:11 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:220:12) TypeError: 2015-05-08 09:11:11 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:295:6) TypeError: 2015-05-08 09:11:11 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:245:29) TypeError: 2015-05-08 09:11:11 error at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2015:14) TypeError: 2015-05-08 09:11:11 error at Adapter.EventEmitter.emit (events.js:92:17)
Gesendet von meinem Cynus T7 mit Tapatalk
-
Guten Morgen zusammen,
habe heute morgen auf meinem Pi2-2 das Update duchgeführt.
Etwas Geduld sollte man haben. (Dauer ca. 5 Min)
iobroker 2015-05-10 07:59:50 info exit 0 iobroker 2015-05-10 07:59:50 info Starting node restart.js iobroker 2015-05-10 07:59:49 info _restart iobroker 2015-05-10 07:57:26 info exit 0 iobroker 2015-05-10 07:57:25 info Starting node restart.js iobroker 2015-05-10 07:57:25 info _restart iobroker 2015-05-10 07:56:55 info exit 0 iobroker 2015-05-10 07:56:55 info Starting node restart.js iobroker 2015-05-10 07:56:55 info Chmod finished. Restart controller iobroker 2015-05-10 07:56:55 info Execute: chmod 777 -R /opt/iobroker/node_modules/iobroker.js-controller iobroker 2015-05-10 07:56:55 info Host 'Pi2-2' (linux) updated iobroker 2015-05-10 07:51:37 info npm install iobroker.js-controller --production --prefix '/opt/iobroker' (System call) iobroker 2015-05-10 07:51:36 info upgrade self
Das aktualisieren der Anzeige scheint jedoch nicht zu funktionieren.
Auch ein betätigen des Restart-Button ergibt einen Eintrag im LOG…....
PID vorher
pi@Pi2-2 /opt/iobroker $ ps -A | grep " io.*" 1147 ? 01:55:23 io.js-controlle 1153 ? 00:42:13 io.admin.0 1155 ? 00:01:12 io.node-red.0 1174 ? 00:52:01 io.javascript.0 1206 ? 00:12:00 io.hm-rpc.0 1212 ? 00:37:12 io.history.0 1214 ? 00:15:12 io.hm-rega.0 1233 ? 00:01:39 io.sonos.0 1235 ? 00:04:23 io.web.0 1253 ? 00:01:10 io.email.0 1264 ? 00:02:06 io.ping.0 1266 ? 00:35:42 io.mqtt.0 1300 ? 00:01:33 io.hm-rpc.1
Restart
iobroker 2015-05-10 08:08:03 info exit 0 iobroker 2015-05-10 08:08:03 info Starting node restart.js iobroker 2015-05-10 08:08:02 info _restart
PID nach restart gleich geblieben (1147)
pi@Pi2-2 /opt/iobroker $ ps -A | grep " io.*" 1147 ? 01:55:25 io.js-controlle 1153 ? 00:42:14 io.admin.0 1155 ? 00:01:12 io.node-red.0 1174 ? 00:52:02 io.javascript.0 1206 ? 00:12:00 io.hm-rpc.0 1212 ? 00:37:13 io.history.0 1214 ? 00:15:12 io.hm-rega.0 1233 ? 00:01:39 io.sonos.0 1235 ? 00:04:23 io.web.0 1253 ? 00:01:10 io.email.0 1264 ? 00:02:06 io.ping.0 1266 ? 00:35:43 io.mqtt.0 1300 ? 00:01:33 io.hm-rpc.1 pi@Pi2-2 /opt/iobroker $
Wenn ich mit der console schaue welche Versionen laufen:
pi@Pi2-2 /opt/iobroker $ ./iobroker update update done Adapter "zwave" : 0.1.0 Adapter "yr" : 0.1.5 , installed 0.1.5 Adapter "web" : 0.3.1 , installed 0.3.1 Adapter "vis" : 0.3.2 , installed 0.3.1 [Updateable] Adapter "sonos" : 0.1.6 , installed 0.1.6 Adapter "rickshaw" : 0.2.2 , installed 0.2.2 Adapter "pushover" : 0.1.1 Adapter "owfs" : 0.0.2 Adapter "onkyo" : 0.1.1 Adapter "socketio" : 0.3.0 Adapter "simple-api" : 0.0.4 Adapter "sayit" : 0.3.6 , installed 0.3.6 Adapter "s7" : 0.1.1 Adapter "ping" : 0.1.4 , installed 0.1.4 Adapter "node-red" : 0.1.9 , installed 0.1.9 Adapter "mqtt" : 0.1.7 , installed 0.1.7 Adapter "megad" : 0.0.2 Adapter "legacy" : 0.1.12 Adapter "knx" : 0.0.1 Controller "js-controller" : 0.6.6 , installed 0.6.6 Adapter "javascript" : 0.3.2 , installed 0.3.2 Adapter "ical" : 0.1.0 , installed 0.1.0 Adapter "hmm" : 0.0.17 , installed 0.0.17 Adapter "hue" : 0.2.0 Adapter "hm-rpc" : 0.4.0 , installed 0.4.0 Adapter "hm-rega" : 0.2.2 , installed 0.2.2 Adapter "history" : 0.1.3 , installed 0.1.3 Adapter "example" : 0.1.1 , installed 0.1.1 Adapter "email" : 0.1.2 , installed 0.1.2 Adapter "dwd" : 0.1.9 , installed 0.1.9 Adapter "cul" : 0.0.4 Adapter "b-control-em" : 0.1.1 Adapter "artnet" : 0.0.3 Adapter "admin" : 0.4.6 , installed 0.4.6 pi@Pi2-2 /opt/iobroker $
sieht es so aus, das sie Version 0.6.6 aktiv ist. Daher vermute ich, das die Anzeige "0.6.6(Running: 0.6.4)" nicht nicht stimmt
Gruß
derAuge
-
Doch!
Nach update des controllers reicht ein restart nicht aus.
Du musst einen reboot des rpi machen, dann ist alles OK.
Die Konsole zeigt nur die installierten Dateien, nicht die aktiven.
Gruß
Rainer
Gesendet von meinem LIFETAB_S785X mit Tapatalk
-
Hi Rainer,
ich glaube schon, dass die neue Version auch ohne "Neustart des Gesamtsystems" laufen sollte.
wenn ich nun weiter prüfe, stelle ich fest, dass ich den controller nicht stoppen kann
root@Pi2-2:/opt/iobroker# ./iobroker stop ioBroker controller daemon is not running root@Pi2-2:/opt/iobroker# root@Pi2-2:/opt/iobroker# ps -A | grep " io.*" 1147 ? 01:58:10 io.js-controlle 1153 ? 00:43:25 io.admin.0 1155 ? 00:01:13 io.node-red.0 1174 ? 00:52:53 io.javascript.0 1206 ? 00:12:11 io.hm-rpc.0 1212 ? 00:37:50 io.history.0 1214 ? 00:15:28 io.hm-rega.0 1233 ? 00:01:40 io.sonos.0 1235 ? 00:04:51 io.web.0 1253 ? 00:01:11 io.email.0 1264 ? 00:02:08 io.ping.0 1266 ? 00:36:19 io.mqtt.0 1300 ? 00:01:35 io.hm-rpc.1 root@Pi2-2:/opt/iobroker#
alle Prozesse laufen weiter
ein Restart bringt auch keinen Erfolg
root@Pi2-2:/opt/iobroker# ./iobroker restart ioBroker controller daemon is not running Starting ioBroker controller daemon... ioBroker controller daemon started. PID: 9568 root@Pi2-2:/opt/iobroker# root@Pi2-2:/opt/iobroker# root@Pi2-2:/opt/iobroker# ps -A | grep " io.*" 1147 ? 01:58:24 io.js-controlle 1153 ? 00:43:32 io.admin.0 1155 ? 00:01:13 io.node-red.0 1174 ? 00:53:00 io.javascript.0 1206 ? 00:12:13 io.hm-rpc.0 1212 ? 00:37:55 io.history.0 1214 ? 00:15:29 io.hm-rega.0 1233 ? 00:01:41 io.sonos.0 1235 ? 00:04:51 io.web.0 1253 ? 00:01:11 io.email.0 1264 ? 00:02:08 io.ping.0 1266 ? 00:36:24 io.mqtt.0 1300 ? 00:01:35 io.hm-rpc.1
Da muss man schon etwas härter vorgehen
Von der Konsole aud "schisse" ich die PID ab:
root@Pi2-2:/opt/iobroker# kill 1147 root@Pi2-2:/opt/iobroker# root@Pi2-2:/opt/iobroker# kill 1147 bash: kill: (1147) - Kein passender Prozess gefunden
Danach stelle ich fest, dass der controller automatisch neu gestartet wird (PID 10318 )
root@Pi2-2:/opt/iobroker# ps -A | grep " io.*" 1153 ? 00:43:39 io.admin.0 1155 ? 00:01:14 io.node-red.0 1174 ? 00:53:06 io.javascript.0 1206 ? 00:12:14 io.hm-rpc.0 1212 ? 00:37:59 io.history.0 1214 ? 00:15:31 io.hm-rega.0 1233 ? 00:01:41 io.sonos.0 1235 ? 00:04:51 io.web.0 1253 ? 00:01:11 io.email.0 1264 ? 00:02:09 io.ping.0 1266 ? 00:36:28 io.mqtt.0 1300 ? 00:01:36 io.hm-rpc.1 10318 ? 00:00:12 io.js-controlle 10326 ? 00:00:03 io.node-red.0 10489 ? 00:00:02 io.yr.0 root@Pi2-2:/opt/iobroker#
Nun rufe ich das WebUI wieder auf (Strg F5) und die Anzeige stimmt (0.6.6 0.6.6)
@Bluefox : Kann es in der Start / Stop / Restart - Routine noch ein Problem geben?
Wenn ich nun ioBroker stoppe, wird der controller beendet, die anderen Prozesse laufen weiter
root@Pi2-2:/opt/iobroker# ./iobroker stop Stopping ioBroker controller daemon... ioBroker controller daemon stopped. root@Pi2-2:/opt/iobroker# root@Pi2-2:/opt/iobroker# ps -A | grep " io.*" 1153 ? 00:43:57 io.admin.0 1155 ? 00:01:14 io.node-red.0 1174 ? 00:53:19 io.javascript.0 1206 ? 00:12:17 io.hm-rpc.0 1212 ? 00:38:09 io.history.0 1214 ? 00:15:35 io.hm-rega.0 1233 ? 00:01:42 io.sonos.0 1235 ? 00:04:59 io.web.0 1253 ? 00:01:12 io.email.0 1264 ? 00:02:10 io.ping.0 1266 ? 00:36:38 io.mqtt.0 1300 ? 00:01:36 io.hm-rpc.1 10326 ? 00:00:05 io.node-red.0 root@Pi2-2:/opt/iobroker#
Ist das so gewollt?
Gruß
derAuge
-
Nein. So ist das nicht gewollt…
Ich denke ich werde Aufforderung schreiben, dass nach dem update von js-controller den PC neu starten.