M2Pilot

While reading other posts, I think I found the issue. Somehow, my Docker configuration returned to using Macvlan. I have reconfigured it back to IPvlan -- hopefully this resolves the issue for me. I'd still be interested in learning how to get better systems logs if there is a way.

Hello All For months/years Unraid was rock-solid for me. But over the last ~4 months, it has become increasingly unstable. By this I mean the entire system becomes unresponsive and I must pull power to get it to respond. Initially it was maybe once a month this would happen. Then it became weekly. Now it is daily & the system is no longer reliable at all. There is no rhyme or reason to when it decides to hang -- sometimes in the middle of the day, sometimes in the middle of the night. Sometimes the system is dead as a door nail. Other times I can get some limited response from the web UI, but this usually hangs hard within a minute or two of clicking around trying to figure out what is going on. I've tried looking at logs, but the system logs only seem to exist from when the server is restarted -- meaning I can't see logs from the hang, only starting from the reboot. Surely there must be older logs than that, but I can't find them. Any suggestions on how to diagnose this would be appreciated! Mark

I also am troubled by the seemingly unnecessary updates to this app. Gets my 'have I been hacked' antennae wiggling.

Am I the only one troubled by the seemingly non-existent cadence for security patch releases on unRaid? Don't get me wrong - I love me some UnRaid and talk it up every chance I get. But I'm wondering whether I should be heaping quite so many praises Limetech's way. We are now 10 months since 6.9.2 stable was released. That's a long time. Lots of CVEs posted since then. CVE-2021-44142 (the one being talked about above) is only the latest high severity issue (a 9.9 out of 10). 6.9 was followed a month later by 6.9.1 (CVE-2021-23841, CVE-2021-23840) and then a month after that by 6.9.2 (CVE-2020-27840, CVE-2020-27840). That's the kind of cadence I can feel confident in. But after April 2021? Nothing. I would like to see what published policy Limetech has for security patching. I'm not aware of any (please correct me if this is wrong). Assuming no security patching policy exists, we should be pushing for one, and then help make sure they live up to it.

