zlacker

[return to "NASA mistakenly severs communication to Voyager 2"]
1. hutzli+79[view] [source] 2023-07-31 11:41:35
>>belter+(OP)
In short, it was remote bricked, by giving it commands to rotate a bit. After successfully executing those commands - no further commands could be received, as now the antennas are not facing earth anymore.

But luckily it automatically readjust itself to earth automatically every half year exactly for these events. So on 15.10 we will know, if it is really lost. In either case, the end of its mission is near anyway, because the nuclear batteries are near its end.

edit: Nasa has a blog post on this https://blogs.nasa.gov/sunspot/2023/07/28/mission-update-voy...

◧◩
2. dylan6+2H1[view] [source] 2023-07-31 18:50:13
>>hutzli+79
reminds me of the time I forgot i was on a remote connection, and could not figure out why the thing quit responding when i typed eth0 down
◧◩◪
3. manana+wb2[view] [source] 2023-07-31 21:22:23
>>dylan6+2H1
The Debian package installer once asked me (a long long time ago) whether I want to restart sshd after a glibc update, saying existing sessions wouldn’t be affected. That was a lie, apparently, because the SSH session I was updating the system died and the resulting SIGHUP killed the update process in a way that necessitated some recovery later.

More seriously, Mikrotik routers have a nice feature where they will rollback your config change if the connection you’re configuring one over stops responding to keepalives. Like a lot of Microtik features, it’s probably copied from some Serious Business network OS, but I wouldn’t know.

[go to top]