IOBroker hat sich beendet
-
Allgemein:
ps -ef | grep -E 'iobroker\.|io\.'Listet dann alle Instanzen, wichtig ist der js-controller läuft.
root 8826 1 1 04:11 ? 00:05:19 iobroker.js-controller root 8844 8826 0 04:11 ? 00:00:07 io.admin.0 root 8866 8826 0 04:11 ? 00:00:07 io.web.0 root 8918 8826 0 04:11 ? 00:00:34 io.hm-rpc.0 root 8933 8826 0 04:11 ? 00:00:12 io.hm-rega.0 root 8960 8826 0 04:11 ? 00:00:25 io.hm-rpc.1 root 9022 8826 0 04:12 ? 00:01:37 io.javascript.0 root 9056 8826 0 04:12 ? 00:00:18 io.ping.0 root 9120 8826 0 04:12 ? 00:02:30 io.sql.0 root 9145 8826 0 04:12 ? 00:00:04 io.geofency.0 root 9165 8826 0 04:12 ? 00:00:06 io.tankerkoenig.0 root 9192 8826 0 04:12 ? 00:00:04 io.pushover.0 root 9230 8826 0 04:13 ? 00:00:06 io.cloud.0 root 9246 8826 0 04:13 ? 00:00:06 io.fritzbox.0 root 9261 8826 0 04:13 ? 00:00:06 io.broadlink2.0 root 9284 8826 0 04:13 ? 00:00:04 io.scenes.0 root 9303 8826 0 04:13 ? 00:00:04 io.simple-api.0 root 9345 8826 0 04:13 ? 00:00:04 io.backitup.0 root 9369 8826 0 04:13 ? 00:00:05 io.alexa2.0 root 9387 8826 0 04:13 ? 00:00:07 io.amazon-dash.0 root 9413 8826 0 04:13 ? 00:01:45 io.mqtt.0 root 9484 8826 0 04:13 ? 00:00:46 io.tr-064.0 root 9512 8826 0 04:13 ? 00:00:30 io.hm-rpc.2 root 9530 8826 0 04:13 ? 00:00:11 io.yahka.0 -
Hallo alle
Also zu den Fragen:
Die Iobroker Installation ist die von Rainer Rock64 Image. Die hab ich nicht selber gemacht. Keine Ahnung ob die nach der "neuen Art" aufgesetzt wurde oder nichtWarum setzt Du ein `sudo´ vor Deinen Befehl wenn Du eh schon als root angemeldet bist?
Du solltest Dich mit Linux beschäftigen und Dich einlesen...Ich habe den String von Rainer einfach kopiert. Der Hinweis mich einzulesen ist leider nicht zielführend. Ob ich jetzt root bin und einen Befehl nochmal extra mit Root Rechten ausführe oder nicht sollte Wurst sein. Wenn es einen Unterschied gibt, dann bitte ich Dich den mir zu erklären. Wie auch immer ob mit oder ohne sudo: Das Ergebnis ist das Gleiche.
kann es sein das dein Gerät da neu gestartet ist?
Ich habe eben grad wieder den Effekt gehabt. Es sieht so aus als ob alles laufen würde bis auf den js-controller.
Uptime liefert 19hroot@ioBroker-Rock64:~# iobroker status iobroker is not running root@ioBroker-Rock64:~# ps -e | grep io 11 ? 00:00:00 migration/0 14 ? 00:00:00 migration/1 19 ? 00:00:00 migration/2 24 ? 00:00:00 migration/3 44 ? 00:00:00 rpciod 46 ? 00:00:00 xprtiod 73 ? 00:00:00 nfsiod 11787 ? 00:11:40 io.javascript.0 11797 ? 00:02:34 io.socketio.0 11819 ? 00:02:35 io.text2command 11829 ? 00:02:35 io.sayit.0 11912 ? 00:03:12 io.admin.0 11928 ? 00:02:48 io.web.0 11943 ? 00:02:41 io.fritzbox.0 11953 ? 00:02:41 io.history.0 11997 ? 00:02:32 io.simple-api.0 12021 ? 00:07:14 io.hm-rpc.0 12031 ? 00:13:18 io.hm-rpc.1 12041 ? 00:02:34 io.samsung.0 12051 ? 00:20:38 io.hm-rega.0 12062 ? 00:02:51 io.cloud.0 12073 ? 00:03:08 io.alexa2.0 12087 ? 00:02:54 io.iot.0 12093 ? 00:02:34 io.scenes.0 12107 ? 00:03:01 io.hm-rpc.2 12125 ? 00:02:36 io.shelly.0 14608 ? 00:03:10 io.telegram.0 root@ioBroker-Rock64:~# sudo systemctl iobroker status Unknown operation iobroker. root@ioBroker-Rock64:~# systemctl iobroker status Unknown operation iobroker. root@ioBroker-Rock64:~# uptime 19:39:53 up 1 day, 2:52, 1 user, load average: 0,20, 0,12, 0,09 root@ioBroker-Rock64:~#Also nein, der Rock64 scheint nicht neu gestartet zu sein.
Wie man oben sieht liefert iobroker status "iobroker is not running"
Der Befehl ps -ef | grep -E 'iobroker.|io.' liefertroot@ioBroker-Rock64:~# ps -ef | grep -E 'iobroker\.|io\.' root 11787 1 1 02:15 ? 00:11:49 io.javascript.0 root 11797 1 0 02:15 ? 00:02:36 io.socketio.0 root 11819 1 0 02:15 ? 00:02:37 io.text2command.0 root 11829 1 0 02:15 ? 00:02:37 io.sayit.0 root 11912 1 0 02:15 ? 00:03:15 io.admin.0 root 11928 1 0 02:15 ? 00:02:50 io.web.0 root 11943 1 0 02:15 ? 00:02:42 io.fritzbox.0 root 11953 1 0 02:16 ? 00:02:44 io.history.0 root 11997 1 0 02:16 ? 00:02:34 io.simple-api.0 root 12021 1 0 02:16 ? 00:07:20 io.hm-rpc.0 root 12031 1 1 02:16 ? 00:13:28 io.hm-rpc.1 root 12041 1 0 02:16 ? 00:02:36 io.samsung.0 root 12051 1 2 02:16 ? 00:21:11 io.hm-rega.0 root 12062 1 0 02:16 ? 00:02:53 io.cloud.0 root 12073 1 0 02:16 ? 00:03:10 io.alexa2.0 root 12087 1 0 02:16 ? 00:02:56 io.iot.0 root 12093 1 0 02:16 ? 00:02:36 io.scenes.0 root 12107 1 0 02:16 ? 00:03:03 io.hm-rpc.2 root 12125 1 0 02:17 ? 00:02:38 io.shelly.0 root 14608 1 0 05:04 ? 00:03:12 io.telegram.0 root 14795 14794 0 05:15 ? 00:01:59 node /opt/iobroker/node_modules/ iobroker.js-controller/iobroker.js backup root@ioBroker-Rock64:~#Auch hier der js-controller ist weg. Frage ist, ich wie finde ich raus warum?
Gruss Ralf
-
@derrapf sagte in IOBroker hat sich beendet:
von Rainer Rock64 Image
Wenn du jetzt noch sagst welches, kann ich das beantworten
-
Hallo Rainer
Äh das von der Iobroker.net Download Seite. Gibts da mehrere?Also das hier:
http://www.iobroker.net/docu/?page_id=2563&lang=deGruss Ralf
-
@derrapf
Netter link
das ist die ganze SeiteEtwas gefiltert sieht das so aus:
-
@Homoran
Ui, da sind ja jetzt ganz viele. Sorry. Als ich damals auf der Seite war gab es nur eines.
Ich habe das hier "ioBroker_Image_Rock64_20180419_stretch.img". Hilft Dir das?Ich habe jetzt mal den js-controller auf der Commandline gestartet
Da kommen viele Fehler.root@ioBroker-Rock64:/opt/iobroker# node node_modules/iobroker.js-controller/controlle r.js --logs 2019-02-25 19:55:43.332 - info: host.ioBroker-Rock64 iobroker.js-controller version 1 .4.2 js-controller starting 2019-02-25 19:55:43.342 - info: host.ioBroker-Rock64 Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker 2019-02-25 19:55:43.343 - info: host.ioBroker-Rock64 hostname: ioBroker-Rock64, node: v8.15.0 2019-02-25 19:55:43.350 - info: host.ioBroker-Rock64 ip addresses: 192.168.111.176 fd 13:235b:7090:0:4f6a:8f2e:213a:f7b7 2003:f4:4bc4:8200:b97a:5558:33ac:531c fd13:235b:709 0::cda fd13:235b:7090:0:7897:fff:fefc:11b5 fe80::7897:fff:fefc:11b5 2019-02-25 19:55:44.492 - info: host.ioBroker-Rock64 inMem-objects listening on port 9001 2019-02-25 19:55:44.666 - info: host.ioBroker-Rock64 States connected to redis: 127.0 .0.1:6379 2019-02-25 19:55:44.671 - info: host.ioBroker-Rock64 InMemoryDB connected 2019-02-25 19:55:44.767 - info: host.ioBroker-Rock64 57 instances found host.ioBroker-Rock64 check instance "system.adapter.admin.0" for host "ioBroker-Rock64 " host.ioBroker-Rock64 check instance "system.adapter.web.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.history.0" for host "ioBroker-Rock 64" host.ioBroker-Rock64 check instance "system.adapter.javascript.0" for host "ioBroker-R ock64" host.ioBroker-Rock64 check instance "system.adapter.socketio.0" for host "ioBroker-Roc k64" host.ioBroker-Rock64 check instance "system.adapter.mobile.0" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.vis-bars.0" for host "ioBroker-Roc k64" host.ioBroker-Rock64 check instance "system.adapter.vis-metro.0" for host "ioBroker-Ro ck64" host.ioBroker-Rock64 check instance "system.adapter.vis-rgraph.0" for host "ioBroker-R ock64" host.ioBroker-Rock64 check instance "system.adapter.vis-plumb.0" for host "ioBroker-Ro ck64" host.ioBroker-Rock64 check instance "system.adapter.vis-players.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-map.0" for host "ioBroker-Rock 64" host.ioBroker-Rock64 check instance "system.adapter.vis-keyboard.0" for host "ioBroker -Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-lcars.0" for host "ioBroker-Ro ck64" host.ioBroker-Rock64 check instance "system.adapter.vis-justgage.0" for host "ioBroker -Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-hqwidgets.0" for host "ioBroke r-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-jqui-mfd.0" for host "ioBroker -Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-fancyswitch.0" for host "ioBro ker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-colorpicker.0" for host "ioBro ker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-canvas-gauges.0" for host "ioB roker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-google-fonts.0" for host "ioBr oker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-history.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.ical.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.text2command.0" for host "ioBroker -Rock64" host.ioBroker-Rock64 check instance "system.adapter.sayit.0" for host "ioBroker-Rock64 " host.ioBroker-Rock64 check instance "system.adapter.owntracks.0" for host "ioBroker-Ro ck64" host.ioBroker-Rock64 check instance "system.adapter.js-controller.0" for host "ioBroke r-Rock64" host.ioBroker-Rock64 check instance "system.adapter.fritzbox.0" for host "ioBroker-Roc k64" host.ioBroker-Rock64 check instance "system.adapter.dwd.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.telegram.0" for host "ioBroker-Roc k64" host.ioBroker-Rock64 check instance "system.adapter.tvspielfilm.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.simple-api.0" for host "ioBroker-R ock64" host.ioBroker-Rock64 check instance "system.adapter.vis-timeandweather.0" for host "io Broker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.mqtt-client.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.hm-rpc.0" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.hm-rpc.1" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.samsung.0" for host "ioBroker-Rock 64" host.ioBroker-Rock64 check instance "system.adapter.hm-rega.0" for host "ioBroker-Rock 64" host.ioBroker-Rock64 check instance "system.adapter.cloud.0" for host "ioBroker-Rock64 " host.ioBroker-Rock64 check instance "system.adapter.alexa2.0" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.iot.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.scenes.0" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.hm-rpc.2" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.amazon-dash.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.weatherunderground.0" for host "io Broker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.shelly.0" for host "ioBroker-Rock6 4" 2019-02-25 19:55:44.841 - info: host.ioBroker-Rock64 starting 26 instances 2019-02-25 19:55:44.903 - info: host.ioBroker-Rock64 instance system.adapter.admin.0 started with pid 25475 2019-02-25 19:55:49.553 - info: host.ioBroker-Rock64 instance system.adapter.web.0 started with pid 25481 (node:25465) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated. 2019-02-25 19:55:51.231 - error: host.ioBroker-Rock64 instance system.adapter.admin.0 terminated with code 7 (Adapter already running) 2019-02-25 19:55:51.232 - info: host.ioBroker-Rock64 Restart adapter system.adapter.admin.0 because enabled 2019-02-25 19:55:53.226 - error: host.ioBroker-Rock64 instance system.adapter.web.0 terminated with code 7 (Adapter already running) 2019-02-25 19:55:53.227 - info: host.ioBroker-Rock64 Restart adapter system.adapter.web.0 because enabled 2019-02-25 19:55:57.015 - info: host.ioBroker-Rock64 instance system.adapter.history.0 started with pid 25508 2019-02-25 19:56:02.547 - info: host.ioBroker-Rock64 instance system.adapter.javascript.0 started with pid 25529 Cannot parse "/user/vis-views.json Send diag info: {"uuid":"aec67a1a-f2cf-7abe-98d8-845cd7e36d52","language":"de","country":"","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"linux"}],"node":"v8.15.0","arch":"arm64","adapters":{"admin":{"version":"3.5.10","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.9.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"2.3.0","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"},"vis":{"version":"1.1.8","platform":"Javascript/Node.js"},"history":{"version":"1.8.5","platform":"Javascript/Node.js"},"flot":{"version":"1.9.2","platform":"javascript/Node.js"},"javascript":{"version":"3.6.4","platform":"Javascript/Node.js"},"socketio":{"version":"2.1.1","platform":"Javascript/Node.js"},"mobile":{"version":"0.4.11","platform":"javascript/Node.js"},"vis-bars":{"version":"0.1.4","platform":"Javascript/Node.js"},"vis-metro":{"version":"1.1.2","platform":"Javascript/Node.js"},"vis-rgraph":{"version":"0.0.2","platform":"Javascript/Node.js"},"vis-plumb":{"version":"1.0.1","platform":"Javascript/Node.js"},"vis-players":{"version":"0.1.5","platform":"Javascript/Node.js"},"vis-map":{"version":"1.0.2","platform":"Javascript/Node.js"},"vis-keyboard":{"version":"0.0.2","platform":"Javascript/Node.js"},"vis-lcars":{"version":"1.0.4","platform":"Javascript/Node.js"},"vis-justgage":{"version":"1.0.0","platform":"Javascript/Node.js"},"vis-hqwidgets":{"version":"1.1.2","platform":"Javascript/Node.js"},"vis-jqui-mfd":{"version":"1.0.12","platform":"Javascript/Node.js"},"vis-fancyswitch":{"version":"1.1.0","platform":"Javascript/Node.js"},"vis-colorpicker":{"version":"1.1.1","platform":"Javascript/Node.js"},"vis-canvas-gauges":{"version":"0.1.5","platform":"Javascript/Node.js"},"vis-google-fonts":{"version":"0.1.0","platform":"Javascript/Node.js"},"vis-history":{"version":"0.2.7","platform":"Javascript/Node.js"},"icons-addictive-flavour-png":{"version":"0.1.0","platform":"javascript/Node.js"},"icons-icons8":{"version":"0.0.1","platform":"javascript/Node.js"},"icons-material-png":{"version":"0.1.0","platform":"javascript/Node.js"},"icons-material-svg":{"version":"0.1.0","platform":"javascript/Node.js"},"icons-mfd-png":{"version":"1.0.2","platform":"javascript/Node.js"},"icons-mfd-svg":{"version":"1.0.2","platform":"javascript/Node.js"},"icons-open-icon-library-png":{"version":"0.1.3","platform":"javascript/Node.js"},"icons-ultimate-png":{"version":"1.0.1","platform":"javascript/Node.js"},"ical":{"version":"1.7.0","platform":"Javascript/Node.js"},"text2command":{"version":"1.2.4","platform":"Javascript/Node.js"},"sayit":{"version":"1.7.0","platform":"Javascript/Node.js"},"owntracks":{"version":"0.5.0","platform":"Javascript/Node.js"},"js-controller":{"version":"1.4.2","platform":"Javascript/Node.js"},"fritzbox":{"version":"0.2.1","platform":"Javascript/Node.js"},"dwd":{"version":"2.4.3","platform":"javascript/Node.js"},"telegram":{"version":"1.3.6","platform":"Javascript/Node.js"},"tvspielfilm":{"version":"1.0.4","platform":"javascript/Node.js"},"simple-api":{"version":"2.0.0","platform":"Javascript/Node.js"},"vis-timeandweather":{"version":"1.1.7","platform":"Javascript/Node.js"},"cloud":{"version":"2.6.2","platform":"Javascript/Node.js"},"mqtt-client":{"version":"1.1.1","platform":"Javascript/Node.js"},"rickshaw":{"version":"1.0.0","platform":"javascript/Node.js"},"samsung":{"version":"0.2.9","platform":"Javascript/Node.js"},"alexa2":{"version":"1.1.3","platform":"Javascript/Node.js"},"iot":{"version":"0.2.2","platform":"Javascript/Node.js"},"scenes":{"version":"1.1.0","platform":"Javascript/Node.js"},"amazon-dash":{"version":"0.3.1","platform":"Javascript/Node.js"},"weatherunderground":{"version":"2.0.4","platform":"Javascript/Node.js"},"shelly":{"version":"2.0.8","platform":"Javascript/Node.js"},"plexconnect":{"version":"0.0.7","platform":"Javascript/Node.js"}},"model":"unknown","cpus":4,"mem":4196204544,"ostype":"Linux","city":"","vis":249} 2019-02-25 19:56:04.180 - error: host.ioBroker-Rock64 instance system.adapter.history.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:04.181 - info: host.ioBroker-Rock64 Restart adapter system.adapter.history.0 because enabled 2019-02-25 19:56:04.893 - info: host.ioBroker-Rock64 instance system.adapter.socketio.0 started with pid 25539 2019-02-25 19:56:05.870 - info: host.ioBroker-Rock64 instance system.adapter.vis.0 terminated while should be started once 2019-02-25 19:56:07.395 - error: host.ioBroker-Rock64 instance system.adapter.socketio.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:07.397 - info: host.ioBroker-Rock64 Restart adapter system.adapter.socketio.0 because enabled 2019-02-25 19:56:07.523 - error: host.ioBroker-Rock64 instance system.adapter.javascript.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:07.523 - info: host.ioBroker-Rock64 Restart adapter system.adapter.javascript.0 because enabled 2019-02-25 19:56:08.890 - info: host.ioBroker-Rock64 instance scheduled system.adapter.ical.0 0,30 * * * * 2019-02-25 19:56:08.924 - info: host.ioBroker-Rock64 instance system.adapter.ical.0 started with pid 25553 2019-02-25 19:56:12.886 - info: host.ioBroker-Rock64 instance system.adapter.text2command.0 started with pid 25563 2019-02-25 19:56:14.378 - error: host.ioBroker-Rock64 instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:14.379 - info: host.ioBroker-Rock64 Restart adapter system.adapter.text2command.0 because enabled 2019-02-25 19:56:16.885 - info: host.ioBroker-Rock64 instance system.adapter.sayit.0 started with pid 25573 2019-02-25 19:56:18.485 - error: host.ioBroker-Rock64 instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:18.486 - info: host.ioBroker-Rock64 Restart adapter system.adapter.sayit.0 because enabled 2019-02-25 19:56:20.851 - error: host.ioBroker-Rock64 startInstance js-controller.0: cannot find start file! 2019-02-25 19:56:21.265 - info: host.ioBroker-Rock64 instance system.adapter.admin.0 started with pid 25587 2019-02-25 19:56:23.265 - info: host.ioBroker-Rock64 instance system.adapter.web.0 started with pid 25593 2019-02-25 19:56:24.888 - info: host.ioBroker-Rock64 instance system.adapter.fritzbox.0 started with pid 25603 2019-02-25 19:56:25.005 - error: host.ioBroker-Rock64 instance system.adapter.admin.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:25.006 - info: host.ioBroker-Rock64 Restart adapter system.adapter.admin.0 because enabled 2019-02-25 19:56:25.845 - error: host.ioBroker-Rock64 instance system.adapter.web.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:25.846 - info: host.ioBroker-Rock64 Restart adapter system.adapter.web.0 because enabled 2019-02-25 19:56:26.451 - info: host.ioBroker-Rock64 instance system.adapter.ical.0 terminated with code 0 (OK) TypeError: Cannot read property 'debug' of undefined at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.fritzbox/main.js:130:17) at emitOne (events.js:116:13) at Adapter.emit (events.js:211:7) at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5033:18) at Object.onceWrapper (events.js:315:30) at emitOne (events.js:116:13) at process.emit (events.js:211:7) at process.exit (internal/process.js:146:15) at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:780:25 at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:236:17) 2019-02-25 19:56:28.857 - info: host.ioBroker-Rock64 instance scheduled system.adapter.dwd.0 3 * * * * 2019-02-25 19:56:28.905 - info: host.ioBroker-Rock64 instance system.adapter.dwd.0 started with pid 25617 2019-02-25 19:56:32.476 - info: host.ioBroker-Rock64 instance system.adapter.dwd.0 terminated with code 0 (OK) 2019-02-25 19:56:32.880 - info: host.ioBroker-Rock64 instance system.adapter.telegram.0 started with pid 25627 2019-02-25 19:56:34.218 - info: host.ioBroker-Rock64 instance system.adapter.history.0 started with pid 25633 2019-02-25 19:56:35.925 - error: host.ioBroker-Rock64 instance system.adapter.history.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:35.926 - info: host.ioBroker-Rock64 Restart adapter system.adapter.history.0 because enabled Mon, 25 Feb 2019 18:56:36 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. In the future, you will have to enable it yourself. See Link Removed. at module.js:653:30 2019-02-25 19:56:36.860 - info: host.ioBroker-Rock64 instance scheduled system.adapter.tvspielfilm.0 */5 * * * * 2019-02-25 19:56:36.895 - info: host.ioBroker-Rock64 instance system.adapter.tvspielfilm.0 started with pid 25643 2019-02-25 19:56:37.115 - error: Caught by controller[0]: Mon, 25 Feb 2019 18:56:36 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. 2019-02-25 19:56:37.116 - error: Caught by controller[0]: In the future, you will have to enable it yourself. 2019-02-25 19:56:37.117 - error: Caught by controller[0]: See Link Removed. at module.js:653:30 2019-02-25 19:56:37.118 - error: host.ioBroker-Rock64 instance system.adapter.telegram.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:37.120 - info: host.ioBroker-Rock64 Restart adapter system.adapter.telegram.0 because enabled 2019-02-25 19:56:37.432 - info: host.ioBroker-Rock64 instance system.adapter.socketio.0 started with pid 25653 2019-02-25 19:56:37.564 - info: host.ioBroker-Rock64 instance system.adapter.javascript.0 started with pid 25659 2019-02-25 19:56:38.163 - info: host.ioBroker-Rock64 instance system.adapter.telegram.0 started with pid 25665 2019-02-25 19:56:39.910 - error: host.ioBroker-Rock64 instance system.adapter.socketio.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:39.912 - info: host.ioBroker-Rock64 Restart adapter system.adapter.socketio.0 because enabled 2019-02-25 19:56:40.894 - info: host.ioBroker-Rock64 instance system.adapter.simple-api.0 started with pid 25679 Mon, 25 Feb 2019 18:56:42 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. In the future, you will have to enable it yourself. See Link Removed. at module.js:653:30 2019-02-25 19:56:42.625 - error: host.ioBroker-Rock64 instance system.adapter.javascript.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:42.626 - info: host.ioBroker-Rock64 Restart adapter system.adapter.javascript.0 because enabled 2019-02-25 19:56:43.013 - error: host.ioBroker-Rock64 instance system.adapter.simple-api.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:43.014 - info: host.ioBroker-Rock64 Restart adapter system.adapter.simple-api.0 because enabled 2019-02-25 19:56:44.412 - info: host.ioBroker-Rock64 instance system.adapter.text2command.0 started with pid 25697 2019-02-25 19:56:44.887 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 started with pid 25703 2019-02-25 19:56:46.073 - error: host.ioBroker-Rock64 instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:46.074 - info: host.ioBroker-Rock64 Restart adapter system.adapter.text2command.0 because enabled 2019-02-25 19:56:46.651 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:46.652 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.0 because enabled 2019-02-25 19:56:48.518 - info: host.ioBroker-Rock64 instance system.adapter.sayit.0 started with pid 25717 2019-02-25 19:56:48.884 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 started with pid 25723 2019-02-25 19:56:50.138 - error: host.ioBroker-Rock64 instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:50.139 - info: host.ioBroker-Rock64 Restart adapter system.adapter.sayit.0 because enabled 2019-02-25 19:56:50.573 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running) 2019-02-25 19:56:50.574 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.1 because enabled 2019-02-25 19:56:52.884 - info: host.ioBroker-Rock64 instance system.adapter.samsung.0 started with pid 25737 2019-02-25 19:56:54.545 - error: host.ioBroker-Rock64 instance system.adapter.samsung.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:54.546 - info: host.ioBroker-Rock64 Restart adapter system.adapter.samsung.0 because enabled 2019-02-25 19:56:55.039 - info: host.ioBroker-Rock64 instance system.adapter.admin.0 started with pid 25747 2019-02-25 19:56:55.882 - info: host.ioBroker-Rock64 instance system.adapter.web.0 started with pid 25753 2019-02-25 19:56:56.902 - info: host.ioBroker-Rock64 instance system.adapter.hm-rega.0 started with pid 25759 2019-02-25 19:56:58.354 - error: host.ioBroker-Rock64 instance system.adapter.web.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:58.355 - info: host.ioBroker-Rock64 Restart adapter system.adapter.web.0 because enabled 2019-02-25 19:56:58.567 - error: host.ioBroker-Rock64 instance system.adapter.admin.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:58.568 - info: host.ioBroker-Rock64 Restart adapter system.adapter.admin.0 because enabled 2019-02-25 19:56:59.858 - error: host.ioBroker-Rock64 instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:59.859 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rega.0 because enabled 2019-02-25 19:57:00.875 - info: host.ioBroker-Rock64 instance system.adapter.cloud.0 started with pid 25777 2019-02-25 19:57:03.241 - error: host.ioBroker-Rock64 instance system.adapter.cloud.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:03.242 - info: host.ioBroker-Rock64 Restart adapter system.adapter.cloud.0 because enabled 2019-02-25 19:57:04.873 - info: host.ioBroker-Rock64 instance system.adapter.alexa2.0 started with pid 25787 2019-02-25 19:57:05.952 - info: host.ioBroker-Rock64 instance system.adapter.history.0 started with pid 25793 2019-02-25 19:57:06.720 - error: host.ioBroker-Rock64 instance system.adapter.alexa2.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:06.721 - info: host.ioBroker-Rock64 Restart adapter system.adapter.alexa2.0 because enabled 2019-02-25 19:57:07.486 - error: host.ioBroker-Rock64 instance system.adapter.history.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:07.487 - info: host.ioBroker-Rock64 Restart adapter system.adapter.history.0 because enabled 2019-02-25 19:57:08.873 - info: host.ioBroker-Rock64 instance system.adapter.iot.0 started with pid 25807 2019-02-25 19:57:09.937 - info: host.ioBroker-Rock64 instance system.adapter.socketio.0 started with pid 25813 2019-02-25 19:57:11.972 - error: host.ioBroker-Rock64 instance system.adapter.socketio.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:11.973 - info: host.ioBroker-Rock64 Restart adapter system.adapter.socketio.0 because enabled 2019-02-25 19:57:12.264 - error: host.ioBroker-Rock64 instance system.adapter.iot.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:12.265 - info: host.ioBroker-Rock64 Restart adapter system.adapter.iot.0 because enabled 2019-02-25 19:57:12.647 - info: host.ioBroker-Rock64 instance system.adapter.javascript.0 started with pid 25827 2019-02-25 19:57:12.874 - info: host.ioBroker-Rock64 instance system.adapter.scenes.0 started with pid 25833 2019-02-25 19:57:13.042 - info: host.ioBroker-Rock64 instance system.adapter.simple-api.0 started with pid 25839 2019-02-25 19:57:14.840 - error: host.ioBroker-Rock64 instance system.adapter.scenes.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:14.841 - info: host.ioBroker-Rock64 Restart adapter system.adapter.scenes.0 because enabled 2019-02-25 19:57:14.913 - error: host.ioBroker-Rock64 instance system.adapter.simple-api.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:14.914 - info: host.ioBroker-Rock64 Restart adapter system.adapter.simple-api.0 because enabled 2019-02-25 19:57:16.099 - info: host.ioBroker-Rock64 instance system.adapter.text2command.0 started with pid 25853 2019-02-25 19:57:16.678 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 started with pid 25859 2019-02-25 19:57:16.851 - error: host.ioBroker-Rock64 instance system.adapter.javascript.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:16.853 - info: host.ioBroker-Rock64 Restart adapter system.adapter.javascript.0 because enabled 2019-02-25 19:57:16.879 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.2 started with pid 25869 2019-02-25 19:57:17.926 - error: host.ioBroker-Rock64 instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:17.928 - info: host.ioBroker-Rock64 Restart adapter system.adapter.text2command.0 because enabled 2019-02-25 19:57:18.584 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:18.585 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.0 because enabled 2019-02-25 19:57:18.738 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.2 terminated with code 7 (Adapter already running) 2019-02-25 19:57:18.739 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.2 because enabled 2019-02-25 19:57:20.161 - info: host.ioBroker-Rock64 instance system.adapter.sayit.0 started with pid 25887 2019-02-25 19:57:20.598 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 started with pid 25893 2019-02-25 19:57:20.864 - info: host.ioBroker-Rock64 instance scheduled system.adapter.weatherunderground.0 12 * * * * 2019-02-25 19:57:21.772 - error: host.ioBroker-Rock64 instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:21.773 - info: host.ioBroker-Rock64 Restart adapter system.adapter.sayit.0 because enabled 2019-02-25 19:57:22.301 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running) 2019-02-25 19:57:22.302 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.1 because enabled 2019-02-25 19:57:24.568 - info: host.ioBroker-Rock64 instance system.adapter.samsung.0 started with pid 25907 2019-02-25 19:57:24.874 - info: host.ioBroker-Rock64 instance system.adapter.shelly.0 started with pid 25913 2019-02-25 19:57:26.261 - error: host.ioBroker-Rock64 instance system.adapter.samsung.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:26.262 - info: host.ioBroker-Rock64 Restart adapter system.adapter.samsung.0 because enabled 2019-02-25 19:57:26.848 - error: host.ioBroker-Rock64 instance system.adapter.shelly.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:26.849 - info: host.ioBroker-Rock64 Restart adapter system.adapter.shelly.0 because enabled 2019-02-25 19:57:28.377 - info: host.ioBroker-Rock64 instance system.adapter.web.0 started with pid 25931 2019-02-25 19:57:28.592 - info: host.ioBroker-Rock64 instance system.adapter.admin.0 started with pid 25937 2019-02-25 19:57:29.886 - info: host.ioBroker-Rock64 instance system.adapter.hm-rega.0 started with pid 25943 2019-02-25 19:57:30.776 - error: host.ioBroker-Rock64 instance system.adapter.web.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:30.777 - info: host.ioBroker-Rock64 Restart adapter system.adapter.web.0 because enabled 2019-02-25 19:57:32.099 - error: host.ioBroker-Rock64 instance system.adapter.admin.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:32.103 - info: host.ioBroker-Rock64 Restart adapter system.adapter.admin.0 because enabled 2019-02-25 19:57:32.480 - error: host.ioBroker-Rock64 instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:32.481 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rega.0 because enabled 2019-02-25 19:57:33.264 - info: host.ioBroker-Rock64 instance system.adapter.cloud.0 started with pid 25961 2019-02-25 19:57:35.456 - error: host.ioBroker-Rock64 instance system.adapter.cloud.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:35.457 - info: host.ioBroker-Rock64 Restart adapter system.adapter.cloud.0 because enabled 2019-02-25 19:57:36.746 - info: host.ioBroker-Rock64 instance system.adapter.alexa2.0 started with pid 25971 2019-02-25 19:57:37.512 - info: host.ioBroker-Rock64 instance system.adapter.history.0 started with pid 25977 2019-02-25 19:57:38.516 - error: host.ioBroker-Rock64 instance system.adapter.alexa2.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:38.517 - info: host.ioBroker-Rock64 Restart adapter system.adapter.alexa2.0 because enabled 2019-02-25 19:57:39.076 - error: host.ioBroker-Rock64 instance system.adapter.history.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:39.077 - info: host.ioBroker-Rock64 Restart adapter system.adapter.history.0 because enabled 2019-02-25 19:57:40.789 - info: host.ioBroker-Rock64 instance system.adapter.tvspielfilm.0 terminated with code 0 (OK) 2019-02-25 19:57:42.008 - info: host.ioBroker-Rock64 instance system.adapter.socketio.0 started with pid 25991 2019-02-25 19:57:42.289 - info: host.ioBroker-Rock64 instance system.adapter.iot.0 started with pid 25997 2019-02-25 19:57:44.134 - error: host.ioBroker-Rock64 instance system.adapter.socketio.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:44.135 - info: host.ioBroker-Rock64 Restart adapter system.adapter.socketio.0 because enabled 2019-02-25 19:57:44.869 - info: host.ioBroker-Rock64 instance system.adapter.scenes.0 started with pid 26007 2019-02-25 19:57:44.939 - info: host.ioBroker-Rock64 instance system.adapter.simple-api.0 started with pid 26013 2019-02-25 19:57:45.272 - error: host.ioBroker-Rock64 instance system.adapter.iot.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:45.274 - info: host.ioBroker-Rock64 Restart adapter system.adapter.iot.0 because enabled 2019-02-25 19:57:46.560 - error: host.ioBroker-Rock64 instance system.adapter.scenes.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:46.561 - info: host.ioBroker-Rock64 Restart adapter system.adapter.scenes.0 because enabled 2019-02-25 19:57:46.601 - error: host.ioBroker-Rock64 instance system.adapter.simple-api.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:46.602 - info: host.ioBroker-Rock64 Restart adapter system.adapter.simple-api.0 because enabled 2019-02-25 19:57:46.874 - info: host.ioBroker-Rock64 instance system.adapter.javascript.0 started with pid 26031 2019-02-25 19:57:47.951 - info: host.ioBroker-Rock64 instance system.adapter.text2command.0 started with pid 26037 2019-02-25 19:57:48.613 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 started with pid 26043 2019-02-25 19:57:48.768 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.2 started with pid 26049 2019-02-25 19:57:49.860 - error: host.ioBroker-Rock64 instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:49.862 - info: host.ioBroker-Rock64 Restart adapter system.adapter.text2command.0 because enabled 2019-02-25 19:57:50.670 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:50.671 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.0 because enabled 2019-02-25 19:57:50.831 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.2 terminated with code 7 (Adapter already running) 2019-02-25 19:57:50.832 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.2 because enabled 2019-02-25 19:57:51.166 - error: host.ioBroker-Rock64 instance system.adapter.javascript.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:51.166 - info: host.ioBroker-Rock64 Restart adapter system.adapter.javascript.0 because enabled 2019-02-25 19:57:51.795 - info: host.ioBroker-Rock64 instance system.adapter.sayit.0 started with pid 26071 2019-02-25 19:57:52.326 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 started with pid 26077 2019-02-25 19:57:53.366 - error: host.ioBroker-Rock64 instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:53.367 - info: host.ioBroker-Rock64 Restart adapter system.adapter.sayit.0 because enabled 2019-02-25 19:57:53.975 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running) 2019-02-25 19:57:53.976 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.1 because enabled 2019-02-25 19:57:56.296 - info: host.ioBroker-Rock64 instance system.adapter.samsung.0 started with pid 26091Und dann geht es ewig so weiter.
Dass das VIS Json nicht parsebar ist muss ich noch getrennt untersuchen. VIS läuf eigentlich.
Gruss Ralf
-
@derrapf sagte in IOBroker hat sich beendet:
Ich habe das hier "ioBroker_Image_Rock64_20180419_stretch.img". Hilft Dir das?
Naja, zumindest für die Frage wie zu stoppen/nach dem Status zu fragen ist.
Da geht es immer noch mit (sudo) iobroker status
kann aber da noch gewesen sein, dass das im Veruzeichnis /opt/iobroker ausgeführt werden mussABER:
Das ist ein so genannter "nightly build". Da sind eventuell Features drin, die noch nicht unbedingt stable sein müssen. -
@derrapf
Wo kommen denn diese "created this issue" unter "Gruss Ralf" her? Die hab ich nicht getippt... -
Das Image hat jetzt wochenlang super funktioniert.
Also an Deinem Image kann es nicht gelegen haben.Was ich gemacht habe war:
Ich habe ein paar Scripte zum loggen von offenen Fenstern, Licht und zum Sammeln der IObroker Logs für VIS hinzugefügt. Speziell das Sammeln der IOBroker Logs für VIS hat den javascript Adapter auf 100% CPU gebracht. Deshalb hab ich das wieder disabled.
Ich schmeiss die jetzt alle wieder weg,Ansonsten habe ich hm-rega und alexa.2 upgedatet. Der Absturz vom js-controller ist aber schon vor dem alexa.2 Update passiert.
Beide Adapter haben Probleme beim Update gemacht. Man musste in beiden Adaptern die Dateien in den .../node_modules/.bin Verzeichnissen wegmoven, dann updaten und dann wieder zurückspielen. Ansonsten gab es jedes Mal Fehler vom npn, dass er auf die Dateien nicht zugreifen kann. Neue wurden aber auch nicht installiert. Also hab ich die Alten wieder zurück gemoved.
Gruss Ralf -
@derrapf
Das ist ein Forum-Feature, wo Infos aus einem Beitrag, die nach GitHub-Referenzen aussehen, entsprechende Infoblöcke unter dem Beitrag auslösen.Da braucht es ggf. noch Finetuning.
-
@Stabilostick sagte in IOBroker hat sich beendet:
@derrapf
Das ist ein Forum-Feature, wo Infos aus einem Beitrag, die nach GitHub-Referenzen aussehen, entsprechende Infoblöcke unter dem Beitrag auslösen.Da braucht es ggf. noch Finetuning.
Ah Ok, Ich dachte schon ich seh Gespenster.
-
Das steht in Deinem Logauszug:
See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30Ist doch ganz praktisch, oder?
-
Hi
Jetzt sind die "Created issues" weg. Hast du was gemacht?
Ich hab mal den Link aufgerufen aber nur relativ viel Bahnhof verstanden. Vor allem was das für "Versprechen" sind die da in use sind. Muss mich das issue interessieren? Kann das mit dem Absturz des js-controllers zu tun haben?
Gruss Ralf -
Hier hab ich noch was gefunden. Weiss aber nicht ob das ein relevanter Fehler ist:
iot.0 2019-02-25 20:33:57.703 warn Invalid URL key. Status update is disabled: {"error":"Unsupported version"} iot.0 2019-02-25 20:33:57.701 error Cannot report device state: nullGruss Ralf
-
Jay-Cee hat den Link in Deinem Log entfernt. Dann verschwinden auch die Boxen. An meinem Beispiel oben siehst Du, auf was die GitHub-Box triggert. Aber jetzt zurück zu Deinem eigentlichen Thema...
-
@Stabilostick
Danke.
Also ich habe jetzt mal die Java-Scripts stillgelegt. Und zwar alle die ich aus dem Netz rauskopiert und eingefügt hatte. Das war einmal eines zum Aufbereiten der IOBroker Logs damit man die in VIS anzeigen kann, und eines das die Anzahl der offenen Fenster zählt bzw. auflistet.
Seit ich das gemacht habe (also vor knapp einer Woche) lief der IOBroker stabil.
Heute hab ich allerdings ein anderes Problem gehabt. Weiss aber nicht ob es da Zusammenhänge gibt: Alle Geräte in der Alexa App waren offline. Auch neu Suchen hat nicht funktioniert. Alles wegwerfen und neu suchen auch nicht. Musste komplett den Skill neu installieren. Sehr seltsam.
Ich hoffe jetzt mal, dass es wirklich nur rein an den Scripten lag. Jetzt schalte ich die mal nacheinander wieder ein. Mal sehen ob er dann wieder instabil wird.
Gruss Ralf -
Inzwischen hat sich der js-controller schon wieder beendet, ohne dass ich eines der Scripten wieder aktiviert hätte. Schade. Daran lag es wohl nicht.
Gibt es irgend eine Möglichkeit das Problem einzugrenzen? Ich sehe im Log nichts auffälliges. Und auch im Syslog nichts.
(also damit meine ich, dass ich als Linux Laie nichts sehe..)Ich kann die Logs hier einstellen, aber ich müsste wissen welche für Euch interessant sind...
Gruss Ralf -
Erster Anlaufpunkt ist immer das ioBroker Log. Wenn das nichts enthält und sich der ioBroker "einfach so" beednet ist /var/log/syslog der nächste Anlaufpunkt. Dort vor allem nach "oom" ausschau halten - wenn wenn das drin ist war der RAM voll
-
@apollon77 sagte in IOBroker hat sich beendet:
Erster Anlaufpunkt ist immer das ioBroker Log. Wenn das nichts enthält und sich der ioBroker "einfach so" beednet ist /var/log/syslog der nächste Anlaufpunkt. Dort vor allem nach "oom" ausschau halten - wenn wenn das drin ist war der RAM voll
Nee "oom" kommt nirgends vor. Ich hab mal die beiden Logs gezippt.
-
Ich denke der schuldige Teil ist der hier:
Mar 4 02:15:14 localhost systemd[2008]: Stopped target Default. Mar 4 02:15:14 localhost systemd[2008]: Stopped target Basic System. Mar 4 02:15:14 localhost systemd[2008]: Stopped target Paths. Mar 4 02:15:14 localhost systemd[2008]: Stopped target Timers. Mar 4 02:15:14 localhost systemd[2008]: Stopped target Sockets. Mar 4 02:15:14 localhost systemd[2008]: Closed GnuPG cryptographic agent (ssh-agent emulation). Mar 4 02:15:14 localhost systemd[2008]: Closed GnuPG cryptographic agent and passphrase cache. Mar 4 02:15:14 localhost systemd[2008]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Mar 4 02:15:14 localhost systemd[2008]: Closed GnuPG cryptographic agent (access for web browsers). Mar 4 02:15:14 localhost systemd[2008]: Closed GnuPG network certificate management daemon. Mar 4 02:15:14 localhost systemd[2008]: Reached target Shutdown. Mar 4 02:15:14 localhost systemd[2008]: Starting Exit the Session... Mar 4 02:15:14 localhost systemd[2008]: Received SIGRTMIN+24 from PID 26362 (kill). Mar 4 02:15:14 localhost systemd[1]: Stopped User Manager for UID 0. Mar 4 02:15:14 localhost systemd[1]: Removed slice User Slice of root.Kann es ein das Du ioBroker mal per root manuell per Shell gestartet hast? Aso da wurde der user root quasi final ausgeloggt ... und das hat wohl den ioBroker gekillt.
Was auch immer es war
