Re:NASA mistakenly severs communication to Voyager 2
by renewiltord on Monday July 31, 2023 @04:28PM
(#36948317)
Had a node that I was connected to over wireguard. Wanted to reset the wireguard conf.
Nice one, mate. Had to drive back to log in and bring up that interface. I still do this, FWIW, but now I use `at` to schedule "up" 1 min in future haha. So far so good though it's not smart :)
[ Parent
| on HN ]
Re:NASA mistakenly severs communication to Voyager 2
by dylan604 on Monday July 31, 2023 @05:00PM
(#36948751)
Luckily for me, I just had to go down the hall to the data center, and then reset it with the local terminal. Compared to you, I learned the lesson on the cheap, but you got the bonus of a nice get out of jail free card. Neat CYA trick that I will keep in mind.
Re:NASA mistakenly severs communication to Voyager 2
by dekhn on Monday July 31, 2023 @08:17PM
(#36950706)
There's a feature in many business data centers called "remote hands". Mainly to avoid the drive/flight to admin a remote machine.
Re:NASA mistakenly severs communication to Voyager 2
by owenmarshall on Monday July 31, 2023 @08:29PM
(#36950792)
> FWIW, but now I use `at` to schedule "up" 1 min in future
Any time I’m ever doing a pfctl to change my router’s firewall rules I schedule a “revert to the n-1 rule set” job two minutes from now to avoid the trip to the basement & hunt for the serial cable.
I do +2 because once I was too close to the next minute, fat-fingered the update command & instinctively corrected it. But the change had reverted before I hit enter on the new update, so of course I blocked too much traffic and wedged my SSH connection, triggering the cursing and trip to the basement with the serial cable.