NEWS
Error: ENOSPC: no space left on device, write
ioBroker Allgemein
3
Beiträge
3
Kommentatoren
1.8k
Aufrufe
2
Watching
-
Hallo,
nach ich den Installer-Fix installiert und anschließend alle Adapter ge-updated habe, startet mein iobroker nicht mehr.
Die logs vom controller zeigen das hier:
pi@ioBroker-RasPi:/opt/iobroker $ node node_modules/iobroker.js-controller/controller.js --logs 2019-03-28 11:21:59.148 - info: host.ioBroker-RasPi iobroker.js-controller version 1.4.0 js-controller starting 2019-03-28 11:21:59.155 - info: host.ioBroker-RasPi Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker 2019-03-28 11:21:59.155 - info: host.ioBroker-RasPi hostname: ioBroker-RasPi, node: v8.11.1 2019-03-28 11:21:59.160 - info: host.ioBroker-RasPi ip addresses: 192.168.178.77 fe80::cdf3:6e27:1bba:5721 2019-03-28 11:22:00.129 - error: host.ioBroker-RasPi Cannot parse /opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json: SyntaxError: Unexpected end of JSON input 2019-03-28 11:22:00.131 - error: host.ioBroker-RasPi Cannot parse /opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak: SyntaxError: Unexpected end of JSON input 2019-03-28 11:22:00.152 - info: host.ioBroker-RasPi inMem-objects listening on port 9001 2019-03-28 11:22:00.333 - info: host.ioBroker-RasPi States connected to redis: 127.0.0.1:6379 2019-03-28 11:22:00.337 - info: host.ioBroker-RasPi InMemoryDB connected Cannot find view "system" Cannot find view "system" 2019-03-28 11:22:00.354 - error: host.ioBroker-RasPi _design/system missing - call node iobroker.js setup 2019-03-28 11:22:00.383 - error: uncaught exception: Cannot convert undefined or null to object 2019-03-28 11:22:00.386 - error: TypeError: Cannot convert undefined or null to object at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:863:9) at runCallback (timers.js:798:20) at tryOnImmediate (timers.js:752:5) at processImmediate [as _immediateCallback] (timers.js:729:5) 2019-03-28 11:22:00.402 - error: ENOSPC: no space left on device, write fs.js:735 return binding.writeBuffer(fd, buffer, offset, length, position); ^ Error: ENOSPC: no space left on device, write at Object.fs.writeSync (fs.js:735:20) at Object.fs.writeFileSync (fs.js:1309:24) at saveConfig (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:1897:16) at ObjectsInMemServer.destroy (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:3088:26) at /opt/iobroker/node_modules/iobroker.js-controller/controller.js:2435:49 at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:2415:45) at stop (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:2434:5) at process.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:2614:9) at emitOne (events.js:116:13) at process.emit (events.js:211:7)Es gibt insgesamt 6 errors, von welchem ich jetzt nicht weiß, ob alle stimmen.
Kennt jemand diese Meldung und kann mir sagen, was ich nun tun kann um meinen iobroker wieder ans laufen zu bekommen?
Grüße,
Christian