zigbee shepherd.db Zugriffsproblem unter Windows

klassisch

Systemdata	Bitte Ausfüllen
Hardwaresystem:	Win 10, i5
Arbeitsspeicher:	8GB
Festplattenart:	SSD 166GB, davon 108GB frei
Betriebssystem:	Windows 10
Node-Version:	10.17.0
Nodejs-Version:	10.17.0
NPM-Version:	6.11.3
Installationsart:	Win Installer von @Stabilostick und manuell auf is-controller 3.2.16
Image genutzt:	Installer + manuelles update, workaround @AlCalzone
Win Installer 2	Link

|Zigbee-Adapter-Version:| 1.4.4 |

Hallo,

Habe heute morgen bemerkt, daß ein Sensor, der alle 10 min updatet, eine AussetzerPeriode hatte. Andere Sensiren in diesem Zeitraum auch.
Das log berichtet von einen Zugriffsproblem auf die shepherd.db
Im Wesentlichen

error: zigbee.1 (4920) uncaught exception: EPERM: operation not permitted, rename 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db.tmp' -> 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db'

kopmlettes Log

2021-05-14 06:09:11.047 - error: zigbee.1 (4920) uncaught exception: EPERM: operation not permitted, rename 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db.tmp' -> 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db'
2021-05-14 06:09:11.052 - error: zigbee.1 (4920) Error: EPERM: operation not permitted, rename 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db.tmp' -> 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db'
at Object.renameSync (fs.js:598:3)
at Database.write (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\database.js:67:22)
at Database.update (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\database.js:40:14)
at Device.save (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\model\device.js:216:35)
at Controller.databaseSave (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\controller.js:250:20)
at Timeout.databaseSaveTimer.setInterval [as _onTimeout] (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\controller.js:152:61)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
2021-05-14 06:09:11.052 - error: zigbee.1 (4920) Exception-Code: EPERM: EPERM: operation not permitted, rename 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db.tmp' -> 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db'
2021-05-14 06:09:11.062 - info: zigbee.1 (4920) cleaned everything up...
2021-05-14 06:09:11.063 - info: zigbee.1 (4920) Zigbee: disabling joining new devices.
2021-05-14 06:09:11.578 - info: zigbee.1 (4920) terminating
2021-05-14 06:09:11.585 - warn: zigbee.1 (4920) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-05-14 06:09:12.257 - error: host.DESKTOP-0UPK22M(ioBrMain2) instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-05-14 06:09:12.258 - info: host.DESKTOP-0UPK22M(ioBrMain2) Restart adapter system.adapter.zigbee.1 because enabled
2021-05-14 06:09:42.291 - info: host.DESKTOP-0UPK22M(ioBrMain2) instance system.adapter.zigbee.1 started with pid 1020
2021-05-14 06:09:54.727 - info: zigbee.1 (1020) starting. Version 1.4.4 in C:/Program Files/iobroker/ioBrMain026/node_modules/iobroker.zigbee, node: v10.17.0, js-controller: 3.2.16
2021-05-14 06:09:55.439 - info: zigbee.1 (1020) Starting Zigbee npm ...
2021-05-14 06:09:56.651 - info: zigbee.1 (1020) Installed Version: iobroker.zigbee@1.4.4
2021-05-14 06:09:58.095 - info: zigbee.1 (1020) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210218}}
2021-05-14 06:09:58.108 - info: zigbee.1 (1020) Unable to disable LED, unsupported function.
2021-05-14 06:09:58.108 - info: zigbee.1 (1020) --> transmitPower : normal
2021-05-14 06:09:58.120 - info: zigbee.1 (1020) Currently 47 devices are joined:

Ich vermute mal ein Problem mit Zugriffsrechten.

Ich habe solche Zugriffsmeldungen schon bei älteren Logfiles gesehen.

Hat jemand einen Hinweis für eine Lösung oder wenigstens einen workaround wie z.B. Detektion des Fehlerzustandes und Neustarten des Adapters.

Beim Log bleiben diese Zugriffsfehler folgenlos, beim Zigbee offensichtlich nicht. Und daran häng meine Lichtsteuerung...

