ArveVM Posted October 6, 2023 Share Posted October 6, 2023 On 10/3/2023 at 9:06 AM, BoKKeR said: Could you confirm that there is no space in the name of the server? Also are you using any custom theme? I would normally not use any space in names,, and I believe it is not even allowed in unraid-server-name,,, but thanks for having me verify, - its not like I haven't done stupid rookie mistakes Quote Also are you using any custom theme? if you are refering to the Theme Engine plugin then NO, that is not installed. I use dark mode and DockerFolder in unraid, get my docker-overview/jump-points in Homepage,, and performance should be logged/visible in HA Quote Link to comment
ArveVM Posted October 6, 2023 Share Posted October 6, 2023 On 10/3/2023 at 8:07 PM, BoKKeR said: I will have to look into proper naming with the new HA release. I am open to suggestions! HA-naming: Since I also integrate my unraid-server with MonitorDocker-integration,, I'd like naming of devices as the integration So entities from monitordocker is called like sensor.monitordocker_adguard_home and the unraid-api one could b DeviceName=unraidAPI Server-level sensors: binary_sensor.unraidapi_server button.unraidapi_server_mover button.unraidapi_server_partitycheck button.unraidapi_server_power_off button.unraidapi_server_reboot switch.unraidapi_server_array Docker; button.unraidapi_docker_adguard_home_restart switch.unraidapi_docker_adguard_home (i have no VM's) So for me the logical choice is to have UnraidAPI (integration) as device name But then how about the advanced guys with mulitple servers?? perhaps a combination of integration-name and server-name just to get the full -full length entity-id's Quote Link to comment
lanky8804 Posted October 6, 2023 Share Posted October 6, 2023 On 10/5/2023 at 7:42 AM, BoKKeR said: Could you tell me more how you detected the memory leak? What was your setup? @lanky8804 did you manage to figure it out? Could you try removing the info config file and starting fresh? there is also an env variable that might show if the scraping is working: WRITE_HTML_OUTPUT=true @BoKKeR Thank you yes, rebooted a few times and then it appeared, thank you. Quote Link to comment
praxidike Posted October 7, 2023 Share Posted October 7, 2023 I'm running version: 6.11.5 with your docker using bokker/unraidapi-re:6.11 I don't see any VMs in Home Assistant and I see this error in logs. Get VM Details for ip: 192.168.1.XXX Failed Cannot read properties of undefined (reading 'children') Quote Link to comment
BoKKeR Posted October 7, 2023 Author Share Posted October 7, 2023 4 hours ago, praxidike said: I'm running version: 6.11.5 with your docker using bokker/unraidapi-re:6.11 I don't see any VMs in Home Assistant and I see this error in logs. Get VM Details for ip: 192.168.1.XXX Failed Cannot read properties of undefined (reading 'children') sorry, I have been mostly focused on 6.12, please update if you are able to. Going forward I will try to support older OS. The problem is that the project needed so much rewrite to get to a good shape. And the work is still not done. To be able to do that in two branches turned out to be much harder than expected. Currently I am focusing on fixing up the codebase in 6.12 Quote Link to comment
ABEIDO Posted October 7, 2023 Share Posted October 7, 2023 (edited) @Booker First checking if im using correct repo. Im using bokker/unraidapi-re:6.12 and i am again having issues after restarting HA that all sensors goes unavailable and i need restart UnraidApi container to get the sensors working again. Wrote here about but no one else seemed to have this issue. This was fixed before new restart/button updat. So im wondering if im using incorrect repo or something? Also a new issue that ive traced back to UnraidAPI. Whenever this docker is running my Unraid log gets spammed but below. Have had this a while but didnt know what was the source. Other people have talked about it (unknown if they were running UnraidAPI) and said that its most likely it isnt more than logspamm, but it would be nice to not have them. Example: Oct 7 14:14:01 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:14:34 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:15:07 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:15:40 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:16:13 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:16:46 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:17:20 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:17:53 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:18:26 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:18:59 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:19:32 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:20:05 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:20:39 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:21:12 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:21:45 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:22:18 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:22:51 SERVER-NAME monitor: Stop running nchan processes Oct 7 14:23:24 SERVER-NAME monitor: Stop running nchan processes Edited October 7, 2023 by ABEIDO Quote Link to comment
GardenSnakes Posted October 11, 2023 Share Posted October 11, 2023 Thanks for this amazing app! It works very nice, I enjoy using the API to get data about my Unraid setup. One little feature request which I would love to see: - An API endpoint where I can supply a URL to, so that the UnraidAPI Docker makes a request to this API endpoint with the Unraid authentication cookie. In my case I would love to read the Intel_HTop data from its API which is available at: `http://<UNRAIDIP>/plugins/gpustat/gpustatusmulti.php?gpus={"00:02.0":{"id":"00:02.0","model":"AlderLake-S GT1","vendor":"intel","guid":"0000:00:02.0","panel":1}}` So in this case I would like to call an API endpoint at the UnraidAPI docker image and add the: `/plugins/gpustat/gpustatusmulti.php?gpus={"00:02.0":{"id":"00:02.0","model":"AlderLake-S GT1","vendor":"intel","guid":"0000:00:02.0","panel":1}}` as parameter in the body for example. Would this be possible to add? If could create a pull request which implements this logic, but I wanted to ask you @BoKKeR first if this is a good idea. I think it's great Quote Link to comment
Foehammer1982 Posted October 12, 2023 Share Posted October 12, 2023 On 10/5/2023 at 2:42 AM, BoKKeR said: Could you tell me more how you detected the memory leak? What was your setup? Mine was easily detectable through log files, looking at unraid-api ballooning in ram and then crashing the docker service, i even observed the behavior first hand once as well. The script fixes it if anyone needs to know id be happy to post it, its very simple. But Electic brain uk theirself even detected it and basically did one of these: ¯\_(ツ)_/¯ Heres his post on it from his original support forum thread: Quote Link to comment
Foehammer1982 Posted October 12, 2023 Share Posted October 12, 2023 The script is just for restarting the container every four hours, it doesn't address the actual memory leak, just to be clear. Quote Link to comment
BoKKeR Posted October 12, 2023 Author Share Posted October 12, 2023 @Foehammer1982 I ran some script to detect potential node leaks and it triggered right away. I am not sure if its false positives, will have to investigate more. The whole polling is done with multiple setTimeout calls so if anything thats my suspect. Also I am questioning the need for multiple server support, now with the MQTT change. Considering that users could just run multiple docker instances for multiple servers and it would possibly solve some of the problems around MQTT naming. The list of issues currently are looking into are: - new home assistant MQTT entity names - server shut down ends with ON state - HA entities go unavailable on HA restart (can be fixed with retain:on but those messages have to be cleaned up) - memory leak - make the image support multiple unraid releases with single docker image - deleted dockers end up on HA (unconfirmed) 1 Quote Link to comment
BoKKeR Posted October 12, 2023 Author Share Posted October 12, 2023 15 hours ago, GardenSnakes said: Thanks for this amazing app! It works very nice, I enjoy using the API to get data about my Unraid setup. One little feature request which I would love to see: - An API endpoint where I can supply a URL to, so that the UnraidAPI Docker makes a request to this API endpoint with the Unraid authentication cookie. In my case I would love to read the Intel_HTop data from its API which is available at: `http://<UNRAIDIP>/plugins/gpustat/gpustatusmulti.php?gpus={"00:02.0":{"id":"00:02.0","model":"AlderLake-S GT1","vendor":"intel","guid":"0000:00:02.0","panel":1}}` So in this case I would like to call an API endpoint at the UnraidAPI docker image and add the: `/plugins/gpustat/gpustatusmulti.php?gpus={"00:02.0":{"id":"00:02.0","model":"AlderLake-S GT1","vendor":"intel","guid":"0000:00:02.0","panel":1}}` as parameter in the body for example. Would this be possible to add? If could create a pull request which implements this logic, but I wanted to ask you @BoKKeR first if this is a good idea. I think it's great Interesting idea but I dont think its as clear cut as you might think. You will have to come up with a common structure that the url would have to supply. Or alternatively add a little script inside of unraid-api where you could transform the data to the desired output. Its quite a lot of work currently for me. As always, contributions are welcome. You can probably find me on discord for discussions Quote Link to comment
mattw Posted October 13, 2023 Share Posted October 13, 2023 Really, other than fixing the memory leak... it works as well as the original. I would really like to see it pass the CPU temperature to MQTT. I am running on 6.11.5. Thanks for taking this on! Quote Link to comment
BoKKeR Posted October 15, 2023 Author Share Posted October 15, 2023 (edited) I have potentially fixed the naming problem. Do try out this branch bokker/unraidapi-re:6.12-naming I have also grouped the VM usb devices under the VM There is also an option to set icons in the MQTT messages for entities. I have not had time to choose any. https://pictogrammers.com/library/mdi/ Edited October 15, 2023 by BoKKeR Quote Link to comment
Blade007 Posted October 17, 2023 Share Posted October 17, 2023 Hi @ All, I've been trying for days to get the integration to work but to no avail. The application itself runs and in the WebUI all Unraid entities and actions are displayed, but nothing is sent via mqtt. In Homeassistant also nothing arrives. What is the reason for this and how can I test it? I have a MQTT explorer running in Hassio. Quote Link to comment
ABEIDO Posted October 18, 2023 Share Posted October 18, 2023 (edited) Updated and couldnt find any issues with the naming I keep it kinda simple and set my entities to: docker on/off = mdi:power docker restart = mdi:restart mover: mdi:folder-arrow-up-down-outline array on/off: mdi:power parity check: mdi:sync-alert reboot: mdi:restart shutdown: mdi:power status: mdi:checkbox-marked-outline Edited October 18, 2023 by ABEIDO Quote Link to comment
BoKKeR Posted October 19, 2023 Author Share Posted October 19, 2023 18 hours ago, ABEIDO said: Updated and couldnt find any issues with the naming I keep it kinda simple and set my entities to: docker on/off = mdi:power docker restart = mdi:restart mover: mdi:folder-arrow-up-down-outline array on/off: mdi:power parity check: mdi:sync-alert reboot: mdi:restart shutdown: mdi:power status: mdi:checkbox-marked-outline Did you update to the naming fork? @Blade007 Are you able to add WRITE_HTML_OUTPUT=true to your env variables, it should log every time the site gets scraped. Additionally you could try to remove the config and start fresh. About the memory leaking @Foehammer1982. I am not saying that its not happening but I cant seem to reproduce it on my server (last 7 days view) Quote Link to comment
Blade007 Posted October 19, 2023 Share Posted October 19, 2023 Quote Are you able to add WRITE_HTML_OUTPUT=true to your env variables, it should log every time the site gets scraped. Additionally you could try to remove the config and start fresh. @BoKKeR thx it´s working now. I had this variabled set to false. I also set the unraid server to hide somehow 🤦♂️ 1 Quote Link to comment
BoKKeR Posted October 19, 2023 Author Share Posted October 19, 2023 Keep the variable false if it works 3 hours ago, Blade007 said: @BoKKeR thx it´s working now. I had this variabled set to false. I also set the unraid server to hide somehow 🤦♂️ 1 Quote Link to comment
apedance Posted October 19, 2023 Share Posted October 19, 2023 Hey there! Thank you for your work. Using Unraid 6.9.2 Somehow the old version recently stopped working. Installed your version. Doesn't work. Ton of log file warnings. Docker image is running and web interface is up. Connection via web interface is not working or sluggish. Only a 1 or 2 sensors are loaded. ErrorWarningSystemArrayLogin > [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 WARN No .env file found in /app. READY Server listening on http://0.0.0.0:80 Failed to retrieve config file, creating new. ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) (repeated 2 times) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:590:3) at Object.readFileSync (node:fs:458:35) at _default (api/getServers.js:35:45) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/@nuxt/server/node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:513:28) at SendStream.error (node_modules/@nuxt/server/node_modules/send/index.js:270:17) at SendStream.onStatError (node_modules/@nuxt/server/node_modules/send/index.js:417:12) at next (node_modules/@nuxt/server/node_modules/send/index.js:731:16) at onstat (node_modules/@nuxt/server/node_modules/send/index.js:720:14) at FSReqCallback.oncomplete (node:fs:202:21) npm notice npm notice New major version of npm available! 8.19.4 -> 10.2.1 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.2.1> npm notice Run `npm install -g [email protected]` to update! npm notice 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/2023-10-19T20_43_39_427Z-debug-0.log > [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 WARN No .env file found in /app. READY Server listening on http://0.0.0.0:80 Quote Link to comment
BoKKeR Posted October 19, 2023 Author Share Posted October 19, 2023 (edited) @apedance 6.9-2 is not supported, update to 6.12 for maximum support Edited October 19, 2023 by BoKKeR Quote Link to comment
ABEIDO Posted October 20, 2023 Share Posted October 20, 2023 (edited) 20 hours ago, BoKKeR said: Did you update to the naming fork? Yes bokker/unraidapi-re:6.12-naming, but to be honest i cannot find where to look for any errors for sure. I remember it there was supposed to be errors in debug log regarding naming. Cannot find any there now. So it seems to be working fine. Example from core.entity_registry file looks ok: "original_name": "docker_bazarr_restart", "unique_id": "unraid_bazarr_restart", That said i rename my entities always according to my own standard thats why i need to look in core.entity_registry file. Example: Edited October 20, 2023 by ABEIDO Quote Link to comment
MVLP Posted November 3, 2023 Share Posted November 3, 2023 Hello I have the Issue what the Container lags my WebUI from Unraid because of the following ErrorLogs Nov 3 08:14:28 Tower nginx: 2023/11/03 08:14:28 [error] 9317#9317: *91615 limiting requests, excess: 20.013 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:28 Tower nginx: 2023/11/03 08:14:28 [error] 9317#9317: *91616 limiting requests, excess: 20.013 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:28 Tower nginx: 2023/11/03 08:14:28 [error] 9317#9317: *91617 limiting requests, excess: 20.013 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:28 Tower nginx: 2023/11/03 08:14:28 [error] 9317#9317: *91618 limiting requests, excess: 20.013 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:28 Tower nginx: 2023/11/03 08:14:28 [error] 9317#9317: *91632 limiting requests, excess: 20.877 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:28 Tower nginx: 2023/11/03 08:14:28 [error] 9317#9317: *91633 limiting requests, excess: 20.877 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:28 Tower nginx: 2023/11/03 08:14:28 [error] 9317#9317: *91638 limiting requests, excess: 20.811 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:28 Tower nginx: 2023/11/03 08:14:28 [error] 9317#9317: *91655 limiting requests, excess: 20.675 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:28 Tower nginx: 2023/11/03 08:14:28 [error] 9317#9317: *91656 limiting requests, excess: 20.675 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:30 Tower nginx: 2023/11/03 08:14:30 [error] 9317#9317: *91694 limiting requests, excess: 20.924 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:30 Tower nginx: 2023/11/03 08:14:30 [error] 9317#9317: *91717 limiting requests, excess: 20.616 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:30 Tower nginx: 2023/11/03 08:14:30 [error] 9317#9317: *91718 limiting requests, excess: 20.616 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:30 Tower nginx: 2023/11/03 08:14:30 [error] 9317#9317: *91719 limiting requests, excess: 20.616 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:30 Tower nginx: 2023/11/03 08:14:30 [error] 9317#9317: *91720 limiting requests, excess: 20.616 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:30 Tower nginx: 2023/11/03 08:14:30 [error] 9317#9317: *91721 limiting requests, excess: 20.616 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Nov 3 08:14:39 Tower nginx: 2023/11/03 08:14:39 [error] 9317#9317: *92015 limiting requests, excess: 20.088 by zone "authlimit", client: 172.17.0.12, server: , request: "GET /login HTTP/1.1", host: "192.168.178.2" Is that an know'n issue or maybe an Hickup? After restarting the Container the Performance was good again. Quote Link to comment
Foehammer1982 Posted November 8, 2023 Share Posted November 8, 2023 On 10/19/2023 at 7:00 AM, BoKKeR said: Did you update to the naming fork? @Blade007 Are you able to add WRITE_HTML_OUTPUT=true to your env variables, it should log every time the site gets scraped. Additionally you could try to remove the config and start fresh. About the memory leaking @Foehammer1982. I am not saying that its not happening but I cant seem to reproduce it on my server (last 7 days view) Hmm, perhaps it's something with unraid that changed with an update as i was on 6.9 back when that was an issue, great to see its no longer an issue though Quote Link to comment
Cyklone Posted November 10, 2023 Share Posted November 10, 2023 On 10/17/2023 at 6:29 AM, Blade007 said: Hi @ All, I've been trying for days to get the integration to work but to no avail. The application itself runs and in the WebUI all Unraid entities and actions are displayed, but nothing is sent via mqtt. In Homeassistant also nothing arrives. What is the reason for this and how can I test it? I have a MQTT explorer running in Hassio. Hi, This is also happening with me. Nothing showing up in HA or in the MQTT Explorer app in Windows. Running frigate in docker, HA in VM and HASS.Agent on several computers. I see all the posts from these, but nothing from Unraid-API-RE. The Unraid-API-RE WebGui works fine and can control dockers/VMS from that without issues. Quote Link to comment
BoKKeR Posted November 10, 2023 Author Share Posted November 10, 2023 1 hour ago, Cyklone said: Hi, This is also happening with me. Nothing showing up in HA or in the MQTT Explorer app in Windows. Running frigate in docker, HA in VM and HASS.Agent on several computers. I see all the posts from these, but nothing from Unraid-API-RE. The Unraid-API-RE WebGui works fine and can control dockers/VMS from that without issues. Are you able to wipe the /config folder and start again? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.