Jump to content

Tom3

Members
  • Content Count

    58
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Tom3

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I use NVMe as cache drive. It routinely would get to 75C during normal write activity. Added an after-market M.2 heatsink (available from Microcenter and others) to the NVMe M.2 stick. The temps now run normal on it. -- Tom
  2. Tom3

    Kudos - UPS

    Unraid + UPS was fully tested this morning. One hour power outage. After hitting the time-on-battery limit, UNRAID cleanly shutdown automatically. The UPS alarmed after the timer, then shut itself down until the AC power returned. The server BIOS is (intentionally) set to NOT automatically reboot on power restoration. Powered-ON via IPMI, and all came back up with no reported errors. Kudos to Lime - this all worked perfectly. UPS: APC Back-UPS 650 -- Tom
  3. Dynamix System Temp - update seems to have display issue. Previous Dynamix System Temp worked fine, displayed correct values. Updated to 2020.03.31 and now the motherboard temperature displays as infinty symbol (wow, that's really hot). The Processor temperature still displays correctly. Unraid 6.8.3 Attached is a screen clipping of just the bottom right part of the display. -- Tom
  4. I had this issue as well, updating to UNRAID 6.8.x fixed. -- Tom
  5. You probably need to create a bridge object in Docker that references the VLAN. There are 3 different things called bridges in Docker, so this gets confusing. See:
  6. There's an updated version of libffi include in Nerdpack. Many thanks, that fixes the problem ! How does one mark this as SOLVED ? -- Tom
  7. Hopefully this is the correct place to put this issue (per @Squid recommendation). -- Tom
  8. I've installed iftop and iotop using nerdpack. iftop runs fine. Have rebooted since installing iotop, error doesn't change. UNRAID version 6.8.0 Trying to run iotop, yields the following error: root@Tower:~# iotop libffi.so.7: cannot open shared object file: No such file or directory To run an uninstalled copy of iotop, launch iotop.py in the top directory I am unable to find iotop.py: root@Tower:~# find / -name 'iotop.*' /usr/man/man8/iotop.8.gz /usr/doc/iotop-0.6/iotop.SlackBuild root@Tower:~# Libffi.so seems to be .6 rather than .7 root@Tower:~# find / -name 'libffi.so.*' /usr/lib64/libffi.so.6 /usr/lib64/libffi.so.6.0.4 Any advice as to how to fix this? -- Tom
  9. Among many great features: Responsiveness to problems, issues, questions, etc. is the best feature. For what I would like to see in 2020: easier to create & manage custom docker / docker compose templates. -- Tom
  10. Thank you for the advice ! Spin down delay just set to 'Never' on the cache. -- Tom
  11. Last upgraded to 6.8.0 on 12/22/2019. I can edit the settings on installed (stopped) VM Ubuntu 18.04 and 19.04, works correctly. I can install and run VM Ubuntu 19.10 successfully. However trying to edit settings on (stopped) Ubuntu 19.10 causes the Unraid GUI to spin forever (buttons stay greyed out, spinner spins forever). After this, the Ubuntu 19.10 VM will not boot, it is stuck at grub screen with no bootable image found. "Remove VM & DIsks" 19.10 then reinstalling is successful, it starts, stops, runs fine again, until attempting to edit the VM 19.10 configuration, which causes above problem again. Attached are diagnostics from when the 19.10 VM is working correctly (no VM edits attempted). -- Tom tower-diagnostics-20191228-0809.zip
  12. Tom3

    noVNC errors

    Here is the status: I am currently unable to re-create the original issue. However have discovered a problem that perhaps may have triggered it previously. I can start/stop and edit Ubuntu 18.04 , 19.04 VMs with no issues. These were installed under 6.7.2, and kept after the Upgrade to 6.8 Under 6.8 I was successful in installing Ubuntu 19.10 VM, and it runs fine. However, I cannot edit that VM (the VM is stopped when editing). Trying to edit a property (memory, CPU cores) then clicking apply results in: 1. The GUI never returns - it just hangs with the buttons greyed-out. 2. Trying to then start 19.10 results in it being dead - it goes directly into grub2 screen with no valid image found and asking to do a new install from scratch. I repeated these steps several times. 6.7.2 was never successful in installing 19.10 (nor upgrading 19.04 to 19.10 which fails in the middle of the upgrade becoming unbootable the same way), so 6.8.0 is a wonderful improvement there. - Tom
  13. Tom3

    noVNC errors

    @limetech Thanks for all your help looking into this ! I have re-loaded 6.8 and am trying to methodically go through steps to see if there is a specific trigger that leads to the behavior. Last time this all happened after about 24 hours (or perhaps 10 or so VM start/stops). Will report back in a few days. -- Tom
  14. Tom3

    noVNC errors

    The error happens when clicking "VNC Remote" in the drop-down menu after having started the particular VM. (Happens for all VMs). It happens in Windows Edge and Linux Firefox browsers. Resolved when I reverted to 6.7.2 -- Tom
  15. Tom3

    noVNC errors

    Libvirt log from the above problem: 2019-12-17 03:52:50.664+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=10 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 03:54:15.784+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 03:54:48.864+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=11 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 03:54:48.864+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=11 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 04:03:27.375+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:05:34.833+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=12 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 04:05:34.833+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=12 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 04:16:33.072+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:17:08.712+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=13 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 04:17:08.712+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=13 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 04:18:53.269+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:20:13.009+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=14 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 04:20:13.009+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=14 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 04:31:47.002+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:31:57.890+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=15 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 04:31:57.890+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=15 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 04:33:26.044+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:55:23.921+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=16 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 04:55:23.921+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=16 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 04:59:35.632+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 05:00:19.488+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=17 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 05:00:19.488+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=17 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 05:05:25.075+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:37:03.012+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=18 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 14:37:03.012+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=18 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 14:37:47.027+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=19 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 14:37:47.027+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=19 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 14:39:12.190+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=20 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 14:39:12.190+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=20 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 14:40:06.579+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:41:17.254+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:44:05.842+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=21 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 14:44:05.843+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=21 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 14:50:54.226+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:51:05.707+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=22 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 14:51:05.707+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=22 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 14:51:56.053+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:52:00.842+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=23 name='Ubuntu-18.04-Server' uuid=c4b2ea8f-a0f6-f617-ec72-90a13d5f2a75 is tainted: high-privileges 2019-12-17 14:52:00.842+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=23 name='Ubuntu-18.04-Server' uuid=c4b2ea8f-a0f6-f617-ec72-90a13d5f2a75 is tainted: host-cpu 2019-12-17 14:56:20.832+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor