So I’m working on a server from home.
I do a cat /sys/class/net/eth0/operstate and it says unknown despite the interface being obviously up, since I’m SSH’ing into the box.
I try to explicitely set the interface up to force the status to say up with ip link set eth0 up. No joy, still unknown.
Hmm… maybe I should bring it down and back up.
So I do ip link set eth0 down and… I drive 15 miles to work to do the corresponding ip link set eth0 up
50 years using Unix and I’m still doing this… 😥
If I understand, this is less a complaint about how UNIX works and more a story about the consequences of careless mistakes.
This is why we have KVMs I guess. Though not every server has one of those.
I’ve been trying to find a network capable KVM for home use. They’re all pretty expensive or lacking functionality. I don’t actually need one or I’d pull the trigger, but I sure have been tempted.
Check out JetKVM
Nice! I currently have a PiKVM but haven’t been able to get it working with my NVR. Maybe this would work better.
I had a remote relay box: 8 channels of power control, so I could at least power cycle machines from remote when all else failed.
I actually ended up not using it much at all, it was a nice security blanket, but the last time I decided that I wanted to power cycle something was about 6 years ago, and at that time I realized it had been over 3 years since I had previously used it, and that usage was more of a “let’s make sure this thing is working like I think it should” test.
I don’t buy servers without iDRAC enterprise licenses. It’s too damn useful.