CRTech

One more thing i found now - this behavior starts when i run HA VM and Unraid API docker together. If i start Unraid API after clean reboot of the server without HA VM - no writes to USB, if i then start HA VM,it also start writing to USB. Then i stop HA VM and leave it stopped,stop UA - no writes but if i start UA next time (with HA VM stopped) writing to USB continue... It looks like some network or communication settings persist in Unraid and makes this problem, not UA alone..

I dont know what you mean exactly, i am not completely familiar with docker and containers. I only configured this container via edit option in unraid, nothing special, app/config path point to /mnt/user/appdata/Unraid-API - default setting. after few days,when i looked on stats i saw this big amount of writes(something arround 280K) then i started to trace where it comes from.. i also tried to uninstall it, delete everything from /mnt/user/appdata/Unraid-API and install one more time, restarted vm manager,docker,whole server - but no luck..

Cores percentage is normal,nothing suspicious - is probably not the issue you posted..

Hi, in Unraid API log is only this,i dont know if it means something but it shows when i stop this plugin, last message when is running is : Connected to mqtt broker > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js WARN mode option is deprecated. You can safely remove it from nuxt.config READY Server listening on http://0.0.0.0:80 Connected to mqtt broker Connected to mqtt broker npm ERR! path /app npm ERR! command failed npm ERR! signal SIGTERM npm ERR! command sh -c cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-09-11T10_42_35_003Z-debug.log in this file is : 0 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ] 1 info using [email protected] 2 info using [email protected] 3 timing config:load:defaults Completed in 2ms 4 timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 1ms 5 timing config:load:builtin Completed in 1ms 6 timing config:load:cli Completed in 2ms 7 timing config:load:env Completed in 1ms 8 timing config:load:file:/app/.npmrc Completed in 0ms 9 timing config:load:project Completed in 1ms 10 timing config:load:file:/root/.npmrc Completed in 0ms 11 timing config:load:user Completed in 0ms 12 timing config:load:file:/usr/local/etc/npmrc Completed in 0ms 13 timing config:load:global Completed in 0ms 14 timing config:load:cafile Completed in 0ms 15 timing config:load:validate Completed in 0ms 16 timing config:load:setUserAgent Completed in 0ms 17 timing config:load:setEnvs Completed in 1ms 18 timing config:load Completed in 9ms 19 verbose npm-session 96251fc38a486791 20 timing npm:load Completed in 19ms 21 timing command:run-script Completed in 111880ms 22 timing command:start Completed in 111883ms 23 verbose stack Error: command failed 23 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js :64:27) 23 verbose stack at ChildProcess.emit (node:events:378:20) 23 verbose stack at maybeClose (node:internal/child_process:1067:16) 23 verbose stack at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) 24 verbose pkgid [email protected] 25 verbose cwd /app 26 verbose Linux 5.10.28-Unraid 27 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" 28 verbose node v15.8.0 29 verbose npm v7.5.1 30 error path /app 31 error command failed thats all,syslog is clean..

Anyone with the same problem? what is the cause of this behavior? how i can stop it and use this plugin normaly?

Hi, first,big thanks for this plugin, i use it with HA. I configured everything,everything is working but i have one big problem. If i start docker container with this plugin, i get excessive writes on USB drive. I traced it and found that last updated file is /boot/config/domains.cfg . The content of this file is not changing, with other dockers i dont have this problems. i get maybe 10000 writes/hour, this can destroy boot usb disk in short period of time. For now, i stopped it..