arifer

Members
  • Posts

    12
  • Joined

  • Last visited

arifer's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. I only have a Home Assistant Virtual Machine running on my server with unRAID v6.9.2 and libvirt v6.5.0. It's been working fine for the most parts. However, after waking up this morning, I found out that the virtual machine disappeared. I checked the webGUI and saw in the Virtual Machines tab a big yellow banner that said "Libvirt Service failed to start". I know that I should have taken a screenshot of the page before proceeding but I forgot to log it down. I turned off and on the virtual machine support in the settings menu but nothing changed. I then checked the logs and it was clean, no error messages whatsoever. The last approach I took was to reboot the whole system. I rebooted it, started up the array, re-enabled VM support in the menu and now it's working fine. Checking the logs, there is an entry in it that is suspiciously foreboding. 2021-10-01 02:21:44.048+0000: 12337: info : libvirt version: 6.5.0 2021-10-01 02:21:44.048+0000: 12337: info : hostname: Babel 2021-10-01 02:21:44.048+0000: 12337: warning : networkNetworkObjTaint:5292 : Network name='default' uuid=a67b7b9b-bef4-488b-b243-c9e5f391a3b1 is tainted: hook-script 2021-10-01 02:21:44.923+0000: 12337: warning : qemuDomainObjTaint:6075 : Domain id=1 name='HomeAssistant' uuid=78b2f542-3fd7-039d-f5a5-7866d93e49d6 is tainted: high-privileges 2021-10-01 02:21:44.923+0000: 12337: warning : qemuDomainObjTaint:6075 : Domain id=1 name='HomeAssistant' uuid=78b2f542-3fd7-039d-f5a5-7866d93e49d6 is tainted: host-cpu 2021-10-01 02:21:45.764+0000: 12321: error : virNetSocketReadWire:1826 : End of file while reading data: Input/output error It raises an EoF error message. The first guess I have is that it might have something to do with the fact that my libvirt.img file is hosted on my cache drive but then I would also expect a similar issue with my docker containers which are also running on the same cache drive, which is not the case! I'm posting this here in hope that someone out there may shed some light on this issue.
  2. After it initialises the issue should sort itself out. I believe I faced some permissions issue in my appdata share so I fixed it through the Docker New Permissions tool and my reboots from then on had no hiccups. Tapatalk を使用して私の XQ-AS72 から送信
  3. I faced this issue once and I managed to get it fixed by turning off docker and VMs in the settings before starting up the array. I suggest you stop the array and try that out to see if it works. Tapatalk を使用して私の XQ-AS72 から送信
  4. Thank you for the hard work. The connection is finally going through and I'm seeing myself online and accessible through the internet now. Actually, it seems as if the my-servers page retrieves the connection information a lot faster than it used to! This is great! I'll mark this thread as closed.
  5. I got back and saw this in the debug logs for `unraid-api` ws:closed 1006 closed automatically, restarting ws:closed 1006 closed automatically, restarting ☁️ RELAY:DISCONNECTED ws:closed 1006 closed automatically, restarting ws:closed 1006 closed automatically, restarting ws:closed 1006 closed automatically, restarting ws:closed 1006 closed automatically, restarting ws:closed 1006 closed automatically, restarting ☁️ RELAY:DISCONNECTED ⌨️ INTERNAL:CONNECTED Error: WebSocket is not open: readyState 0 (CONNECTING) at WebSocket2.send (/usr/local/bin/unraid-api/node_modules/graceful-ws/dist/graceful-ws.js:1649:17) at GracefulWebSocket.send (/usr/local/bin/unraid-api/node_modules/graceful-ws/dist/graceful-ws.js:2458:39) at GracefulWebSocket.<anonymous> (/usr/local/bin/unraid-api/dist/index.js:32254:55) at GracefulWebSocket.emit (events.js:315:20) at GracefulWebSocket.EventEmitter.emit (domain.js:467:12) at WebSocket2.<anonymous> (/usr/local/bin/unraid-api/node_modules/graceful-ws/dist/graceful-ws.js:2479:12) at WebSocket2.onOpen (/usr/local/bin/unraid-api/node_modules/graceful-ws/dist/graceful-ws.js:1109:20) at WebSocket2.emit (events.js:315:20) at WebSocket2.EventEmitter.emit (domain.js:467:12) at WebSocket2.setSocket (/usr/local/bin/unraid-api/node_modules/graceful-ws/dist/graceful-ws.js:1566:14) Not sure if this helps but I hope it shed some light into why the connection keeps failing to sustain.
  6. Actually, it seems that it's starting to fail to connect again. I'm getting a flurry of reconnecting issues in the debug. libvirt: No changes detected. libvirt: No changes detected. ☁️ RELAY:Too Many Requests:RECONNECTING:NOW ☁️ RELAY:Too Many Requests:RECONNECTING:NOW ☁️ RELAY:429:Too Many Requests:RECONNECTING:30_000 ... libvirt: No changes detected. libvirt: No changes detected. ☁️ RELAY:Too Many Requests:RECONNECTING:NOW ☁️ RELAY:Too Many Requests:RECONNECTING:NOW libvirt: No changes detected. ☁️ RELAY:Too Many Requests:RECONNECTING:NOW
  7. I updated to v2021.09.15.1853 last night. I noticed when I was out today that I could not access it from the internet. When I got home, it first raised the error that Graphql was offline so I tried using `unraid-api restart` to get it running since I had encountered this issue before. However, it continued to fail to connect to the mothership no matter how long I wait or how many times I tried. I referenced this post and re-installed the plugin twice but that also did not make a difference. Once all the dry methods had failed, I tried to debug the issue. I ran `unraid-api --debug restart` and lo and behold, connection to the mothership is made and sustained. Right now I'm running that in a tmux session so that it remains online for as long as the server stays online. It also gives me a good log of what's happening just in case something fails.
  8. @iker 's solution worked for me on SWAG. I also had to include the following lines in my configuration.yaml file for the Hassio VM. http: use_x_forwarded_for: true trusted_proxies: - XXX.XXX.XXX.XXX # IP address of my unRAID box If you're facing problems getting the right IP address, try accessing the web app through the site you have set up the CNAME for like homeassistant.domain.host and search your Home Assistant logs under "Configuration >> Logs" for the following entry: where the IP address shown is what you need to insert into the code block above.
  9. @bigbangus You would need to add the following lines to the configuration.yaml file: http: use_x_forwarded_for: true trusted_proxies: - 172.XX.XX.XX # The SWAG docker IP address You can always check for your SWAG docker IP address by checking it in the port mappings column of the Dockers tab.
  10. I can't seem to add any podcasts by URL. The Uncast one in particular. https://feeds.buzzsprout.com/1746902.rss Is there anybody else facing the same issue?
  11. You'd need to add the following to the `location` block. proxy_set_header X-Forwarded-Proto http; proxy_set_header X-Forwarded-Ssl off;
  12. I doubt that this is configurable from the server side since the clients need to have the fonts installed to be able to have it displayed accurately. If you are on Linux, there are many different methods that you can employ to install fonts, graphical and console alike. A quick google search will lead you the right way. If you just want to get it done fast, one mostly distro-agnostic method would be to move the .ttf into `/usr/local/share/fonts/ttf/` and then running `fc-cache -fs` to install the font. If you are on Mac, IIRC you just need to double click on the font and there should be a button to install the font: https://support.apple.com/en-us/HT201749 As for Windows, you should be able to install it by picking the appropriate context after right-clicking the font: https://www.fontspring.com/support/how-do-i-install-fonts-on-my-windows-pc However, if you are in a case where you cannot enforce the fonts to be installed on all the clients you wish to play the media on, you're in bad luck then. There's a request upstream to get something like this added to Plex so maybe you can add a vote to it: https://forums.plex.tv/t/subtitles-settings-font-color-offset-time-position/232538