mcm1957
commented
2 weeks ago Thanks for the detailled problem description.
But this repository is targetted to request new adapters.
I suggest a) to open atopic at forum (https://forum.iobroker.net) to discuss with other users end to check whther some system setup could cause this problem b) to open a Issue at the mystrom adapter repository (https://github.com/TA2k/ioBroker.mystrom)
Thanks. mcm1957
Hello all I’m running a ioBroker in a Docker environment on a small Ubuntu system. My problem is, that ioBroker (within 1-2 days) gets extremely slow (web access response times of over 1' become the norm). Only remedial action is then to stop and restart ioBroker manually (as after a certain time no reaction over the web was given at all. The diagnosis of ioBroker is "unremarkable". Only thing strange in my eyes is the process "iobroker.js-con", whose CPU "consumption" increases continuously after a restart and after a certain time on average (not peak) hijacks around 100% CPU performance for this single process. Without a running myStrom instance, the CPU share of “ iobroker.js-con” remains around 30% on average (between approx. 10% and with peaks of approx. 100%). With the myStrom adapter turned on, this value climbs continuously until "nothing works". Attempts to stop the instance or display the status of ioBroker may fail with various error messages but NOT always. It seems to be a timeout question Below the errors (if I get them; sorry, I could not pack everything between code-tags...):
Connection is closed. Uncaught Rejection: Error: Objects DB is not allowed to start in the current Multihost environment at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:493:23) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Unable to subscribe to evicted Keyspace events from Redis Server: Connection is closed. Unable to subscribe to meta namespace "meta." changes: Connection is closed. Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! root@iobroker:/opt/iobroker# iobroker stop mystrom No connection to databases possible ... /opt/iobroker/node_modules/standard-as-callback/built/index.js:6throw e; ^Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:632:26) at Socket.emit (node:events:517:28) at TCP.<anonymous> (node:net:350:12)Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Node.js v18.19.1It took me a while to find the suspect in the MyStrom adapter. I can stop it (or kill it); then restart it; afterwards the system runs smoothly again for a while and the CPU "consumption" stays within normal range first. As long as the system is still responding, I can restart the instance via the GUI. If not, only killing / restarting the io.mystrom.0 process helps. With this "half-knowledge" I built a simple Blockly, which stops and restarts this instance every night. This works and keeps ioBroker happy. But that's not supposed to be the definitive solution... In total I have 10 MyStrom smartswitches and 4 MyStrom buttons installed. I have already massively reduced the refresh times (switches every 3' and buttons only every 5' down from the default). What additional information do you need to be able to help me? Below is the "DIAG" information: Details
Summary
Summary: