Sys admin shit is hell.

Proxmox and its first VM working great... until it isn't. Spontaneously. Looks like everything is still running but the networking is getting knocked out.

Googling... specific ethernet controller + specific driver release = these failures. Sure, yeah, that classic "r8168 vs r8169" gotcha.

How do I install/revert to r8168? Enable `non-free-firmware` apt sources. But, what... can't resolve the domains? Total DNS failure... Oh, DNS server is set to localhost? Update to 8.8.8.8 (this is shit I'm surprised I know and am not happy it's taking space in my brain). Ah, now able to resolve DNS.

Cool, back to apt. Can't update from an unsecure repository? Okay, googling... edit `/etc/apt/sources.list` (again).

Nope, not there. Ah, remove the proxmox enterprise repos...

(endless spiraling sys admin hell continues)

Reply to this note

Please Login to reply.

Discussion

Installed the r8168 driver. Reboot. Networking now totally dead!

Gonna give it a bit more googling, but will probably just nuke it all and start over.

πŸ˜‚πŸ˜‚πŸ˜‚. I feel you on all of this. I’ve been a Windows sys admin for years and have only dabbled in Linux. I have been on similar rabbit holes many times and usually it ends with me getting pissed and quitting. Only to pick it back up again a few weeks later. Proxmox is cool and worth the work though!

Looking forward to this awaiting madness. Bitcoin node is the last bit missing on my nuc. I expect everything to work for a couple of days, making me feel like a master overlord, then crash and letting me burn in hell.

These steps are fairly ancient now, but still helped me figure out how to configure some things for my node yesterday. Def helpful to have me in the past explaining something I've long since forgotten to me in the present!

https://github.com/kdmukai/raspi4_bitcoin_node_tutorial

That looks amazing. Definitely going to have a look and find out what I have missed in my current setup to make it better in the new one πŸ€™

Bitcoin Core itself is fairly all-terrain. If the hardware is adequate it shouldn't give you too many headaches.

Not so much with the LN stuff, unfortunately πŸ˜„

keith you are bothered with the same issues as me with proxmox and the realtek network driverπŸ˜…

i will try the kernel downgrade to 5.x.x lts

I "fixed" it by finally managing to install the r8168 driver. But after a reboot, networking was totally dead. I haven't had time to do any further debugging.

Q1: Have you installed "pve-headers" before the "r8169-dkms" package?

Q2: In the folder "/etc/modprobe.d" is a "r8168-dkms.conf"

Uncomment the last line and reboot this fix worked for me. but network is still unstable, so I will try the 5.15 kernel.

Network looks more stable with kernel 6.2.16-3 (I think you Proxmox 8 runs with >=6.2.16-6)

So far so good for me with Proxmox v7.4-3! Zero network dropouts.