OMV Version: 6.9.14-1
Kernel: Linux 6.1.0-0.deb11.13-amd64
CPU: Intel i7-4790K 4GHz
32GB RAM
~7GB-8 RAM in use maximum at any time.
1 SSD that's 1TB in size with only 5% in use.
[I repurpose my old PCs for OMV, I know the above is overkill but better to reuse what I have]
I'm not sure when this started, it's been happening for at least a month or maybe longer now. When I connect to OMV using PuTTY on Windows 11 23H2, after a minute (just timed it, it seems rather consistent), the terminal will stop responding and PuTTY will say "Network error: Software caused connection abort". I tried enabling logging in PuTTY but I don't see any errors in the log.
What's odd is that when this happens, I still have no issues connecting to the web GUI (again, all is being done on the same local subnet), nor any of my docker containers, nor does the web GUI respond slowly (or the docker containers). So I definitely can connect to the device. I have a monitor attached to it for debugging purposes in the event I can't log in via a browser, and haven't seen any errors appear on the screen there either.
I realize trying to troubleshoot with such little info is impossible. Obviously, there could be configuration issues not at all related to OMV (such as switches or other installed plugins).
So before doing a deep dive and asking for a magic solution, what would be the best way to start troubleshooting this issue on my end before reporting back? I'm not sure which log(s) to look at (if any). I basically need to just be pointed in the right direction for where to start looking before I waste a bunch of people's time with things I could be trying on my end first. In case it matters, I have the following plugins installed:
- compose
- diskstats
- kernel
- locate
- omvextrasorg
- remotemount
- sharerootfs
- symlinks
Much appreciated.