Jump to content

A player can not connect after server crash- "Internal server Error"


halldinen

Recommended Posts

Hi!

As the title says, a player ("Paddsky", index 18) fails to connect to my server after my system crashed. The system crash was related to hardware failure.

I, ("Halldinen", index 1), can still connect to my server. Another player ("Thomas Snow", index 19) can also connect just fine. Thomas Snow was NOT connected to our server at the time of the crash.

 

There are in total four players using the server.

 

I was hoping that we could recieve some help, or advice on how to fix the server. I do not believe that the server, or client can be blamed for this problem. We are all also aware the meaning of Early Access and that losing a galaxy is a possibility due to Beta.

However we would very much love to return to our galaxy, rather than restart and lose all those hours of blood, sweat and tears  ;D .

 

Some background as to what happened:

  • I, Halldinen  (The host) connected to my own dedicated server, hosted on the same computer used for gaming.
    At the time, only Paddsky was online.
  • After roughly one minute the Host computer crashed. This most likely was caused by a defective graphics card (overheat etc). There have been serveral of these crashes leading up to this one, most likely this was the crash which finally caused corruption in our galaxy.
  • I was forced to do a hard reset on the host PC
  • I started the Host PC, and avorion server again.
  • Player Paddsky tries to connect, but is unable. Player recieves an error popup when trying to connect (Log snippet: http://pastebin.com/GJ9UsWdJ)
  • The connection attempt is logged on the server. This is the first log after the "Fatal" crash: http://pastebin.com/arLHafcu
  • I, the host, connects to the server with success.
  • Another player connects, also with success. Player Thomas Snow

 

Server and clients are running in Stable branch.

 

There was two crashes on the same evening prior to the final one which caused the problems.

Here is the final log before the system crash which caused this to happen: http://pastebin.com/ekLzGnNT

 

For completeness, here are the log from the first crash that evening. This did not cause any apparent corruption: http://pastebin.com/Pc6fmdpy

The log from the first crash is rather large as it covers almost 24 hours of up-time. I did cut some parts of it just to fit within the free limit on Pastebin.

 

The log directly after the first crash. There were no aparent problems with the server at this point, however the crash at the end of this log is where the problem occured: http://pastebin.com/W55s0HEV

 

And again, as linked earlier above, this is the log which shows the problem where player Paddsky, index 18 fails to connect : http://pastebin.com/arLHafcu

 

 

And hardware specs for server:

Intel i5 4570K cpu,

16 gb DDR3 ram,

GTX 770 2gb,

Windows 10 Home OS.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...