Papi_Sosa

So I just want to post an update to this. I think this was closely related to the network issue I had seen earlier that clued to the IPv6 spam in the log. As mentioned before, disabling IPv6 did not resolve the issue and just eliminated the noise in the logs. I looked into my networking equipment a bit and found out that the switchport that my server was plugged into was actually faulty and generating a bunch of errors. I swapped out the switch and the server has been stable now for the last 3 weeks with no errors being reported on the port. I'll keep the post open a little longer just to clear my suspicions but so far it's looking good.

I’m not sure what the Mystic Light device is (Could be an RGB controller in my keyboard), I do have a KVM that I use to move my mouse and keyboard between my main computer and the server for my VM so sometimes that spits out errors when I click the switch. There is a BIOS update available so I’ll try updating that tonight.

The router is a Ubiquiti UDM-SE and the server is connected to a USW-8-Pro-PoE that is acting as my core switch. IPv6 address leasing for an hour sounds strange. It's configured for 24 hours in the LAN configuration for the subnet.

That was when I disabled the Docker Manager and VM Manager so I could change the network protocol from "IPv4 + IPv6" to "IPv4 only". I just checked the switch port that the server is connected to and I see some Tx and Rx errors. The errors don't appear to be incrementing so I'll keep an eye on it.

IPv6 to the server itself was disabled but the IPv6 addressing to the ISP router and my router are still active. The ISP router is in bridged mode so my router is seeing the public IP directly.

The server primarily uses IPv4. I don't have it statically configured in the server as I do all of my IP reservations from the DHCP server itself. IPv6 was just an addition from the ISP that I allowed my router to propagate to clients on my networks and isn't really required for anything. If it's the cause of the problem then I'll leave it disabled.

Sorry, here is the diagnostic zip. Hopefully this helps. I also disabled IPv6 on the server for the time being in case that was the problem. salisbury-htpc-diagnostics-20241018-2352.zip

The issue happened today at 18:17. Looks like it might be an issue associated with IPv6? syslog-previous syslog

Hello, I wanted to see if anybody would be able to help me understand why my server keeps crashing. Today has been the most amount of times it's crashed in a single day (4 times) and I'm not sure why it's doing it and I don't know where to begin to troubleshoot. This doesn't appear to be specific to 6.12.13 as it was happening before and had calmed down a bit over the past few months however it's progressively gotten worse in the past 2 weeks. Any help on where to start would be greatly appreciated.

Hi there, I've been experiencing some slow performance with my Windows 10 VM and I wanted to know what the issue might be. I've watched the Spaceinvader videos however nothing has improved. Some games won't break 30 fps and will stutter and others will crash shortly after launch. Motherboard: MSI Z590-A CPU: Intel i7-11700K RAM: 64GB DDR4 (VM is set to use 32GB) Graphics Card: ASUS TUF RTX 3060 (I have it passed to the VM but I don't remember how it was done) Storage: VM Storage is 500GB SSD however there is a "share" folder in the array CPU Pinning for VM: 3,5,6,7 HT Pinning for VM: 11,13,14,15 Same CPU and HTs are isolated. I've attached my VM XML file below if anybody can review it and provide some suggestions or insight. I had tweaked the XML file at some point so that the VM appears as a host rather than a VM. Win10-VM-XML