rjorgenson

Thanks! I dug around in the menu on the device but couldn't find an option to enable modbus anywhere, there was an NMC setting that was network based but I decided not to mess with that and just set it up as usbhid-ups and everything worked as before =]

Trying to get this plugin setup to replace the outdated NUT plugin. I used the auto-config and it detected my UPS but the service wont start. When trying to start it manually form the command line it gives a timeout error. Writing NUT configuration... Updating permissions for NUT... Checking if the NUT Runtime Statistics Module should be enabled... Disabling the NUT Runtime Statistics Module... Network UPS Tools - UPS driver controller 2.8.0.1 Network UPS Tools - NUT APC Modbus driver 0.01 (2.8.0.1) _apc_modbus_read_registers: Read of 516:604 failed: Connection timed out (auto) Can't read inventory information from the UPS upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it Driver failed to start (exit status=1) The autoconfig sees the device plugged in over USB and says it's writing the config NUT Scanner is now searching for UPS devices... ##################################################### [nutdev1] driver = "apc_modbus" port = "auto" vendorid = "051D" productid = "0003" product = "Smart-UPS 1500 FW:UPS 08.8 / ID=18" serial = "__REDACTED__" vendor = "American Power Conversion" bus = "005" device = "003" busport = "001" ###NOTMATCHED-YET###bcdDevice = "0106" ##################################################### I'm not sure what could be the issue here, is this config actually written? It looks like it's trying to connect to a busport other than what is detected.

yeah it's all good now, no longer complaining after upgrading.

Glad the issue was found. Am I safe to dismiss this for now until a new version is released? Or will I need to change something about my cert eventually anyways?

Sure thing, here you go. Thanks for the help! mnemos-diagnostics-20221212-1254.zip

This is a wildacard cert provided by letsencrypt. Here is the output of those two commands. root@mnemos:~# openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p' *.rendezvous.agffa.net root@mnemos:~# openssl x509 -noout -ext subjectAltName -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | grep -Eo 'DNS:[a-zA-Z 0-9.*-]*' | sed 's/DNS://g' *.rendezvous.agffa.net agffa.net rendezvous.agffa.net root@mnemos:~#

FCP recently started warning me that But my subject CN appears to be set correct for a wildcard root@mnemos:/boot/config/ssl/certs# openssl x509 -noout -text -in mnemos_unraid_bundle.pem | grep "Subject: CN" Subject: CN = *.rendezvous.agffa.net root@mnemos:/boot/config/ssl/certs# and my local TLD also appears to be correct I am still on unRAID 6.9.2 if that matters.

Any luck with this? It'd be nice if there was a bug thread somewhere we could follow to know when this is resolved.

Had to give it the old hard power cycle =/ It came back up fine and is running a parity check. Nothing in the logs from before the restart either. I'll look into setting up a syslog sever like you suggested in case it ever happens again.

Nope, my ssh connection to the server just hangs. I had an open session running midnight commander that was responsive, but when i tried to run a new shell command it just hung and is still sitting there after a few hours. My only option is to try an ACPI reboot via the power button and hope that is configured properly I guess.

This same thing just happened to me last night. I am not able to SSH into the host or get to the GUI to attempt to troubleshoot/reboot but the VM's are still running and everything else seems okay. I have no idea what to do other than just do a hard reset, which seems like a not so great idea. *edit* - Also I am stubbing my GPU to a VM so my unRAID console is not available, no idea what is in there =/

I have an Asus Prime x370 Pro(latest BIOS, 5603) with a Ryzen 1700X, GTX 1080, and a Samsung 960 Pro NVMe SSD that I am currently running windows on. I am attempting to run unRAID on this system and virtualize my windows system(for gaming) so I can consolidate my computers down a bit. I am also currently acquiring parts to upgrade this host to a Ryzen 3900XT on x570 a bit down the line (or maybe Ryzen 4000, or 5000? who knows). I put unRAID 6.9 beta25 on a thumb drive and am giving this a go to see how well it might or might not work before migrating all my unRAID stuff from my actual server to this new one. So far I am having terrible lag and stuttering on the VM when gaming, though it seems to run pretty much okay for normal desktop stuff(web browser, video playback, etc). Here is how I have my VM setup. Host passthrough on the last 4 CPU cores and their threads(8 total, all isolated in unraid settings) emulatorpin set to the first core and it's thread 8G of memory for initial and max (I initially tried 16G as I have it to spare but read that more can cause issues so I tried with less) i440fx-5.0 OVMF hyper-v off (nvidia card) passing in my game storage drive via /dev/disk/by-id with SATA driver passing through my GTX 1080 with ROM BIOS from techpowerup and hex edited (only GPU in system) bother motherboard and GPU sound cards being passed through bridged networking stubbed (via vfio plugin) NVMe samsung 960 pro (it's in it's own IOMMU group) USB mouse dongle (wireless) USB keyboard (wired) Here is a list of the things I have tried, all with no success. cpu isolation/pinning (with 4 core and their threads[8 total] as well as 3 cores and their threads) emulatorpin setting motherbaord audio only graphics card audio only no audio at all passing just the NVMe drive and not the storage drive rebuilt the machine using q35-5.0 instead of i440fx-5.0 installed a completely new instance of windows 10 to a vdisk not passing through any drives various permutations of CPU cores/pinning/isolation I am at a complete loss as to what to try next. I am hoping someone can point me in the right direction every thread i've found so far has been a dead end =/ Any help would be greatly appreciated! As far as testing goes i've been using latencymon(seeing interrupt to process latency up to 71416 microseconds and DPC routine execution time as high as 30911 microseconds) as well as just firing up a game and seeing how it plays. Here is my current XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>67a99274-6d55-5348-5429-af9ea7a40d9b</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='15'/> <emulatorpin cpuset='0,8'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-5.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/67a99274-6d55-5348-5429-af9ea7a40d9b_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-TOSHIBA_HDWF180_Y731Y0CVFZ1D'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:fb:b2:cf'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/roms/msi1080.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x02fe'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc539'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04d9'/> <product id='0x0296'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> </domain>

Having an issue with the permissions for this container. I'm trying to set the GID to 100 just like the rest of my containers but it keeps settings the permissions on all it's files to GID 101. Any idea what's going on with this? I see the below in the logs when starting the container ... groupmod: GID '100' already exists but I don't see this error for other groups that exist on the host, I'm guessing this is something it's trying to do inside the container. How can I run this container with GID 100?

I ran into this same issue, it looks like the VPN server I was using (CA Vancouver) either removed support for port forwarding or is just down or gone. I swapped out to Spain and everything was fine. If you check the output of the docker logs it will list all the servers that support port forwarding and it appears to be a real time check so if your server ever comes back it should show up in the list.

Just pulled down the latest version and it is working for me so far as well.