September 26, 20232 yr Hi all, I'm a long time user and a first time poster, and I could use a little bit of help. I tried posting earlier, but it doesn't look like my post was submitted. Anyway, we all have those homelab issues that we just live with. I've had one of those issues for quite a long time, however, now they are interfering with the day to day by getting increasingly worse. - I seem to have a problem throughout the day where Unraid GUI, and even ssh lag to the point of timing out. There doesn't appear to be anything in the logs that has caught my eye, and nobody in the house (or connected from the outside) notice a pattern to the unresponsiveness. -Docker containers are unresponsive, VMs, etc, etc... -Possibly related - yesterday afternoon I was transferring a zip file from one of my workstations to my unraid box (80+GB) that would not complete the transfer. SMB, 80GB file. I attempted to send this file multiple times from different computers on the network. Would anyone be willing to take a look at my diagnostic dump to see what might be going on? --Likely a best practice that I missed somewhere. Thank you for any help and time that your are willing to give. Best, -DroidLev unraid1-diagnostics-20230926-0742.zip
September 26, 20232 yr Community Expert Sep 26 07:33:43 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 07:33:44 unraid1 kernel: device eth0 left promiscuous mode Sep 26 07:36:24 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 07:36:35 unraid1 kernel: device eth0 left promiscuous mode Sep 26 07:36:35 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 07:36:36 unraid1 kernel: device eth0 left promiscuous mode Sep 26 07:36:36 unraid1 kernel: device eth0 entered promiscuous mode This is likely not the problem but it's spamming the log, see if you have a container constantly restarting, you can check the uptimes.
September 26, 20232 yr Author 1 hour ago, JorgeB said: Sep 26 07:33:43 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 07:33:44 unraid1 kernel: device eth0 left promiscuous mode Sep 26 07:36:24 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 07:36:35 unraid1 kernel: device eth0 left promiscuous mode Sep 26 07:36:35 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 07:36:36 unraid1 kernel: device eth0 left promiscuous mode Sep 26 07:36:36 unraid1 kernel: device eth0 entered promiscuous mode This is likely not the problem but it's spamming the log, see if you have a container constantly restarting, you can check the uptimes. Thanks! Did a server reboot about 5 hours ago, I'll check the uptimes as soon as I notice a change. (right now, everything that came up, is still up). Thank you for the suggestion. I'll take any other suggestions with regards to path mappings, etc, etc *if you notice anything odd.
September 26, 20232 yr Author 2 hours ago, droidlev said: Thanks! Did a server reboot about 5 hours ago, I'll check the uptimes as soon as I notice a change. (right now, everything that came up, is still up). Thank you for the suggestion. I'll take any other suggestions with regards to path mappings, etc, etc *if you notice anything odd. Sep 26 15:51:21 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:51:21 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:51:21 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:51:21 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:51:22 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:51:22 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:51:23 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:51:23 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:51:23 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:51:23 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:51:24 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:54:20 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:54:31 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:54:31 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:54:31 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:54:31 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:54:32 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:54:32 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:54:33 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:54:33 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:54:33 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:54:33 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:54:34 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:57:32 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:57:43 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:57:43 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:57:43 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:57:43 unraid1 kernel: device eth0 entered promiscuous mode Sep 26 15:57:44 unraid1 kernel: device eth0 left promiscuous mode Sep 26 15:57:44 unraid1 kernel: device eth0 entered promiscuous mode There does not appear to be a correlation between my naughty (ahem, promiscuous) eth0 and docker uptime. No containers were knocked offline during the above errors. I was able to access the server GUI during this time. So although this is concerning, it doesn't appear to be directly related do the random lag-outs. . Appreciate the input.
September 27, 20232 yr Community Expert 11 hours ago, droidlev said: , it doesn't appear to be directly related do the random lag-outs. Like mentioned I didn't expect there to be a relation, but it makes analyzing the logs to look for something else very difficult.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.