July 20, 20241 yr Anyone ever seen these, i moved from an Intel Ethernet Card to another with an Intel Ethernet Card. I tried upgrading but that didn't make any difference. These messages weren't there before switching out the motherboard. Attaching Diagnotics, anyone have any suggestions on how to fix it. Jul 21 05:37:43 Tower kernel: veth7574e5c: renamed from eth0 Jul 21 05:37:43 Tower kernel: eth0: renamed from veth246d9d3 Jul 21 05:38:00 Tower kernel: veth246d9d3: renamed from eth0 Jul 21 05:38:01 Tower kernel: eth0: renamed from veth7257c17 Jul 21 05:38:17 Tower kernel: veth7257c17: renamed from eth0 Jul 21 05:38:18 Tower kernel: eth0: renamed from veth74ebec2 Jul 21 05:38:35 Tower kernel: veth74ebec2: renamed from eth0 Jul 21 05:38:35 Tower kernel: eth0: renamed from vethb478acf Jul 21 05:38:52 Tower kernel: vethb478acf: renamed from eth0 Jul 21 05:38:53 Tower kernel: eth0: renamed from veth6960e55 Jul 21 05:39:10 Tower kernel: veth6960e55: renamed from eth0 Jul 21 05:39:10 Tower kernel: eth0: renamed from veth8ff1cbc Jul 21 05:39:28 Tower kernel: veth8ff1cbc: renamed from eth0 Jul 21 05:39:28 Tower kernel: eth0: renamed from vethbe2c01a Jul 21 05:39:45 Tower kernel: vethbe2c01a: renamed from eth0 Jul 21 05:39:45 Tower kernel: eth0: renamed from vethe11298f Jul 21 05:40:03 Tower kernel: vethe11298f: renamed from eth0 Jul 21 05:40:03 Tower kernel: eth0: renamed from veth470aa43 Jul 21 05:40:19 Tower kernel: veth470aa43: renamed from eth0 Jul 21 05:40:19 Tower kernel: eth0: renamed from vethd2261d5 Jul 21 05:40:36 Tower kernel: vethd2261d5: renamed from eth0 Jul 21 05:40:36 Tower kernel: eth0: renamed from veth23b3f6b Jul 21 05:40:52 Tower kernel: veth23b3f6b: renamed from eth0 Jul 21 05:40:53 Tower kernel: eth0: renamed from veth96c40fb Jul 21 05:41:10 Tower kernel: veth96c40fb: renamed from eth0 Jul 21 05:41:10 Tower kernel: eth0: renamed from veth91b9029 Jul 21 05:41:27 Tower kernel: veth91b9029: renamed from eth0 Jul 21 05:41:27 Tower kernel: eth0: renamed from veth3c239da Jul 21 05:41:44 Tower kernel: veth3c239da: renamed from eth0 Jul 21 05:41:44 Tower kernel: eth0: renamed from veth62b354d Jul 21 05:42:01 Tower kernel: veth62b354d: renamed from eth0 Jul 21 05:42:02 Tower kernel: eth0: renamed from vetha5e03e2 Jul 21 05:42:18 Tower kernel: vetha5e03e2: renamed from eth0 Jul 21 05:42:19 Tower kernel: eth0: renamed from veth009bc2e Jul 21 05:42:36 Tower kernel: veth009bc2e: renamed from eth0 Jul 21 05:42:36 Tower kernel: eth0: renamed from veth705ed30 Jul 21 05:42:53 Tower kernel: veth705ed30: renamed from eth0 Jul 21 05:42:53 Tower kernel: eth0: renamed from veth15e9705 Jul 21 05:43:01 Tower kernel: veth15e9705: renamed from eth0 Jul 21 05:43:13 Tower kernel: eth0: renamed from veth791e18a Jul 21 05:43:30 Tower kernel: veth791e18a: renamed from eth0 Jul 21 05:43:31 Tower kernel: eth0: renamed from veth53e22e4 Jul 21 05:43:47 Tower kernel: veth53e22e4: renamed from eth0 Jul 21 05:43:48 Tower kernel: eth0: renamed from vethcbcc80c tower-diagnostics-20240720-1946.zip
July 20, 20241 yr Community Expert That suggests you have a container constantly restarting, check their uptimes to see if you can find out which.
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.