Ja geil, der "Fixer" hat es gerichtet. Hab tausend Dank!

Das Log spukt folgendes aus:

pi@raspberrypi:/opt/iobroker $ node node_modules/iobroker.js-controller/controller.js --logs
2019-07-03 20:02:51.114  - info: host.raspberrypi iobroker.js-controller version 1.4.2 js-controller s                   tarting
2019-07-03 20:02:51.127  - info: host.raspberrypi Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
2019-07-03 20:02:51.129  - info: host.raspberrypi hostname: raspberrypi, node: v8.15.0
2019-07-03 20:02:51.139  - info: host.raspberrypi ip addresses: 192.168.2.121 fe80::ba27:ebff:fe8d:5f2                   6
2019-07-03 20:02:51.372  - info: host.raspberrypi  inMem-states listening on port 9000
2019-07-03 20:02:51.858  - info: host.raspberrypi  inMem-objects listening on port 9001
2019-07-03 20:02:51.909  - info: host.raspberrypi InMemoryDB connected
2019-07-03 20:02:51.954  - info: host.raspberrypi 16 instances found
host.raspberrypi check instance "system.adapter.admin.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.discovery.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.cloud.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.terminal.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.web.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.hue.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.mihome.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.yeelight-2.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.javascript.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.zigbee.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.mihome-vacuum.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.backitup.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.ble.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.scenes.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.alexa2.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.harmony.0" for host "raspberrypi"
2019-07-03 20:02:51.998  - info: host.raspberrypi starting 14 instances
2019-07-03 20:02:52.123  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 853
2019-07-03 20:02:52.180  - error: uncaught exception: EACCES: permission denied, open '/opt/iobroker/l                   og/iobroker.2019-07-03.log'
2019-07-03 20:02:52.182  - error: Error: EACCES: permission denied, open '/opt/iobroker/log/iobroker.2                   019-07-03.log'
2019-07-03 20:02:52.197  - info: iobroker _restart
2019-07-03 20:02:53.435  - info: iobroker Starting node restart.js
2019-07-03 20:02:53.496  - info: iobroker exit 0
EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../.                   ./../iobroker-data/objects.json.bak'
Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/                   ../../../../iobroker-data/objects.json.bak'
    at Object.fs.openSync (fs.js:646:18)
    at Object.fs.writeFileSync (fs.js:1299:33)
    at Timeout.saveConfig [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/lib/objec                   ts/objectsInMemServer.js:1897:16)
    at ontimeout (timers.js:498:11)
    at tryOnTimeout (timers.js:323:5)
    at Timer.listOnTimeout (timers.js:290:5)

Re: Startseite iobroker nicht erreichbar

Hallo,
es gibt zwar schon einiger ähnliche Beiträge, aber mit allem, was dort diskutiert wird, komme ich nicht weiter.
Nach einem Stromausfalls erreiche ich meinen ioBroker über die Weboberfläche nicht mehr und meine Skripte werden auch nicht mehr ausgeführt. Über Putty komme ich auf den ioBroker, hab ihn und auch den raspberry auch schon neugestartet, hat aber nichts gebracht. Hier mal die Liste der Adapter:

Spoiler

pi@raspberrypi:~ $ iobroker list instances
system.adapter.admin.0 : admin - enabled, port: 8081, bin d: 0.0.0.0, run as: admin
system.adapter.alexa2.0 : alexa2 - enabled
system.adapter.backitup.0 : backitup - enabled
system.adapter.ble.0 : ble - disabled
system.adapter.cloud.0 : cloud - enabled
system.adapter.discovery.0 : discovery - enabled
system.adapter.harmony.0 : harmony - enabled
system.adapter.hue.0 : hue - enabled, port: 80
system.adapter.javascript.0 : javascript - enabled
system.adapter.mihome-vacuum.0 : mihome-vacuum - enabled, port: 54321
system.adapter.mihome.0 : mihome - disabled, port: 9898, bin d: 0.0.0.0
system.adapter.scenes.0 : scenes - enabled
system.adapter.terminal.0 : terminal - enabled, port: 8088, bin d: 0.0.0.0, run as: admin
system.adapter.web.0 : web - enabled, port: 8082, bin d: 0.0.0.0, run as: admin
system.adapter.yeelight-2.0 : yeelight-2 - enabled
system.adapter.zigbee.0 : zigbee - enabled, port: /dev/seri al/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001936AA0C-if00

Hat jemand eine Idee? Vielen lieben Dank.