Closed Negalein closed 4 months ago
das dauernde Neustarten des Adapter hat sich selbst behoben. Allerdings geht die CPU noch immer von ca. 15% (Adapter gestoppt) bei laufenden Adapter auf 70-75% hoch.
JS-Controller: 5.0.17 Admin: 6.12.9 Node.js: 18.19.0 NPM: 10.2.3
2023-12-18 10:03:44.080 - [32minfo[39m: host.ioBroker "system.adapter.unifi.0" enabled
2023-12-18 10:03:44.585 - [32minfo[39m: host.ioBroker instance system.adapter.unifi.0 started with pid 128723
2023-12-18 10:06:04.137 - [32minfo[39m: host.ioBroker stopInstance system.adapter.unifi.0 (force=false, process=true)
2023-12-18 10:06:04.165 - [32minfo[39m: host.ioBroker stopInstance system.adapter.unifi.0 send kill signal
2023-12-18 10:06:04.666 - [33mwarn[39m: unifi.0 (128723) redis get unifi.0.default.clients.d0:bf:9c:df:e9:18.is_online, error - Connection is closed.
2023-12-18 10:06:04.670 - [33mwarn[39m: unifi.0 (128723) Could not perform strict object check of state unifi.0.default.clients.d0:bf:9c:df:e9:18.is_online: DB closed
2023-12-18 10:06:04.670 - [33mwarn[39m: unifi.0 (128723) get state error: Connection is closed.
2023-12-18 10:06:04.798 - [31merror[39m: unifi.0 (128723) [updateUnifiData-fetchSites site undefined] error: DB closed, stack: Error: DB closed
at Unifi.setForeignState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:8549:30)
2023-12-18 10:06:04.953 - [32minfo[39m: host.ioBroker instance system.adapter.unifi.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-12-18 10:06:07.389 - [32minfo[39m: host.ioBroker instance system.adapter.unifi.0 started with pid 128797
2023-12-18 10:06:07.947 - [34mdebug[39m: unifi.0 (128797) Redis Objects: Use Redis connection: 0.0.0.0:9001
2023-12-18 10:06:08.015 - [34mdebug[39m: unifi.0 (128797) Objects client ready ... initialize now
2023-12-18 10:06:08.016 - [34mdebug[39m: unifi.0 (128797) Objects create System PubSub Client
2023-12-18 10:06:08.017 - [34mdebug[39m: unifi.0 (128797) Objects create User PubSub Client
2023-12-18 10:06:08.152 - [34mdebug[39m: unifi.0 (128797) Objects client initialize lua scripts
2023-12-18 10:06:08.159 - [34mdebug[39m: unifi.0 (128797) Objects connected to redis: 0.0.0.0:9001
2023-12-18 10:06:08.245 - [34mdebug[39m: unifi.0 (128797) Redis States: Use Redis connection: 0.0.0.0:9000
2023-12-18 10:06:08.306 - [34mdebug[39m: unifi.0 (128797) States create System PubSub Client
2023-12-18 10:06:08.306 - [34mdebug[39m: unifi.0 (128797) States create User PubSub Client
2023-12-18 10:06:08.399 - [34mdebug[39m: unifi.0 (128797) States connected to redis: 0.0.0.0:9000
2023-12-18 10:06:08.472 - [34mdebug[39m: unifi.0 (128797) Plugin sentry Initialize Plugin (enabled=true)
2023-12-18 10:06:08.741 - [32minfo[39m: unifi.0 (128797) starting. Version 0.6.7 in /opt/iobroker/node_modules/iobroker.unifi, node: v18.19.0, js-controller: 5.0.17
2023-12-18 10:06:08.767 - [34mdebug[39m: unifi.0 (128797) Schedule restart: * */4 * * *
2023-12-18 10:06:08.787 - [32minfo[39m: unifi.0 (128797) UniFi adapter is ready
2023-12-18 10:06:08.788 - [34mdebug[39m: unifi.0 (128797) controller = 10.0.1.151:8443
2023-12-18 10:06:08.788 - [34mdebug[39m: unifi.0 (128797) updateInterval = 60
2023-12-18 10:06:08.788 - [34mdebug[39m: unifi.0 (128797) Update started
2023-12-18 10:06:09.767 - [34mdebug[39m: unifi.0 (128797) Login successful
2023-12-18 10:06:09.798 - [34mdebug[39m: unifi.0 (128797) fetchSites: default
2023-12-18 10:06:09.804 - [34mdebug[39m: unifi.0 (128797) Update site: default
2023-12-18 10:06:09.829 - [34mdebug[39m: unifi.0 (128797) fetchSiteSysinfo default: 1
2023-12-18 10:06:09.905 - [34mdebug[39m: unifi.0 (128797) fetchClients default: 42
2023-12-18 10:06:16.599 - [34mdebug[39m: unifi.0 (128797) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2023-12-18 10:06:17.340 - [34mdebug[39m: unifi.0 (128797) fetchDevices default: 18
2023-12-18 10:06:29.221 - [34mdebug[39m: unifi.0 (128797) fetchWlans default: 3
2023-12-18 10:06:29.368 - [34mdebug[39m: unifi.0 (128797) fetchNetworks default: 1
2023-12-18 10:06:29.431 - [34mdebug[39m: unifi.0 (128797) fetchHealth default: 5
2023-12-18 10:06:29.621 - [34mdebug[39m: unifi.0 (128797) fetchVouchers default: 10
2023-12-18 10:06:30.862 - [34mdebug[39m: unifi.0 (128797) fetchAlarms default: 1511
2023-12-18 10:07:34.787 - [32minfo[39m: host.ioBroker "system.adapter.unifi.0" disabled
2023-12-18 10:07:34.787 - [32minfo[39m: host.ioBroker stopInstance system.adapter.unifi.0 (force=false, process=true)
2023-12-18 10:07:35.200 - [32minfo[39m: host.ioBroker stopInstance system.adapter.unifi.0 send kill signal
2023-12-18 10:07:35.641 - [33mwarn[39m: unifi.0 (128797) redis mget of 47 keys, err: Connection is closed.
2023-12-18 10:07:35.656 - [31merror[39m: unifi.0 (128797) uncaught exception: Connection is closed.
2023-12-18 10:07:35.656 - [31merror[39m: unifi.0 (128797) Error: Connection is closed.
2023-12-18 10:07:35.657 - [31merror[39m: unifi.0 (128797) Connection is closed.
2023-12-18 10:07:35.818 - [32minfo[39m: host.ioBroker instance system.adapter.unifi.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)```
Könntest du mal schaun wieviele States du unter unifi.0.default.alarm.* hast? Da gabs ein Issue beim javascript wo 70000 satets existierten ...
Könntest du mal schaun wieviele States du unter unifi.0.default.alarm.* hast?
die Alarms hab ich deaktiviert. CPU geht noch immer auf 60% hoch.
nach längerer Beobachtungszeit hat sich das Problem erledigt. Man darf nicht alles abfragen. Nur auf das Wichtigste konzentrieren.
seit 0.6.7 startet der Adapter immer neu und die CPU schießt in die Höhe.