NEWS
Kein Start mehr nach reboot vom PI
-
Hallo,
mein iobroker wollte nach einem Neustart des PI nicht mehr hochfahren:
2015-09-29 18:28:36.992 - info: host.raspberrypi ioBroker.js-controller version 0.7.11 js-controller starting 2015-09-29 18:28:37.008 - info: host.raspberrypi Copyright (c) 2014-2015 bluefox, hobbyquaker 2015-09-29 18:28:37.010 - info: host.raspberrypi hostname: raspberrypi 2015-09-29 18:28:37.011 - info: host.raspberrypi ip addresses: 192.168.1.12 192.168.1.185 2015-09-29 18:28:45.019 - info: inMem-states listening on port 9000 2015-09-29 18:28:45.615 - info: inMem-objects listening on port 9001 2015-09-29 18:28:45.630 - info: host.raspberrypi InMemoryDB connected 2015-09-29 18:28:45.671 - info: host.raspberrypi 26 instances found 2015-09-29 18:28:45.675 - warn: host.raspberrypi does not start any instances on this host 2015-09-29 18:30:27.520 - info: host.raspberrypi received SIGTERM 2015-09-29 18:30:27.619 - info: host.raspberrypi terminated 2015-09-29 18:30:28.523 - info: host.raspberrypi received SIGTERM 2015-09-29 18:30:28.610 - info: host.raspberrypi terminated 2015-09-29 18:30:36.981 - info: host.raspberrypi ioBroker.js-controller version 0.7.11 js-controller starting 2015-09-29 18:30:36.993 - info: host.raspberrypi Copyright (c) 2014-2015 bluefox, hobbyquaker 2015-09-29 18:30:36.994 - info: host.raspberrypi hostname: raspberrypi 2015-09-29 18:30:36.994 - info: host.raspberrypi ip addresses: 192.168.1.12 192.168.1.185 2015-09-29 18:30:45.044 - info: inMem-states listening on port 9000 2015-09-29 18:30:45.654 - info: inMem-objects listening on port 9001 2015-09-29 18:30:45.668 - info: host.raspberrypi InMemoryDB connected 2015-09-29 18:30:45.709 - info: host.raspberrypi 26 instances found 2015-09-29 18:30:45.713 - warn: host.raspberrypi does not start any instances on this host 2015-09-29 18:32:41.736 - info: host.raspberrypi received SIGTERM 2015-09-29 18:32:41.742 - info: host.raspberrypi stopInstance system.adapter.admin.0 2015-09-29 18:32:41.743 - warn: host.raspberrypi stopInstance system.adapter.admin.0 not running 2015-09-29 18:32:41.743 - info: host.raspberrypi stopInstance system.adapter.web.0 2015-09-29 18:32:41.744 - warn: host.raspberrypi stopInstance system.adapter.web.0 not running 2015-09-29 18:32:41.744 - info: host.raspberrypi stopInstance system.adapter.vis.0 2015-09-29 18:32:41.744 - info: host.raspberrypi stopInstance system.adapter.vis-metro.0 2015-09-29 18:32:41.744 - info: host.raspberrypi stopInstance system.adapter.vis-lcars.0 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.vis-hqwidgets.0 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.vis-bars.0 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.vis-plumb.0 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 2015-09-29 18:32:41.745 - warn: host.raspberrypi stopInstance system.adapter.hm-rpc.0 not running 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 2015-09-29 18:32:41.746 - warn: host.raspberrypi stopInstance system.adapter.hm-rega.0 not running 2015-09-29 18:32:41.746 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 2015-09-29 18:32:41.746 - warn: host.raspberrypi stopInstance system.adapter.hm-rpc.1 not running 2015-09-29 18:32:41.746 - info: host.raspberrypi stopInstance system.adapter.vis-colorpicker.0 2015-09-29 18:32:41.746 - info: host.raspberrypi stopInstance system.adapter.fritzbox.0 2015-09-29 18:32:41.747 - warn: host.raspberrypi stopInstance system.adapter.fritzbox.0 not running 2015-09-29 18:32:41.747 - info: host.raspberrypi stopInstance system.adapter.javascript.0 2015-09-29 18:32:41.747 - warn: host.raspberrypi stopInstance system.adapter.javascript.0 not running 2015-09-29 18:32:41.747 - info: host.raspberrypi stopInstance system.adapter.yr.0 2015-09-29 18:32:41.747 - warn: host.raspberrypi stopInstance system.adapter.yr.0 not scheduled 2015-09-29 18:32:41.747 - info: host.raspberrypi stopInstance system.adapter.node-red.0 2015-09-29 18:32:41.749 - warn: host.raspberrypi stopInstance system.adapter.node-red.0 not running 2015-09-29 18:32:41.750 - info: host.raspberrypi stopInstance system.adapter.history.0 2015-09-29 18:32:41.750 - warn: host.raspberrypi stopInstance system.adapter.history.0 not running 2015-09-29 18:32:41.750 - info: host.raspberrypi stopInstance system.adapter.ping.0 2015-09-29 18:32:41.750 - warn: host.raspberrypi stopInstance system.adapter.ping.0 not running 2015-09-29 18:32:41.842 - info: host.raspberrypi terminated 2015-09-29 18:32:42.740 - info: host.raspberrypi received SIGTERM 2015-09-29 18:32:56.633 - info: host.raspberrypi ioBroker.js-controller version 0.7.11 js-controller starting 2015-09-29 18:32:56.644 - info: host.raspberrypi Copyright (c) 2014-2015 bluefox, hobbyquaker 2015-09-29 18:32:56.646 - info: host.raspberrypi hostname: raspberrypi 2015-09-29 18:32:56.646 - info: host.raspberrypi ip addresses: 192.168.1.12 2015-09-29 18:33:18.610 - info: inMem-states listening on port 9000 2015-09-29 18:33:19.317 - info: inMem-objects listening on port 9001 2015-09-29 18:33:19.330 - info: host.raspberrypi InMemoryDB connected 2015-09-29 18:33:19.372 - info: host.raspberrypi 26 instances found 2015-09-29 18:33:19.376 - warn: host.raspberrypi does not start any instances on this host 2015-09-29 18:37:46.599 - info: host.raspberrypi received SIGTERM
Kann man am Log sehen, wo es hakt?
Ich habe das Backup des Data-Ordners von heute Nacht eingespielt, danach lief alles wieder.
-
Hallo,
mein iobroker wollte nach einem Neustart des PI nicht mehr hochfahren:
2015-09-29 18:28:36.992 - info: host.raspberrypi ioBroker.js-controller version 0.7.11 js-controller starting 2015-09-29 18:28:37.008 - info: host.raspberrypi Copyright (c) 2014-2015 bluefox, hobbyquaker 2015-09-29 18:28:37.010 - info: host.raspberrypi hostname: raspberrypi 2015-09-29 18:28:37.011 - info: host.raspberrypi ip addresses: 192.168.1.12 192.168.1.185 2015-09-29 18:28:45.019 - info: inMem-states listening on port 9000 2015-09-29 18:28:45.615 - info: inMem-objects listening on port 9001 2015-09-29 18:28:45.630 - info: host.raspberrypi InMemoryDB connected 2015-09-29 18:28:45.671 - info: host.raspberrypi 26 instances found 2015-09-29 18:28:45.675 - warn: host.raspberrypi does not start any instances on this host 2015-09-29 18:30:27.520 - info: host.raspberrypi received SIGTERM 2015-09-29 18:30:27.619 - info: host.raspberrypi terminated 2015-09-29 18:30:28.523 - info: host.raspberrypi received SIGTERM 2015-09-29 18:30:28.610 - info: host.raspberrypi terminated 2015-09-29 18:30:36.981 - info: host.raspberrypi ioBroker.js-controller version 0.7.11 js-controller starting 2015-09-29 18:30:36.993 - info: host.raspberrypi Copyright (c) 2014-2015 bluefox, hobbyquaker 2015-09-29 18:30:36.994 - info: host.raspberrypi hostname: raspberrypi 2015-09-29 18:30:36.994 - info: host.raspberrypi ip addresses: 192.168.1.12 192.168.1.185 2015-09-29 18:30:45.044 - info: inMem-states listening on port 9000 2015-09-29 18:30:45.654 - info: inMem-objects listening on port 9001 2015-09-29 18:30:45.668 - info: host.raspberrypi InMemoryDB connected 2015-09-29 18:30:45.709 - info: host.raspberrypi 26 instances found 2015-09-29 18:30:45.713 - warn: host.raspberrypi does not start any instances on this host 2015-09-29 18:32:41.736 - info: host.raspberrypi received SIGTERM 2015-09-29 18:32:41.742 - info: host.raspberrypi stopInstance system.adapter.admin.0 2015-09-29 18:32:41.743 - warn: host.raspberrypi stopInstance system.adapter.admin.0 not running 2015-09-29 18:32:41.743 - info: host.raspberrypi stopInstance system.adapter.web.0 2015-09-29 18:32:41.744 - warn: host.raspberrypi stopInstance system.adapter.web.0 not running 2015-09-29 18:32:41.744 - info: host.raspberrypi stopInstance system.adapter.vis.0 2015-09-29 18:32:41.744 - info: host.raspberrypi stopInstance system.adapter.vis-metro.0 2015-09-29 18:32:41.744 - info: host.raspberrypi stopInstance system.adapter.vis-lcars.0 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.vis-hqwidgets.0 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.vis-bars.0 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.vis-plumb.0 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 2015-09-29 18:32:41.745 - warn: host.raspberrypi stopInstance system.adapter.hm-rpc.0 not running 2015-09-29 18:32:41.745 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 2015-09-29 18:32:41.746 - warn: host.raspberrypi stopInstance system.adapter.hm-rega.0 not running 2015-09-29 18:32:41.746 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 2015-09-29 18:32:41.746 - warn: host.raspberrypi stopInstance system.adapter.hm-rpc.1 not running 2015-09-29 18:32:41.746 - info: host.raspberrypi stopInstance system.adapter.vis-colorpicker.0 2015-09-29 18:32:41.746 - info: host.raspberrypi stopInstance system.adapter.fritzbox.0 2015-09-29 18:32:41.747 - warn: host.raspberrypi stopInstance system.adapter.fritzbox.0 not running 2015-09-29 18:32:41.747 - info: host.raspberrypi stopInstance system.adapter.javascript.0 2015-09-29 18:32:41.747 - warn: host.raspberrypi stopInstance system.adapter.javascript.0 not running 2015-09-29 18:32:41.747 - info: host.raspberrypi stopInstance system.adapter.yr.0 2015-09-29 18:32:41.747 - warn: host.raspberrypi stopInstance system.adapter.yr.0 not scheduled 2015-09-29 18:32:41.747 - info: host.raspberrypi stopInstance system.adapter.node-red.0 2015-09-29 18:32:41.749 - warn: host.raspberrypi stopInstance system.adapter.node-red.0 not running 2015-09-29 18:32:41.750 - info: host.raspberrypi stopInstance system.adapter.history.0 2015-09-29 18:32:41.750 - warn: host.raspberrypi stopInstance system.adapter.history.0 not running 2015-09-29 18:32:41.750 - info: host.raspberrypi stopInstance system.adapter.ping.0 2015-09-29 18:32:41.750 - warn: host.raspberrypi stopInstance system.adapter.ping.0 not running 2015-09-29 18:32:41.842 - info: host.raspberrypi terminated 2015-09-29 18:32:42.740 - info: host.raspberrypi received SIGTERM 2015-09-29 18:32:56.633 - info: host.raspberrypi ioBroker.js-controller version 0.7.11 js-controller starting 2015-09-29 18:32:56.644 - info: host.raspberrypi Copyright (c) 2014-2015 bluefox, hobbyquaker 2015-09-29 18:32:56.646 - info: host.raspberrypi hostname: raspberrypi 2015-09-29 18:32:56.646 - info: host.raspberrypi ip addresses: 192.168.1.12 2015-09-29 18:33:18.610 - info: inMem-states listening on port 9000 2015-09-29 18:33:19.317 - info: inMem-objects listening on port 9001 2015-09-29 18:33:19.330 - info: host.raspberrypi InMemoryDB connected 2015-09-29 18:33:19.372 - info: host.raspberrypi 26 instances found 2015-09-29 18:33:19.376 - warn: host.raspberrypi does not start any instances on this host 2015-09-29 18:37:46.599 - info: host.raspberrypi received SIGTERM
Kann man am Log sehen, wo es hakt?
Ich habe das Backup des Data-Ordners von heute Nacht eingespielt, danach lief alles wieder. `
Name von raspberry host wurde geändert. -
Hallo,
nachdem ich das Backup (von iobroker) von der Nacht wieder eingespielt hatte, lief alles wieder.
Wo kann ich denn den Hostnamen ändern?
-
über die Konsole mit raspi-config
Gruß
Rainer
-
Hallo,
Danke. Da habe ich aber nichts gemacht. Hostname ist geblieben wie vorher.
-
` > 2015-09-29 18:28:45.671 - info: host.raspberrypi 26 instances found
2015-09-29 18:28:45.675 - warn: host.raspberrypi does not start any instances on this host `
Sagt, dass Adapter Instanzen existieren, aber nicht für diesen Host.Nächstes Mal
iobroker o get "system.adapter.admin.0" --pretty
Aufrufen und schauen "common.host" Wert.