You must log in or register to comment.
Next hardware reset and automatic reorientation for Voyager 2 is October 15th. Yes the device automatically resets itself about four to five times a year. Communications are expected to be reestablished then.
In the meantime, they’re going to shout at it.
That’s good news! I was about to ask whether they have some absolute software recovery procedure and glad they do!
That’s great to know. This post made me weirdly depressed and was a bad way to start the morning lol.
Almost like real engineers planned for such an event!
Someone ran ‘systemctl restart networking’ while SSH’d into the probe.
Wikipedia states: “In July 2023, communication with Voyager 2 was lost when flight control pointed its antenna away from Earth, moving it by 2 degrees away from Earth. The NASA dish antenna in Canberra is being used to search for the space probe and will be used to saturate its location with commands to re-align the probe’s antenna in an attempt to re-establish the radio link. If NASA fails to contact the probe, it is expected that an automatic system on Voyager 2 will direct its dish toward Earth in October 2023.”
Great that they included these automatic hardware resets. Way to go if your computer will never see a human or human-made thing ever again
So essentially someone probably wanted to move it one way and it moved the other. It should automatically reposition itself in contact with NASA in 2 months. It’s amazing the foresight we had in 1977 to write in all sorts of catch-alls… In 2 months we’ll get back in contact with the probe and it will have its own place, hanging out with aliens.
Sounds like those two need to go to couples therapy.
V2 be like: “WHAT did you say about my mother? F… you, Earth man.”
Mission control: “Dude you don’t have a mother it was a typo. Dude. Talk to me.”
seenMission control: “Dude.”
seenMission control: “C’mon man.”
This message could not be sent. V2 may have blocked your numberYou just need to reboot it manually
Just press and hold the power button smh
Hello IT, have you tried turning it off and on again?
That’s why your color your production windows red.
When you ufw enable but forgot to whitelist port 22
sudo rm -rf --no-preserve-root /sudo rm -rf /*
