1. Welcome to the Starbound support forums. Please check the support FAQs before posting: http://playstarbound.com/support

Bug/Issue Corrupted ship on single player and can't connect to Starbound dedicated server.

Discussion in 'Starbound Support' started by naamapokemon, Sep 10, 2016.

  1. naamapokemon

    naamapokemon Yeah, You!

    Hello,

    After the new update (gj on that), our dedi server was down. While it was down and our server admin was at work I used my multiplayer character in a single player game.

    With that character I had not gone through the initial hoops on single player I only did them on multiplayer server about a month ago. So in order to access the outpost I had to go to a lush planet and activate portal there. I got to the outpost, talked to a few npcs there and accepted one quest from the penguin bartender.

    At this point server went up on it's own and I tried connecting. I got: "Exception caught in client main-loop (EofException) Failed to read full buffer in readFull, eof reached."

    I asked our server admin to reboot the dedi server as it had helped some people with similar issues. It didn't help.

    Then I went back to single player, but my ship was empty of all the items and it had the hazard blocks between all the upgrade areas.

    Should I use http://community.playstarbound.com/threads/fixing-lost-corrupted-universes-and-player-files.119985/ tutorial to try to fix the issue?

    The log files are in zipped at https://www.dropbox.com/s/ecbqfaxibnb0vs8/storage.zip?dl=1
     
  2. Iris Blanche

    Iris Blanche Pudding Paradox Forum Moderator

    It seems that the error you encountered when joining the server was your shipworld that caused an error. You can try the steps in the tutorial and restore your shipworld (won't work if you started SB too often). A lot of people had their ship resetted with 1.1 but i can't say why. All i can say is that i didn't experience this issue at all. Unfortunately the log files aren't telling much either so it's pretty hard to track down. >w<

    ~ Iris ~
     
    naamapokemon likes this.
  3. naamapokemon

    naamapokemon Yeah, You!

    Thanks a lot for help. The problem was the server version. We assumed(mother of all fails) that server updated itself like it should, but this wasn't the case.

    The error message was misleading to us, as the client didn't actually check, or at least didn't inform of the server-client version mismatch like the game did with the earlier updates.

    Our server admin backed up the storage files and updated the server manually. everything is fine now.

    Thanks again, hard working community helpers.
     

Share This Page