johntdyer Posted July 23, 2023 Share Posted July 23, 2023 (edited) I keep getting 503 errors from this app, unsure why... is there any way to increase logging level ? text error warn system array login WARN mode option is deprecated. You can safely remove it from nuxt.config WARN No .env file found in /app. > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js READY Server listening on http://0.0.0.0:80 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 KEYSTOREAGE config KEYSTOREAGE Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Temporarily Unavailable</h1></center> <hr><center>nginx</center> </body> </html> Get Dashboard Details for ip: 192.168.100.13 Failed with status code: undefined Request failed with status code 503 Get VM Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Docker Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Get Main Details for ip: 192.168.100.13 Failed Request failed with status code 503 Edited July 23, 2023 by johntdyer Quote Link to comment
BoKKeR Posted July 23, 2023 Author Share Posted July 23, 2023 (edited) No idea, have you tried restarting your OS/container, authenticating again using the web-ui ? PS, the USB devices are fixed now Edited July 24, 2023 by BoKKeR Quote Link to comment
valiente Posted July 24, 2023 Share Posted July 24, 2023 Good day, this seems to work great. One thing I noticed today, one of the entity names coming through to MQTT is extremely long: brute_VM_home_assistant_USB_nbsp    _ <input_type="number"_size="5"_maxlength="5"_id="usbboot0"_class="narrow_bootorder"___style="width__50px;"_name="usbboot[1a86_7523]"___title="boot_order"__value=""_> qinheng_electronics_ch340_serial_converter turned off I am running a Home Assistant VM, which has a USB Serial Adapter passed through. Seems like every time this serial USB has a reading, I get the MQTT entry of the device turning ON and OFF. Quote Link to comment
BoKKeR Posted July 24, 2023 Author Share Posted July 24, 2023 (edited) the usb name should be fixed, I pushed it yesterday, have you pulled since? I will have to look into the ON/OFF loop Edited July 24, 2023 by BoKKeR Quote Link to comment
valiente Posted July 28, 2023 Share Posted July 28, 2023 (edited) I just updated and still seeing my HA logs spiking: Logger: homeassistant Source: helpers/entity_platform.py:750 First occurred: 12:51:59 (781 occurrences) Last logged: 13:05:25 Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 504, in async_add_entities await asyncio.gather(*tasks) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 750, in _async_add_entity raise HomeAssistantError(f"Invalid entity ID: {entity.entity_id}") homeassistant.exceptions.HomeAssistantError: Invalid entity ID: binary_sensor.brute_vm_home_assistant_usb_nbsp_nbsp_nbsp_nbsp_nbsp_nbsp_nbsp_input_type_checkbox_name_usbopt_0463_ffff_id_usbopt0_value_0463_ffff_nbsp_nbsp_nbsp_nbsp_nbsp_input_type_number_size_5_maxlength_5_id_usbboot0_class_narrow_bootorder_style_width_ Logger: homeassistant.components.binary_sensor Source: helpers/entity_platform.py:750 Integration: Binary Sensor (documentation, issues) First occurred: 12:51:59 (461 occurrences) Last logged: 13:07:22 Error adding entities for domain binary_sensor with platform mqtt Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 504, in async_add_entities await asyncio.gather(*tasks) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 750, in _async_add_entity raise HomeAssistantError(f"Invalid entity ID: {entity.entity_id}") homeassistant.exceptions.HomeAssistantError: Invalid entity ID: binary_sensor.brute_vm_home_assistant_usb_nbsp_nbsp_nbsp_nbsp_nbsp_nbsp_nbsp_input_type_checkbox_name_usbopt_0463_ffff_id_usbopt0_value_0463_ffff_nbsp_nbsp_nbsp_nbsp_nbsp_input_type_number_size_5_maxlength_5_id_usbboot0_class_narrow_bootorder_style_width_ 781 entries in 15 minutes... Edited July 28, 2023 by valiente Quote Link to comment
retsamel Posted July 28, 2023 Share Posted July 28, 2023 My logs are flooded by this: Quote Link to comment
BoKKeR Posted July 31, 2023 Author Share Posted July 31, 2023 (edited) @retsamel and @johntdyer, could you pull the latest 6.12, I have added the option to write the html files to config/html_output, as long you use the environment variable: WRITE_HTML_OUTPUT=true These files are not anonymised they are the copy of the VM page and the Dashboard page as seen in the unraid dashboard. Feel free to send them over in a PM if you wish so, I will take a look why the parser has failed. With these files I can possibly debug what is happening Edited July 31, 2023 by BoKKeR Quote Link to comment
song Posted August 1, 2023 Share Posted August 1, 2023 Thank you for maintaining this project. The good news is that you were unable to control the virtual machine before. Now, the information about the virtual machine appears in the plugin, but after connecting to the home assistant, the entity still cannot control the Docker container and virtual machine, I tried to control the container and virtual machine on the web ui page of 'unraid apis', but the results were equally uncontrollable, and even made the web ui page of' unraid 'crash and inaccessible, which took a few minutes to access. I don't know what caused it Quote Link to comment
BoKKeR Posted August 1, 2023 Author Share Posted August 1, 2023 @song I have tested the vm start/stop functionality on a test machine, it works on 6.12.3, Can you tell me more about your system, any logs when this happened? Also could you send the HTML files as stated above? Quote Link to comment
song Posted August 2, 2023 Share Posted August 2, 2023 10 hours ago, BoKKeR said: @song I have tested the vm start/stop functionality on a test machine, it works on 6.12.3, Can you tell me more about your system, any logs when this happened? Also could you send the HTML files as stated above? My system version is 6.12.3. When this issue occurred earlier, I did not record any relevant information because I have not been using it recently. I remember when this issue occurred, there were a large number of warning messages in the system log Quote Link to comment
song Posted August 2, 2023 Share Posted August 2, 2023 This is my system log after running the Docker container on 'unraid API'. I tried to open a container, but unfortunately it directly crashed the 'unraid' webui page. I had to force 'unraid API' to be closed to restore it to normal System log information Aug 2 11:34:42 song kernel: docker0: port 4(vethb6da9cc) entered blocking state Aug 2 11:34:42 song kernel: docker0: port 4(vethb6da9cc) entered disabled state Aug 2 11:34:42 song kernel: device vethb6da9cc entered promiscuous mode Aug 2 11:34:44 song kernel: eth0: renamed from veth05a0186 Aug 2 11:34:44 song kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb6da9cc: link becomes ready Aug 2 11:34:44 song kernel: docker0: port 4(vethb6da9cc) entered blocking state Aug 2 11:34:44 song kernel: docker0: port 4(vethb6da9cc) entered forwarding state Aug 2 11:34:48 song webGUI: Successful login user root from 172.17.0.5 Aug 2 11:34:57 song nginx: 2023/08/02 11:34:57 [error] 6871#6871: *539406 open() "/usr/local/emhttp/plugins/dynamix.vm.manager/templates/images/DS" failed (2: No such file or directory) while sending to client, client: 172.17.0.5, server: , request: "GET /plugins/dynamix.vm.manager/templates/images/DS HTTP/1.1", host: "192.168.50.254" Aug 2 11:35:27 song php-fpm[4970]: [WARNING] [pool www] server reached max_children setting (50), consider raising it Aug 2 11:38:22 song kernel: veth05a0186: renamed from eth0 Aug 2 11:38:22 song kernel: docker0: port 4(vethb6da9cc) entered disabled state Aug 2 11:38:22 song kernel: docker0: port 4(vethb6da9cc) entered disabled state Aug 2 11:38:22 song kernel: device vethb6da9cc left promiscuous mode Aug 2 11:38:22 song kernel: docker0: port 4(vethb6da9cc) entered disabled state I am unable to obtain the log information of 'unraid API' because opening the container while it is running will cause the webui of 'unraid' to become unresponsive. I must stop 'unraid API' to restore it to normal. However, after stopping the operation, the log information of 'unraid API' will be lost and the log from the last startup will not be displayed. I can only provide you with the system log of 'unraid' Quote Link to comment
BoKKeR Posted August 2, 2023 Author Share Posted August 2, 2023 Do you have the chance to run this command while the container is running: docker logs --timestamps `docker ps -aqf "name=Unraid-API-RE"` >> unraid-api-re.txt And attach the unraid-api-re.txt file. In case the container freezes the UI you can also use this command to kill it docker stop `docker ps -aqf "name=Unraid-API-RE"` Quote Link to comment
neighboring-ferryman2976 Posted August 13, 2023 Share Posted August 13, 2023 (edited) Hey all, Im using latest Unraid and wanted to install latest 6.12 version of UnraidAPI-RE the continer is not starting and i keep getting these. updated: The fix for me is change appdata folder from previous installation i just renamed it asa unraidapi2 BTW: No grouping and No device specs in mqqt WARN mode option is deprecated. You can safely remove it from nuxt.config WARN No .env file found in /app. /app/utils/Unraid.ts:275 console.log(e.response.data) ^ TypeError: Cannot read properties of undefined (reading 'data') at /app/utils/Unraid.ts:275:30 at processTicksAndRejections (node:internal/process/task_queues:96:5) at async /app/utils/Unraid.ts:225:6 npm notice npm notice New major version of npm available! 8.19.4 -> 9.8.1 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.8.1> npm notice Run `npm install -g [email protected]` to update! npm notice WARN mode option is deprecated. You can safely remove it from nuxt.config WARN No .env file found in /app. /app/utils/Unraid.ts:275 console.log(e.response.data) ^ TypeError: Cannot read properties of undefined (reading 'data') at /app/utils/Unraid.ts:275:30 at processTicksAndRejections (node:internal/process/task_queues:96:5) at async /app/utils/Unraid.ts:225:6 WARN mode option is deprecated. You can safely remove it from nuxt.config WARN No .env file found in /app. /app/utils/Unraid.ts:275 console.log(e.response.data) ^ TypeError: Cannot read properties of undefined (reading 'data') at /app/utils/Unraid.ts:275:30 at processTicksAndRejections (node:internal/process/task_queues:96:5) at async /app/utils/Unraid.ts:225:6 WARN mode option is deprecated. You can safely remove it from nuxt.config WARN No .env file found in /app. /app/utils/Unraid.ts:275 console.log(e.response.data) ^ TypeError: Cannot read properties of undefined (reading 'data') at /app/utils/Unraid.ts:275:30 at processTicksAndRejections (node:internal/process/task_queues:96:5) at async /app/utils/Unraid.ts:225:6 > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js Connected to mqtt broker > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js Connected to mqtt broker > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js READY Server listening on http://0.0.0.0:80 Connected to mqtt broker > [email protected] start > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js READY Server listening on http://0.0.0.0:80 Connected to mqtt broker ** Press ANY KEY to close this window ** Edited August 13, 2023 by neighboring-ferryman2976 Quote Link to comment
Algiarept Posted August 13, 2023 Share Posted August 13, 2023 Hello there, after a long hiatus, I´ve tried this fork. However, it just seems to me to justcrash after a few seconds. Via Dozzle i´ve extracted the following logs stdout 13.08.2023 16:40:26 > [email protected] start stdout 13.08.2023 16:40:26 > cross-env NUXT_HOST=0.0.0.0 NODE_ENV=production node server/index.js stdout 13.08.2023 16:40:26 stderr 13.08.2023 16:40:26 stderr 13.08.2023 16:40:26 WARN mode option is deprecated. You can safely remove it from nuxt.config stderr 13.08.2023 16:40:26 stderr 13.08.2023 16:40:26 stderr 13.08.2023 16:40:26 WARN No .env file found in /app. stderr 13.08.2023 16:40:26 stdout 13.08.2023 16:40:27 Connected to mqtt broker stdout 13.08.2023 16:40:27 stdout 13.08.2023 16:40:27 READY Server listening on http://0.0.0.0:80 stdout 13.08.2023 16:40:27 stderr 13.08.2023 16:40:33 /app/utils/Unraid.ts:272 stderr 13.08.2023 16:40:33 console.log(e.response.data) stderr 13.08.2023 16:40:33 ^ stderr 13.08.2023 16:40:33 stderr 13.08.2023 16:40:33 TypeError: Cannot read properties of undefined (reading 'data') stderr 13.08.2023 16:40:33 at /app/utils/Unraid.ts:272:30 stderr 13.08.2023 16:40:33 at processTicksAndRejections (node:internal/process/task_queues:96:5) stderr 13.08.2023 16:40:33 at async /app/utils/Unraid.ts:233:6 stderr 13.08.2023 16:40:33 npm notice stderr 13.08.2023 16:40:33 npm notice New major version of npm available! 8.19.4 -> 9.8.1 stderr 13.08.2023 16:40:33 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.8.1> stderr 13.08.2023 16:40:33 npm notice Run `npm install -g [email protected]` to update! stderr 13.08.2023 16:40:33 npm notice Any idea what I am overseeing? I´ve doublechecked the MQTT servers credentials. Ideas ? Quote Link to comment
BoKKeR Posted August 13, 2023 Author Share Posted August 13, 2023 On 7/31/2023 at 2:07 PM, BoKKeR said: @retsamel and @johntdyer, could you pull the latest 6.12, I have added the option to write the html files to config/html_output, as long you use the environment variable: WRITE_HTML_OUTPUT=true These files are not anonymised they are the copy of the VM page and the Dashboard page as seen in the unraid dashboard. Feel free to send them over in a PM if you wish so, I will take a look why the parser has failed. With these files I can possibly debug what is happening @Algiarept can you pull the latest and do as said above? Quote Link to comment
neighboring-ferryman2976 Posted August 13, 2023 Share Posted August 13, 2023 1 hour ago, BoKKeR said: @Algiarept can you pull the latest and do as said above? Hey bro, Do you have any idea why the mqtt is not grouping and no data about free and used space etc? Quote Link to comment
BoKKeR Posted August 13, 2023 Author Share Posted August 13, 2023 (edited) 3 hours ago, neighboring-ferryman2976 said: Hey bro, Do you have any idea why the mqtt is not grouping and no data about free and used space etc? Do you get the free space data in the unraid-api dashboard? I will have to look into mqtt grouping. Edited August 13, 2023 by BoKKeR Quote Link to comment
Algiarept Posted August 14, 2023 Share Posted August 14, 2023 13 hours ago, BoKKeR said: @Algiarept can you pull the latest and do as said above? Yes, so this fixed it and now the MQTT entities show up in Home Assistant. The container stays online and works just fine. This is brilliant ! Question is: If this is an issue for multiple users, can we implement this fix in the template for future users? Quote Link to comment
BoKKeR Posted August 14, 2023 Author Share Posted August 14, 2023 1 hour ago, Algiarept said: Yes, so this fixed it and now the MQTT entities show up in Home Assistant. The container stays online and works just fine. This is brilliant ! Question is: If this is an issue for multiple users, can we implement this fix in the template for future users? happy it works, you should remove the env variable. What fixed the container for you was pulling the latest version. Quote Link to comment
petersem Posted August 15, 2023 Share Posted August 15, 2023 Is this essentially screen scraping the data from the unraid dashboard pages? Quote Link to comment
BoKKeR Posted August 15, 2023 Author Share Posted August 15, 2023 50 minutes ago, petersem said: Is this essentially screen scraping the data from the unraid dashboard pages? Yes, just how the original repo worked Quote Link to comment
johntdyer Posted August 15, 2023 Share Posted August 15, 2023 I am constantly getting this in the logs, ``` Get VM Details for ip: https://unraid.xxxx.xxxxx Failed Request failed with status code 500 Get VM Details for ip: https://unraid.xxxxx.xxxxx Failed Request failed with status code 500 ``` I dont run VM's in unraid so this is as expected... How do I disable this check ? Quote Link to comment
johntdyer Posted August 15, 2023 Share Posted August 15, 2023 On 8/14/2023 at 12:56 AM, Algiarept said: Yes, so this fixed it and now the MQTT entities show up in Home Assistant. The container stays online and works just fine. This is brilliant ! Question is: If this is an issue for multiple users, can we implement this fix in the template for future users? How did you get past this? I am running latest and I see the space usage in the dashboard but no sensors are created in HASS.... Unsure how to debug it Quote Link to comment
johntdyer Posted August 15, 2023 Share Posted August 15, 2023 18 minutes ago, johntdyer said: How did you get past this? I am running latest and I see the space usage in the dashboard but no sensors are created in HASS.... Unsure how to debug it oh, they are attributes under a binary_sensor rather then a sensor... IMHO thats an odd place for them but at least tehy are there Thanks Quote Link to comment
BoKKeR Posted August 15, 2023 Author Share Posted August 15, 2023 2 hours ago, johntdyer said: I am constantly getting this in the logs, ``` Get VM Details for ip: https://unraid.xxxx.xxxxx Failed Request failed with status code 500 Get VM Details for ip: https://unraid.xxxxx.xxxxx Failed Request failed with status code 500 ``` I dont run VM's in unraid so this is as expected... How do I disable this check ? do you mean that your VM feature is disabled in unraid settings ? Or that you don’t have any VM 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.