Systemdata	Bitte Ausfüllen
Hardwaresystem:	NUC/Pi3/etc.
Arbeitsspeicher:	1GB
Festplattenart:	SD-Karte/SSD/HDD
Betriebssystem:	Ubuntu/Windows/Mac
Node-Version:	10.x.x
Nodejs-Version:	10.x.x
NPM-Version:	6.x.x
Installationsart:	Skript/Manuell
Image genutzt:	Ja/Nein
Ort/Name der Imagedatei:	Link	Systemdata	Bitte Ausfüllen
--	--
Hardwaresystem:	Win 10, i5
Arbeitsspeicher:	8GB
Festplattenart:	SSD 166GB, davon 108GB frei
Betriebssystem:	Windows 10
Node-Version:	10.17.0
Nodejs-Version:	10.17.0
NPM-Version:	6.11.3
Installationsart:	Win Installer von @Stabilostick und manuell auf is-controller 3.2.16
Image genutzt:	Installer + manuelles update, workaround @AlCalzone
Win Installer 2	Link

|Zigbee-Adapter-Version:| 1.4.4 |

Hallo,

Habe heute morgen bemerkt, daß ein Sensor, der alle 10 min updatet, eine AussetzerPeriode hatte. Andere Sensiren in diesem Zeitraum auch.
Das log berichtet von einen Zugriffsproblem auf die shepherd.db
Im Wesentlichen

error: zigbee.1 (4920) uncaught exception: EPERM: operation not permitted, rename 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db.tmp' -> 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db'

kopmlettes Log

2021-05-14 06:09:11.047 - error: zigbee.1 (4920) uncaught exception: EPERM: operation not permitted, rename 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db.tmp' -> 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db'
2021-05-14 06:09:11.052 - error: zigbee.1 (4920) Error: EPERM: operation not permitted, rename 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db.tmp' -> 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db'
at Object.renameSync (fs.js:598:3)
at Database.write (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\database.js:67:22)
at Database.update (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\database.js:40:14)
at Device.save (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\model\device.js:216:35)
at Controller.databaseSave (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\controller.js:250:20)
at Timeout.databaseSaveTimer.setInterval [as _onTimeout] (C:\Program Files\iobroker\ioBrMain026\node_modules\zigbee-herdsman\dist\controller\controller.js:152:61)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
2021-05-14 06:09:11.052 - error: zigbee.1 (4920) Exception-Code: EPERM: EPERM: operation not permitted, rename 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db.tmp' -> 'C:\Program Files\iobroker\ioBrMain026\iobroker-data\zigbee_1\shepherd.db'
2021-05-14 06:09:11.062 - info: zigbee.1 (4920) cleaned everything up...
2021-05-14 06:09:11.063 - info: zigbee.1 (4920) Zigbee: disabling joining new devices.
2021-05-14 06:09:11.578 - info: zigbee.1 (4920) terminating
2021-05-14 06:09:11.585 - warn: zigbee.1 (4920) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-05-14 06:09:12.257 - error: host.DESKTOP-0UPK22M(ioBrMain2) instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-05-14 06:09:12.258 - info: host.DESKTOP-0UPK22M(ioBrMain2) Restart adapter system.adapter.zigbee.1 because enabled
2021-05-14 06:09:42.291 - info: host.DESKTOP-0UPK22M(ioBrMain2) instance system.adapter.zigbee.1 started with pid 1020
2021-05-14 06:09:54.727 - info: zigbee.1 (1020) starting. Version 1.4.4 in C:/Program Files/iobroker/ioBrMain026/node_modules/iobroker.zigbee, node: v10.17.0, js-controller: 3.2.16
2021-05-14 06:09:55.439 - info: zigbee.1 (1020) Starting Zigbee npm ...
2021-05-14 06:09:56.651 - info: zigbee.1 (1020) Installed Version: iobroker.zigbee@1.4.4
2021-05-14 06:09:58.095 - info: zigbee.1 (1020) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210218}}
2021-05-14 06:09:58.108 - info: zigbee.1 (1020) Unable to disable LED, unsupported function.
2021-05-14 06:09:58.108 - info: zigbee.1 (1020) --> transmitPower : normal
2021-05-14 06:09:58.120 - info: zigbee.1 (1020) Currently 47 devices are joined:

Ich vermute mal ein Problem mit Zugriffsrechten.

Ich habe solche Zugriffsmeldungen schon bei älteren Logfiles gesehen.

Hat jemand einen Hinweis für eine Lösung oder wenigstens einen workaround wie z.B. Detektion des Fehlerzustandes und Neustarten des Adapters.

Beim Log bleiben diese Zugriffsfehler folgenlos, beim Zigbee offensichtlich nicht. Und daran häng meine Lichtsteuerung...

Community Forum

NEWS

zigbee shepherd.db Zugriffsproblem unter Windows

Support us

581

32.7k

82.4k

1.3m