Monatsrückblick Januar/Februar 2026 ist online!

[deta]

Hallo,

nach update auf den neuen JS-Controller Version heute.

Habe ich im Backitup Adapter Fehler und wird nicht mehr grün.

! host.raspi 2019-01-06 12:24:29.612 info Restart adapter system.adapter.backitup.0 because enabled
! host.raspi 2019-01-06 12:24:29.611 error instance system.adapter.backitup.0 terminated with code 0 (OK)
! host.raspi 2019-01-06 12:24:29.611 error Caught by controller[0]: path: '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh' }
! host.raspi 2019-01-06 12:24:29.611 error Caught by controller[0]: syscall: 'unlink',
! host.raspi 2019-01-06 12:24:29.611 error Caught by controller[0]: code: 'ENOENT',
! host.raspi 2019-01-06 12:24:29.611 error Caught by controller[0]: errno: -2,
! host.raspi 2019-01-06 12:24:29.611 error Caught by controller[0]: at tryOnImmediate (timers.js:768:5)
! host.raspi 2019-01-06 12:24:29.611 error Caught by controller[0]: at runCallback (timers.js:814:20)
! host.raspi 2019-01-06 12:24:29.611 error Caught by controller[0]: at Immediate.createInstancesObjects [as onImmediate] (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:830:13)
! host.raspi 2019-01-06 12:24:29.610 error Caught by controller[0]: at createInstancesObjects (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:869:54)
! host.raspi 2019-01-06 12:24:29.610 error Caught by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5290:18)
! host.raspi 2019-01-06 12:24:29.610 error Caught by controller[0]: at Adapter.emit (events.js:208:7)
! host.raspi 2019-01-06 12:24:29.610 error Caught by controller[0]: at emitNone (events.js:106:13)
! host.raspi 2019-01-06 12:24:29.610 error Caught by controller[0]: at Adapter.main (/opt/iobroker/node_modules/iobroker.backitup/main.js:555:5)
! host.raspi 2019-01-06 12:24:29.610 error Caught by controller[0]: at createBashScripts (/opt/iobroker/node_modules/iobroker.backitup/main.js:489:16)
! host.raspi 2019-01-06 12:24:29.609 error Caught by controller[0]: at Object.fs.unlinkSync (fs.js:1061:18)
! host.raspi 2019-01-06 12:24:29.609 error Caught by controller[0]: { Error: ENOENT: no such file or directory, unlink '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh'
! backitup.0 2019-01-06 12:24:29.067 error Error: ENOENT: no such file or directory, unlink '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh' at Object.fs.unlinkSync (fs.js:1061:18) at createBashScripts (/opt/iobroker/node
! backitup.0 2019-01-06 12:24:29.067 error uncaught exception: ENOENT: no such file or directory, unlink '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh'

cu Deta

[dirkhe]

Die Lösung habe ich eben an ein vorhandes Issue gepostet:

https://github.com/simatec/ioBroker.bac … -451734335

Ändere mal in der main.js folgendes (Zeile 489ff)

fs.existsSync(__dirname + '/lib/stopIOB.sh') && fs.unlinkSync(__dirname + '/lib/stopIOB.sh'); fs.existsSync(__dirname + '/lib/startIOB.sh') && fs.unlinkSync(__dirname + '/lib/startIOB.sh'); fs.existsSync(__dirname + '/lib/start_b_IOB.sh') && fs.unlinkSync(__dirname + '/lib/start_b_IOB.sh'); fs.existsSync(__dirname + '/lib/stop_r_IOB.sh') && fs.unlinkSync(__dirname + '/lib/stop_r_IOB.sh'); fs.existsSync(__dirname + '/lib/.update') && fs.unlinkSync(__dirname + '/lib/.update');

[deta]

Update vorhanden auf Git.. Damit gehts 1.0.3 :-)

cu Deta