top 50 comments

sorted by: hot top controversial new old
[–] 144 points 3 years ago (4 children)

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.

  • source
  • hideshow 4 child comments
  • [–] 58 points 3 years ago (4 children)

    Someone ran 'systemctl restart networking' while SSH'd into the probe.

  • source
  • hideshow 4 child comments
  • [–] 4 points 3 years ago* (3 children)

    Unrelated but I've been wondering this for years: What's your avatar from and why do so many people across the web have that exact same one?

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (2 replies)
  • [–] 38 points 3 years ago (6 children)

    sudo rm -rf --no-preserve-root /

  • source
  • hideshow 6 child comments
  • [–] 22 points 3 years ago* (3 children)

    starman is not in the sudoers file.
    This incident will be reported.

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (1 reply)
  • load more comments (1 reply)
    [–] 34 points 3 years ago (2 children)

    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."

  • source
  • hideshow 2 child comments
  • [–] 34 points 3 years ago

    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.

  • source
  • parent
  • [–] 32 points 3 years ago (2 children)

    https://www.npr.org/2023/08/02/1191341035/nasa-voyager-2-spacecraft-contact

    Sounds like it's a recoverable error (if the scientists can't do it the spacecraft has an automated process that'll kick in in October.) Still, I can't imagine what that must feel like.

  • source
  • hideshow 2 child comments
  • load more comments (1 reply)
    [–] 32 points 3 years ago

    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."

    seen

    Mission control: "Dude."

    seen

    Mission control: "C'mon man."

    This message could not be sent. V2 may have blocked your number

  • source
  • [–] 29 points 3 years ago (1 child)

    You just need to reboot it manually

  • source
  • hideshow 1 child comment
  • [–] 27 points 3 years ago

    That's why your color your production windows red.

  • source
  • [–] 25 points 3 years ago (1 child)

    When you ufw enable but forgot to whitelist port 22

  • source
  • hideshow 1 child comment
  • [–] 22 points 3 years ago

    Hello IT, have you tried turning it off and on again?

  • source
  • [–] 16 points 3 years ago

    Probably played with the firewall settings and accidentally disabled port 22... It sucked when I did that

  • source
  • [+] 15 points 3 years ago* (8 children)
  • [–] 27 points 3 years ago (7 children)

    I bet you don't simply send random commands to the probe. There are likely a dozen of people who need to approve literally every keystroke.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 15 points 3 years ago (3 children)

    This. And even then there should be procedures in place to essentially make it impossible to send the wrong inputs.

    It's like when an intern accidentally drops the production database. It's not the interns fault for sending the wrong command. It's the managements fault for not restricting access in the first place.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 3 years ago (2 children)

    This. This. I used to work on safety control systems for heavy industrial applications and it's this. Once the system is running any changes at all went through a whole chain of people. When the change was being implemented I had my supervisor and their manager checking every line over my shoulder before we wrote it. Then test. Then lock it down with a digital signature.

    It's not at all like in college/university where you're making changes to your code over and over. Well it is in simulations but that's long before you deploy it. By the end everyone involved should be able to say exactly what every line of code is going to do. This isn't an intern fucking up, the whole team did, and whomever the buck stops with at the top is responsible.

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (2 replies)
  • load more comments (1 reply)
  • Looks like someone removed the ssh keys

  • source
  • [–] 15 points 3 years ago

    There's no going into the office to fix this one...

  • source
  • [–] 11 points 3 years ago

    Patching recent ssh vulnerabilities I see

  • source
  • [–] 10 points 3 years ago
    [–] 10 points 3 years ago

    Tfw you conf t and shut a management port down on accident and don't have a backup console connection

  • source
  • [–] 8 points 3 years ago
    ssh root@vps
    [commands]
    sudo shutdown now
    

    FUC-

  • source
  • [–] 8 points 3 years ago
    [–] 7 points 3 years ago

    Have you tried turning it off and on again?

  • source
  • [+] 7 points 3 years ago* (last edited 3 years ago)
    [–] 7 points 3 years ago

    No biggie just get someone to mount the files system and edit the ssh file 😌

  • source
  • [–] 6 points 3 years ago

    iptables -P INPUT DROP

  • source
  • [–] 6 points 3 years ago

    Must have been an intern.

  • source
  • [–] 5 points 3 years ago (3 children)

    Awww, what a shame though. This probe was doing some really cool stuff, it's kinda iconic in my head.

  • source
  • hideshow 3 child comments
  • [–] 24 points 3 years ago

    It should be ok. It's due to self-reset its orientation on October 15, they put measures in place for if they accidentally lost contact.

    I would still be besides myself if I had made that error though.

  • source
  • parent
  • [–] [S] 7 points 3 years ago* (last edited 3 years ago) (1 child)

    Yeah all jokes aside this is a actually pretty big loss for the scientific community. Assuming it's completely unrecoverable. We blew our chance to actually measure the conditions in interstellar space and see if it lines up with our theories, and another probe is not only not planned for the foreseeable future by any space agency, it will also take decades to get to where Voyager 2 is now.

    Edit: Nevermind, see the other comment. It's likely not permanently lost!

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 3 years ago

    Wow, I just read the wiki. It has a 64 Megabyte tape storage, so after it realigns the antenna they can receive the data they've missed. Pretty state of the art for 1977. I wonder how they shielded it from radiation. The fuel source of the reactor lasts probably until 2026. After that, it'll travel as a brick, most likely long after humans rm -rf'd

  • source
  • load more comments
    view more: next ›