Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[lalam]

Hallo an alle,

habe gerade massive Probleme. Neuer Rechner, ioBroker neu aufgesetzt mit dem Windows Installer. Natürlich alles vorher gesichert. Es lassen sich die Backups auswählen, Skripte und History-Daten lassen sich problemlos zurücksichern. Nur das ioBroker Backup nicht. Auch andere (ältere Backups nicht. Es erscheint die (Browser-) Meldung: "localhost hat die Verbindung abgelehnt.". Firewall, Defender und der ganze Mist ist deaktiviert, sämtliche Caches gelöscht, diese Intel-Grafikkacke deaktiviert (alle Prozesse abgeschossen die danach riechen)...
Parallel auf meinem Laptop (anderer Rechner) nochmal installiert - das gleiche Phänomen! Bin ratlos. Wenn ihr irgendwas braucht - Log oder so um zu helfen bitte Info ....

host.Fujitsu
2024-05-07 12:35:00.702	info	Restart adapter system.adapter.backitup.0 because enabled
host.Fujitsu
2024-05-07 12:35:00.702	error	instance system.adapter.backitup.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at AdapterClass.<anonymous> (C:\ioBroker\node_modules\iobroker.backitup\main.js:259:34)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at Object.restore (C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:125:9)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at getFile (C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:49:9)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:168:21
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at startDetachedRestore (C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:74:17)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at spawn (node:child_process:761:9)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at ChildProcess.spawn (node:internal/child_process:421:11)
host.Fujitsu
2024-05-07 12:35:00.701	error	Caught by controller[1]: Error: spawn EINVAL
host.Fujitsu
2024-05-07 12:35:00.701	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

[Thomas Braun]

@lalam sagte in Restore mit Backup Adapter nicht möglich - Conn. refused...:

massive Probleme. Neuer Rechner, ioBroker neu aufgesetzt mit dem Windows Installer.

Okay. Alles gesagt... :-)

Wenn ihr irgendwas braucht - Log oder so um zu helfen bitte Info ....

Log sind nie verkehrt. Auch nicht unter Windows.

[lalam]

@thomas-braun ```

host.Fujitsu
2024-05-07 12:35:00.702	info	Restart adapter system.adapter.backitup.0 because enabled
host.Fujitsu
2024-05-07 12:35:00.702	error	instance system.adapter.backitup.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at AdapterClass.<anonymous> (C:\ioBroker\node_modules\iobroker.backitup\main.js:259:34)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at Object.restore (C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:125:9)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at getFile (C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:49:9)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:168:21
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at startDetachedRestore (C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:74:17)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at spawn (node:child_process:761:9)
host.Fujitsu
2024-05-07 12:35:00.702	error	Caught by controller[1]: at ChildProcess.spawn (node:internal/child_process:421:11)
host.Fujitsu
2024-05-07 12:35:00.701	error	Caught by controller[1]: Error: spawn EINVAL
host.Fujitsu
2024-05-07 12:35:00.701	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

[Thomas Braun]

@lalam

Ich werde dir wohl keine Hilfe sein, mit dem exotischen Windows kenn ich mich Null aus. Ein Nerd-System für Freaks. :-D

[lalam]

@thomas-braun Trotzdem Danke

[lalam]

backitup.0
2024-05-07 12:35:00.654	info	terminating

backitup.0
2024-05-07 12:35:00.145	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

backitup.0
2024-05-07 12:35:00.144	info	terminating

backitup.0
2024-05-07 12:35:00.144	info	cleaned everything up...

backitup.0
2024-05-07 12:35:00.125	error	Exception-Code: EINVAL: spawn EINVAL

backitup.0
2024-05-07 12:35:00.125	error	Error: spawn EINVAL at ChildProcess.spawn (node:internal/child_process:421:11) at spawn (node:child_process:761:9) at startDetachedRestore (C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:74:17) at C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:168:21 at getFile (C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:49:9) at Object.restore (C:\ioBroker\node_modules\iobroker.backitup\lib\restore.js:125:9) at AdapterClass.<anonymous> (C:\ioBroker\node_modules\iobroker.backitup\main.js:259:34)

backitup.0
2024-05-07 12:35:00.121	error	unhandled promise rejection: spawn EINVAL

backitup.0
2024-05-07 12:35:00.121	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().