pervin_1 Posted June 3, 2018 Share Posted June 3, 2018 Since the Last Unraid Update to 6.5.2, I am getting this error: "noVNC encountered an error" Script Error Here are the couple screenshots running VM and Krusader: Any ideas why? Thank you in advance!!! 2 Quote Link to comment
wilsonhomelab Posted August 30, 2021 Share Posted August 30, 2021 I know this is an old thread. But I have encountered this exactly same issue and couldn't figure out why. This happened after I had a potentially bad mini sas cable and force me to rebuild disable disk, and (after swapping another cable) also upgraded to a higher capacity parity drive, as well as adding an extra 1TB ssd nvme cache drive (on top of an existing 240GB sata SSD cache drive). All of a sudden, when I used noVNC to connect to any VM or docker GUI, I had this annoying red window of message error "noVNC encountered an error: script error". Here is a diagnostic file. unraid-ryzen-diagnostics-20210830-1222.zip I noticed that under logs folder, libvirt.txt 2021-08-30 02:39:11.351+0000: 11053: info : libvirt version: 6.5.0 2021-08-30 02:39:11.351+0000: 11053: info : hostname: UNRAID-Ryzen 2021-08-30 02:39:11.351+0000: 11053: warning : networkNetworkObjTaint:5292 : Network name='default' uuid=28cda2d7-3c5e-4367-8d0e-b710f66e1910 is tainted: hook-script 2021-08-30 02:39:15.395+0000: 11037: error : virNetSocketReadWire:1826 : End of file while reading data: Input/output error 2021-08-30 02:39:17.377+0000: 11037: error : virNetSocketReadWire:1826 : End of file while reading data: Input/output error 2021-08-30 02:39:20.654+0000: 11037: error : virNetSocketReadWire:1826 : End of file while reading data: Input/output error 2021-08-30 02:46:03.365+0000: 11038: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Windows 10 Lite' uuid=82d34170-e0fd-6590-b65e-1fa1ecd5a2de is tainted: high-privileges 2021-08-30 02:46:03.365+0000: 11038: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Windows 10 Lite' uuid=82d34170-e0fd-6590-b65e-1fa1ecd5a2de is tainted: host-cpu 2021-08-30 02:47:49.286+0000: 19530: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor I think it might be the error related to noVNC?! not sure Any suggestion is appreciated! Quote Link to comment
Brandonb1987 Posted August 11, 2022 Share Posted August 11, 2022 Having the exact same issue today. Went to bed and woke up to no VM accessibility. Tried the latest RC to see if that would fix it. It did not. help! 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.