Server cannot be restarted after crash - v2.5.6.43503

[Flighter]

Hi ppl.

After latest update, we have the following behavior/issue :

 

 

• The server crashes.
  
• Our automated restart script restarts it.
  
• The server gets stuck with the error message "Someone has logged in with your account on a different machine". This is a modal window (the user has to press OK to continue) so we are done.
  

 

The username used for the server is not used anywhere else.

The restart delay after the detection of the crashed server is set to 60 seconds.

 

Any advice from ED ?

 

At the moment I have modified the crash restart script to :

 

• start a new instance
  
• wait 60 second then kill it
  
• start the server again.
  

No idea yet if this works.

Overall 2.5.6 has been a problematic update with relentless server crashes (we had that before) but newly developed restart issues. Also much much longer loading times and way higher memory usage. And the gameplay took a big FPS blow at least in VR.

Hope it gets better soon.

 

 

[BIGNEWY]

Hi please ensure you on have two logins active for the same account.

 

If you are running a server and playing on the same account a third login would kick another.

 

How many servers are you running?

[Flighter]

Hi Bignewy

Thanks for responding.

 

 

I have two servers but each one uses it's own account name/login.

I use my main account (third one) for playing.

 

 

Cheers.

[BIGNEWY]

Thanks the team are looking into it,

 

it could be related to an IP change.

[viperhill]

Hello, since the new version 5.5.6 our server is simply invisible in the selection of servers in the game. if we try to connect directly with the ip address locally we have a message server offlines

[Flighter]

Thanks the team are looking into it,

 

it could be related to an IP change.

 

Thanks BIG.

 

The server is on static IP.

Just for the benefit of other server owners, I have temporarily worked around the issue by :

- Removing the Stennis from mission (no more memory running out)

- Starting then killing the process then restarting again.

 

I wait for the update since the scoreboard and player IDs are bugged.

 

Thanks again.

[Zarma]

I think the memory leak is the cause. With 2.5.6 our dedicated went full RAM and rebooted. Had to restart DCS Dedicated Server manually. Wait for next fix today or tomorrow.