CodeThief

Wow, thanks for the super-quick reply! I guess this is potentially a one-time problem in reality, as I could just CHMOD everything, move the files to the new share and then I won't need to move them again so it's irrelevant what they're permissioned as... Thanks

Hi all, can anyone help me with a permissions issue I appear to have for Plex-created Optimised versions? I want to move all of my optimised versions of films out of their individual folders and into a different library to enable easier selection when remotely streaming. The problem I have is that it appears that when Plex creates an optimised version that it permissions the "Plex Versions" folder as 755: This all works just fine inside of Plex, but when I'm trying to move the optimised versions via SMB on my Windows PC I don't have permission to the files to modify them as the users group only has Read and Execute permissions The Docker container is configured to use PUID 99 and PGID 100 which I believe is correct, but there doesn't seem to be an option to specify the UMASK for created files. Is there a permanent fix for this? I know I could just CHMOD all of the folders, but the next time a file is written by Plex it'll be wrong again Thanks!

Oh I have that installed already, but just needed to do something quickly with the VM from outside of my network on a machine I don't control; noVNC was the simplest option via a reverse-proxied unraid interface. Thanks for the reply

Hi, I'm trying to copy and paste into a noVNC window on my Ubuntu 21.04 VM, but it doesn't seem to be wired up inside of the VM and paste isn't an option. Is there anything I need to do to get paste working from the noVNC clipboard into the X window on my VM? Thanks!

OK, false alert, I had a look in the system log of the server and it's the Windows licensing management service that's shutting the machine down, not the VM host!

It's just shut down again with no corresponding entry in syslog this time, so must have been a coincidence

Discovered there's a /var/log/libvirt/libvirtd.log and it has this entry for the same time: 2021-09-10 21:36:41.956+0000: 4648: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-09-10 21:36:41.956+0000: 4648: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor Interestingly there's an entry in syslog at exactly the same time for a Docker container starting: Sep 10 21:36:40 Server kernel: eth0: renamed from vethd78ed5c Sep 10 21:36:40 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0fea234: link becomes ready Sep 10 21:36:40 Server kernel: docker0: port 6(veth0fea234) entered blocking state Sep 10 21:36:40 Server kernel: docker0: port 6(veth0fea234) entered forwarding state Sep 10 21:36:41 Server rc.docker: Komga: started succesfully! Sep 10 21:36:41 Server kernel: docker0: port 7(veth28dce0c) entered blocking state Sep 10 21:36:41 Server kernel: docker0: port 7(veth28dce0c) entered disabled state Sep 10 21:36:41 Server kernel: device veth28dce0c entered promiscuous mode Sep 10 21:36:41 Server kernel: docker0: port 7(veth28dce0c) entered blocking state Sep 10 21:36:41 Server kernel: docker0: port 7(veth28dce0c) entered forwarding state Sep 10 21:36:41 Server kernel: docker0: port 7(veth28dce0c) entered disabled state Could be a coincidence?

I have a Server 2022 VM configured which is being shut down after what appears to be an arbitrary length of time. This appears in the logs: 2021-09-10T21:36:41.927876Z qemu-system-x86_64: terminating on signal 15 from pid 4371 (/usr/sbin/libvirtd) 2021-09-10 21:36:42.157+0000: shutting down, reason=shutdown I've had a search and can't find anything obvious relating to this problem. The closest I could find was someone who's VMs were pausing and it was due to a full cache drive. Mine is 500GB and only 25% full. I tried a BTRFS balance for fun and it hasn't made any difference. Any ideas?

Sure, it's Unraid v6.9.2. Diagnostics attached. Thanks server-diagnostics-20210910-1531.zip

So I've kind of worked around this by adding a static DNS record on my router to resolve to the correct internal IP, but I'd really like to fix this properly if anyone knows how to force it to update the record on unraid.net

Hi, I recently switched routers and am now using a different IP address range (192.168.1.0/24 --> 192.168.88.0/24). I've updated the IP on my Unraid server and that's fine, but I can't get it to update the guid.unraid.net DNS record for HTTPS access. The update DNS button under the Management Access settings page says there's nothing to update, but that's not correct. I've checked the DNS cache on my router and it looks like the unraid record only has a TTL of 1 minute and I've watched it disappear and reappear with the old IP address every time so I know it's not a caching problem (at least inside of my network!). Is there a way to force the update manually from the commandline? Thanks!

This sounds helpful?

Some sort of CPU scheduling perhaps? Have you got the CPU cores pinned?

Sure, but these settings specifically are in the dynamix folder. The others are all obviously named and in the /config folder but these ones weren't obvious so I thought I'd call them out for others in the future. Thanks for your assistance and suggestions!

Fixed it! I created a new Unraid USB stick to compare the contents and found the only obvious thing that was different was that I was missing a "dynamix" folder under /config/plugins. I had a file called "dynamix", but not a folder; something must have gotten corrupted somehow. Anyway, I deleted the file, copied the folder over and everything is working as expected again. So the server image and the notification settings are all stored in the /config/plugins/dynamix folder for anyone who stumbles across this in the future