Hi All- I've been struggling with creating custom docker containers on UnRaid -- specifically figuring out which elements on a docker run command belong where when it comes to UnRaid. To cut to the chase, I'm trying to follow the quickstart guide for Cassandra DB (https://cassandra.apache.org/_/quickstart.html) and there are a number of docker run commands for establishing the dockerized instance and then interacting with it. The area where I'm particularly having issues is with the --network option. Here are two examples: docker run --rm -d --name cassandra --hostname cassandra --network cassandra cassandra docker run --rm --network cassandra -v "$(pwd)/data.cql:/scripts/data.cql" -e CQLSH_HOST=cassandra -e CQLSH_PORT=9042 nuvo/docker-cqlsh In both cases I remove elements which are handled differently by unraid (e.g., the rm, setting the name etc) but the network option has me baffled. Any pointers for this? The docs and other posts I've found don't really help. Thanks, Mark

Still seeing a few messages in the logs. I also ran into some issues this morning that seemed to be associated with the built-in hub of a dell keyboard. USB manager really did not like the hub, especially if I plugged the mouse into it. When I connected the mouse directly to the KVM switch, USB Manager was much happier. Here's the latest log with a few errors in it -- not sure if these are anything to be concerned about: Jan 5 11:39:37 SkiServer kernel: usb 1-2: USB disconnect, device number 103 Jan 5 11:39:37 SkiServer kernel: usb 1-2.1: USB disconnect, device number 104 Jan 5 11:39:37 SkiServer acpid: input device has been disconnected, fd 9 Jan 5 11:39:37 SkiServer kernel: usb 1-2.2: USB disconnect, device number 105 Jan 5 11:39:37 SkiServer kernel: usb 1-2.2.2: USB disconnect, device number 107 Jan 5 11:39:37 SkiServer kernel: usb 1-2.2.4: USB disconnect, device number 109 Jan 5 11:39:37 SkiServer kernel: usb 1-2.3: USB disconnect, device number 106 Jan 5 11:39:37 SkiServer kernel: usb 1-2.3.1: USB disconnect, device number 108 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager usb_remove /dev/bus/usb/001/109 001 109 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Device Match 046d_HD_Pro_Webcam_C920_F1F9C06F vm: Mark Windows 10 001 109 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager usb_remove /dev/bus/usb/001/108 001 108 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Device Match Logitech_USB_Receiver vm: Mark Windows 10 001 108 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager usb_remove /dev/bus/usb/001/104 001 104 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager usb_remove /dev/bus/usb/001/107 001 107 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Device Match C-Media_Electronics_Inc._USB_Audio_Device vm: Mark Windows 10 001 107 Jan 5 11:39:37 SkiServer usb_manager: usb_manager virsh called Mark Windows 10 1 109 Device detached successfully Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Disconnect 046d_HD_Pro_Webcam_C920_F1F9C06F vm: Mark Windows 10 running 001 109 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Removed 046d_HD_Pro_Webcam_C920_F1F9C06F vm: Mark Windows 10 running 001 109 Jan 5 11:39:37 SkiServer usb_manager: usb_manager virsh called Mark Windows 10 1 108 Device detached successfully Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Disconnect Logitech_USB_Receiver vm: Mark Windows 10 running 001 108 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Removed Logitech_USB_Receiver vm: Mark Windows 10 running 001 108 Jan 5 11:39:37 SkiServer usb_manager: usb_manager virsh called Mark Windows 10 1 107 error: Failed to open file '/tmp/libvirthotplugusbbybusMark Windows 10.xml': No such file or directory Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Disconnect C-Media_Electronics_Inc._USB_Audio_Device vm: Mark Windows 10 running 001 107 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Removed C-Media_Electronics_Inc._USB_Audio_Device vm: Mark Windows 10 running 001 107 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager usb_remove /dev/bus/usb/001/106 001 106 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Device Match ASIX_Electronics_AX68004_00000001 vm: 001 106 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager usb_remove /dev/bus/usb/001/105 001 105 Jan 5 11:39:37 SkiServer usb_manager: usb_manager virsh called 1 106 error: Failed to get option 'domain': Option argument is empty Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Disconnect ASIX_Electronics_AX68004_00000001 vm: nostate 001 106 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Removed ASIX_Electronics_AX68004_00000001 vm: nostate 001 106 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager usb_remove /dev/bus/usb/001/103 001 103 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Device Match 1a40_USB_2.0_Hub vm: 001 103 Jan 5 11:39:37 SkiServer usb_manager: usb_manager virsh called 1 103 error: Failed to get option 'domain': Option argument is empty Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Disconnect 1a40_USB_2.0_Hub vm: nostate 001 103 Jan 5 11:39:37 SkiServer usb_manager: Info: rc.usb_manager Removed 1a40_USB_2.0_Hub vm: nostate 001 103

Seems to be working now, Simon -- thanks. I had to manually go into the VM xml interface to clean out all the residue of USB mappings. Once I configured USB Manager, i had to restart the VM. After doing that, for the first time I successfully switched from the VM to the laptop and back again with no hangs. Mark

My KVM does have dedicated mouse and kdb ports. It also allegedly does EDID. I've never had an issue with monitors not being in the "right place" when switching between devices. That all being said, this is hardly the creme-de-la-creme of KVM devices. I ran several tests and captured diagnostics. I also made a timeline of what I was doing at what time. Finally, I have a diagram of how things are physically connected up. Hopefully this helps identify if I'm doing something wrong, or if there is an issue inside unraid usb handling. mrs KVM timeline skiserver-diagnostics-20220104-1151 -- KVM switch back and forth.zip kvm setup.pdf

I will create a diagram and can post diagnostics. Is there any value to running diagnostics before attempting using the switch and then again after? In any case, I will also include a timeline of when I tried & when I tried it so it is easy to find associated messages in the logs. Thanks, Mark

Hello- I've been trying to use a physical KVM switch to move between both physical PCs and VMs running under UnRaid 6.9. This has not proved to be successful (for the Unraid VM portion) -- to the point where simply trying to switch to an Unraid VM with the KVM can destabilize the entire system. In the most innocuous case, the VM simply does not recognize the mouse and keyboard when the KVM switch is used. To clear this problem, I must unmap and then remap USB devices from the VM for them to be recognized. Sometimes I have to restart the VM to clear the issue. Once cleared, the mouse and keyboard behave normally. A more significant issue is when switching to the VM not only results in the keyboard and mouse not being recognized by the VM, but also the webgui of the Unraid server becoming unresponsive for 60-120 seconds. The most significant issue is when switching to the VM not only results in the keyboard and mouse not being recognized by the VM, but the webgui reports it is no longer able to access the unraid OS thumb drive and the server must be either manually rebooted, or crashes. This has occurred 3 times over the last 2 days of testing this. Clearly, the KVM switch is causing something bad to happen within the USB management aspects of UnRaid. Whether the KVM switch is uncleanly attaching/detaching the USB devices is not clear. Weirdly, other USB devices (e.g., USB headset, USB Webcam) switch fine every time. It's only the keyboard and mouse which seem to cause mischief. I would be happy to help troubleshoot this more.

Alas, using the USBIP plugin does not immediately solve the problem. But does seem to give a hint what the problem is. See the attached screen shot. Note the error reported for both the keyboard and mouse. Who might I report this to??

I'm in the same boat as others above - need to use my physical KVM switch to move between unraid VMs with my single keyboard and mouse. As other have said, when the kvm switches to a different unraid VM, things lock up. Right now I'm just trying to switch between my laptop and a single unraid VM. So I have mapped the USB devices for mouse and kbd to that vm. When I first save the config, it works great. I switch the physical KVM to my laptop, and that works great. I switch back to the VM and the KBD and Mouse are dead. I have to unmap them and remap them in unraid control panel to get them to work again. I'll try the suggested solution to see if that works. If not, I'm eager to work with someone to figure out whats going on & what to do about it.

In addition to the above, it is necessary to update the bios for this mobo. Bios versions older than .60 not boot normally with both IGD and multiple PCI devices plugged in. Once the bios is updated to .60, boot will behave more normally.

I am tearing my hair out trying to actually access the GitLab CE instance from a development workstation. Accessing the WebUI via unraid works fine - I can peruse the settings the live long day. As I mentioned above, I even have emails being sent for new users now. But actually trying to connect via a git command line, as it shows for the project I set up in the WebUI just isn't happening for me. I follow the command lines to the letter, but always get a login failure when I try to push to master: git@unraid: Permission denied (publickey,password,keyboard-interactive). fatal: Could not read from remote repository. I am completely baffled why this is not working for me. Any can set me straight?

I just got gmail based SMTP working today. If you check the production.log for your install you will likely find password failures in there from Gmail. The trick is that you need to understand that Gmail considers GitLab-CE to be a "less secure app" and will automatically block any login attempts from it *unless* you configure your gmail account to allow "less secure apps" to connect. In my case, I'd created a new gmail account for it but had not enabled less secure apps. As soon as I did, email started flowing normally.