NEWS
[gelöst] Backitup macht keine Backups mehr.
-
@simatec, sorry f
ü
r die sp
ä
te R
ü
ckmeldung.Hier das Log von Heute Nacht. Habe inzwischen den Adapter gel
ö
scht und neu installiert sowie das System neu gestartet.2019-02-22 03:00:10.082 - debug: backitup.0 [total] exec: done 2019-02-22 03:00:10.599 - error: backitup.0 uncaught exception: Cannot read property 'val' of null 2019-02-22 03:00:10.600 - error: backitup.0 TypeError: Cannot read property 'val' of null at Socket.adapter.getState (/opt/iobroker/node_modules/iobroker.backitup/main.js:208:39) at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9) at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12) at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15) at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20) at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8) at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15) at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20) at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12) at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16) 2019-02-22 03:00:11.676 - error: Caught by controller[0]: TypeError: Cannot read property 'val' of null 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Socket.adapter.getState (/opt/iobroker/node_modules/iobroker.backitup/main.js:208:39) 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9) 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12) 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15) 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16) 2019-02-22 03:00:11.680 - error: host.ioBroker-Master instance system.adapter.backitup.0 terminated with code 6 (uncaught exception) 2019-02-22 03:00:11.680 - info: host.ioBroker-Master Restart adapter system.adapter.backitup.0 because enabled 2019-02-22 03:00:41.712 - info: host.ioBroker-Master instance system.adapter.backitup.0 started with pid 27000 2019-02-22 03:00:44.287 - debug: backitup.0 objectDB connected 2019-02-22 03:00:44.337 - debug: backitup.0 statesDB connected 2019-02-22 03:00:44.452 - info: backitup.0 starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.14.0 2019-02-22 03:00:44.665 - info: backitup.0 [total] backup was activated at 03:00 every 1 day(s) 2019-02-22 03:00:44.712 - debug: backitup.0 [total] 10 00 03 */1 * *Nodejs = 0.8.15
NPM 6.8.0
Backitup 1.1.2 -
@simatec, sorry f
ü
r die sp
ä
te R
ü
ckmeldung.Hier das Log von Heute Nacht. Habe inzwischen den Adapter gel
ö
scht und neu installiert sowie das System neu gestartet.2019-02-22 03:00:10.082 - debug: backitup.0 [total] exec: done 2019-02-22 03:00:10.599 - error: backitup.0 uncaught exception: Cannot read property 'val' of null 2019-02-22 03:00:10.600 - error: backitup.0 TypeError: Cannot read property 'val' of null at Socket.adapter.getState (/opt/iobroker/node_modules/iobroker.backitup/main.js:208:39) at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9) at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12) at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15) at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20) at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8) at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15) at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20) at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12) at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16) 2019-02-22 03:00:11.676 - error: Caught by controller[0]: TypeError: Cannot read property 'val' of null 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Socket.adapter.getState (/opt/iobroker/node_modules/iobroker.backitup/main.js:208:39) 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9) 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12) 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15) 2019-02-22 03:00:11.678 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12) 2019-02-22 03:00:11.679 - error: Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16) 2019-02-22 03:00:11.680 - error: host.ioBroker-Master instance system.adapter.backitup.0 terminated with code 6 (uncaught exception) 2019-02-22 03:00:11.680 - info: host.ioBroker-Master Restart adapter system.adapter.backitup.0 because enabled 2019-02-22 03:00:41.712 - info: host.ioBroker-Master instance system.adapter.backitup.0 started with pid 27000 2019-02-22 03:00:44.287 - debug: backitup.0 objectDB connected 2019-02-22 03:00:44.337 - debug: backitup.0 statesDB connected 2019-02-22 03:00:44.452 - info: backitup.0 starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.14.0 2019-02-22 03:00:44.665 - info: backitup.0 [total] backup was activated at 03:00 every 1 day(s) 2019-02-22 03:00:44.712 - debug: backitup.0 [total] 10 00 03 */1 * *Nodejs = 0.8.15
NPM 6.8.0
Backitup 1.1.2 -
Hast du mal den Adapter neu gestartet.
Ich kann diesen Fehler nich rekonstruieren.Hast du nach der Installation einen Upload gemacht?
Die Version 1.1.2 ist inzwischen auch in der latest repro.
Installiere es mal neu aus der repro -
Hast du mal den Adapter neu gestartet.
Ich kann diesen Fehler nich rekonstruieren.Hast du nach der Installation einen Upload gemacht?
Die Version 1.1.2 ist inzwischen auch in der latest repro.
Installiere es mal neu aus der repro -
An der dropbox wurde nix ge
ä
ndert ... F
ü
ge den Token noch einmal ein ... eventuell ist da was schief gelaufen.
Was sagt der Log? -
@simatec hab ich schon gemacht. Musste ich ja nach der neu Installation. Werde es heute Nacht nochmal
ü
ber die Dropbox laufen lassen und poste das Log.
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden


