Server network interface seems to hang sporadically (nothing to be found in the logs)


Recommended Posts

Hi everyone,

I am currently facing a critical issue with my Unraid server's network hanging for reasons I don’t know. Physically reconnecting or disabling/enabling the port on my UniFi switch brings the server back online.

 

I used to have this issue when my Debian VM with GPU passthrough was running. Plugging the ethernet cable in and out solves the issue for the next few minutes. With the VM being shut down, the server remained accessible. (I have created a thread on that in the past)

 

I assumed that there was some network storming caused by the VM and to troubleshoot I created a new VLAN in which only the VM is running (managed by my UniFi UDM Pro). The server has not become inaccessible since then until yesterday. But this time not due to my GPU passthrough VM but rather due to the ZWaveJS2MQTT Docker.

 

I checked my Home Assistant VM as I can see when devices (the network) became unavailable. The last two times were in the following timespans:

 

Offline 8:46 - 8:58

Online in between

Offline 9:59 - 10:13

 

I have not touched the port settings or the cable itself. It became available again on its own - just to say bye bye again shortly after. 😞

 

I can't find anything in dmesg nor in the syslog:

 

dmesg -T:
[Thu May 19 08:33:58 2022] usb 1-1.4: new full-speed USB device number 5 using xhci_hcd
[Thu May 19 08:33:58 2022] usb 1-1.4: device descriptor read/64, error -32
[Thu May 19 08:33:58 2022] usb 1-1.4: device descriptor read/64, error -32
[Thu May 19 08:33:58 2022] usb 1-1.4: new full-speed USB device number 6 using xhci_hcd
[Thu May 19 08:33:59 2022] usb 1-1.4: device descriptor read/64, error -32
[Thu May 19 08:33:59 2022] usb 1-1.4: device descriptor read/64, error -32
[Thu May 19 08:33:59 2022] usb 1-1-port4: attempt power cycle
[Thu May 19 08:34:00 2022] usb 1-1.4: new full-speed USB device number 7 using xhci_hcd
[Thu May 19 08:34:00 2022] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device
[Thu May 19 08:34:59 2022] eth0: renamed from vethf1123ae
[Thu May 19 09:51:56 2022] usb 3-4.4: new full-speed USB device number 4 using xhci_hcd
[Thu May 19 09:51:57 2022] cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device
[Thu May 19 09:52:00 2022] usb 3-4.4: USB disconnect, device number 4
[Thu May 19 09:52:00 2022] usb 3-4.4: new full-speed USB device number 5 using xhci_hcd
[Thu May 19 09:52:00 2022] cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device
[Thu May 19 09:53:52 2022] veth97f0b8f: renamed from eth0
[Thu May 19 09:53:52 2022] docker0: port 3(vethf6f1318) entered disabled state
[Thu May 19 09:53:53 2022] docker0: port 3(vethf6f1318) entered disabled state
[Thu May 19 09:53:53 2022] device vethf6f1318 left promiscuous mode
[Thu May 19 09:53:53 2022] docker0: port 3(vethf6f1318) entered disabled state
[Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered blocking state
[Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered disabled state
[Thu May 19 09:53:54 2022] device veth1c69dab entered promiscuous mode
[Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered blocking state
[Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered forwarding state
[Thu May 19 09:53:54 2022] docker0: port 3(veth1c69dab) entered disabled state
[Thu May 19 09:53:56 2022] eth0: renamed from vethaefd029
[Thu May 19 09:53:56 2022] IPv6: ADDRCONF(NETDEV_CHANGE): veth1c69dab: link becomes ready
[Thu May 19 09:53:56 2022] docker0: port 3(veth1c69dab) entered blocking state
[Thu May 19 09:53:56 2022] docker0: port 3(veth1c69dab) entered forwarding state
[Thu May 19 10:51:49 2022] usb 3-4.4: USB disconnect, device number 5
[Thu May 19 10:51:50 2022] usb 3-4.4: new full-speed USB device number 6 using xhci_hcd
[Thu May 19 10:51:50 2022] cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device
[Thu May 19 10:51:53 2022] usb 3-4.4: USB disconnect, device number 6
[Thu May 19 10:51:53 2022] usb 3-4.4: new full-speed USB device number 7 using xhci_hcd
[Thu May 19 10:51:54 2022] cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device

cat /var/log/syslog:
May 19 08:34:59 GRAViTY kernel: eth0: renamed from vethf1123ae
May 19 08:59:05 GRAViTY vsftpd[19965]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:05 GRAViTY vsftpd[19965]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:05 GRAViTY vsftpd[19969]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:05 GRAViTY vsftpd[19969]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:22 GRAViTY vsftpd[20033]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:22 GRAViTY vsftpd[20033]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:22 GRAViTY vsftpd[20038]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:22 GRAViTY vsftpd[20038]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:22 GRAViTY vsftpd[20044]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:22 GRAViTY vsftpd[20044]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:22 GRAViTY vsftpd[20047]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:22 GRAViTY vsftpd[20047]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:22 GRAViTY vsftpd[20053]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:22 GRAViTY vsftpd[20053]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:23 GRAViTY vsftpd[20056]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:23 GRAViTY vsftpd[20056]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:23 GRAViTY vsftpd[20059]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:23 GRAViTY vsftpd[20059]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:23 GRAViTY vsftpd[20070]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:23 GRAViTY vsftpd[20070]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:23 GRAViTY vsftpd[20073]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:23 GRAViTY vsftpd[20073]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:23 GRAViTY vsftpd[20076]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:23 GRAViTY vsftpd[20076]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:23 GRAViTY vsftpd[20079]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:23 GRAViTY vsftpd[20079]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:23 GRAViTY vsftpd[20082]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:23 GRAViTY vsftpd[20082]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:23 GRAViTY vsftpd[20101]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:23 GRAViTY vsftpd[20101]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 08:59:23 GRAViTY vsftpd[20104]: connect from 10.10.10.62 (10.10.10.62)
May 19 08:59:23 GRAViTY vsftpd[20104]: [mediaclient] OK LOGIN: Client "10.10.10.62"
May 19 09:51:57 GRAViTY kernel: usb 3-4.4: new full-speed USB device number 4 using xhci_hcd
May 19 09:51:57 GRAViTY kernel: cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device
May 19 09:52:01 GRAViTY kernel: usb 3-4.4: USB disconnect, device number 4
May 19 09:52:01 GRAViTY kernel: usb 3-4.4: new full-speed USB device number 5 using xhci_hcd
May 19 09:52:01 GRAViTY kernel: cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device
May 19 09:53:53 GRAViTY kernel: veth97f0b8f: renamed from eth0
May 19 09:53:53 GRAViTY kernel: docker0: port 3(vethf6f1318) entered disabled state
May 19 09:53:54 GRAViTY kernel: docker0: port 3(vethf6f1318) entered disabled state
May 19 09:53:54 GRAViTY kernel: device vethf6f1318 left promiscuous mode
May 19 09:53:54 GRAViTY kernel: docker0: port 3(vethf6f1318) entered disabled state
May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered blocking state
May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered disabled state
May 19 09:53:55 GRAViTY kernel: device veth1c69dab entered promiscuous mode
May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered blocking state
May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered forwarding state
May 19 09:53:55 GRAViTY kernel: docker0: port 3(veth1c69dab) entered disabled state
May 19 09:53:56 GRAViTY kernel: eth0: renamed from vethaefd029
May 19 09:53:56 GRAViTY kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1c69dab: link becomes ready
May 19 09:53:56 GRAViTY kernel: docker0: port 3(veth1c69dab) entered blocking state
May 19 09:53:56 GRAViTY kernel: docker0: port 3(veth1c69dab) entered forwarding state
May 19 10:51:50 GRAViTY kernel: usb 3-4.4: USB disconnect, device number 5
May 19 10:51:50 GRAViTY kernel: usb 3-4.4: new full-speed USB device number 6 using xhci_hcd
May 19 10:51:51 GRAViTY kernel: cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device
May 19 10:51:54 GRAViTY kernel: usb 3-4.4: USB disconnect, device number 6
May 19 10:51:54 GRAViTY kernel: usb 3-4.4: new full-speed USB device number 7 using xhci_hcd
May 19 10:51:55 GRAViTY kernel: cdc_acm 3-4.4:1.0: ttyACM1: USB ACM device

 

Diagnostics file is attached.

gravity-diagnostics-20220519-1157.zip

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.