[FEEDBACK]Servers stop appearing on the 'master' list despite being up.

[HC_Official]

Thanks robgraham

 

we would like to see your dcs.log from the server after it happens.

 

Ofcourse there is always the possibility that local or wide network could be playing a role here as well.

 

It may be worth doing a tracert to the master server when you notice problems.

 

thanks

 

 

I have seen exactly what Rob is describing many many many times

one server = 503 no reporting, another server on box hardware = reporting fine (which means it sure aint network related)

 

it is one of two things as far as I can tell

 

1. Master server is rejecting the single server instance "I am ALIVE" data packet

2. The single server instance is NOT sending the "I am ALIVE" data packet to the master server in the correct "format" or not sending it at all

 

@BIGNEWY , is there a debug build of the server exe that logs more output info to the log that we could try for you guys, to give you more usefull data ?

[Dutch Baron]

Hi all,

 

We are experiencing the same issues.

Not visible on MP list after a while, but can 'connect by ip' and join the server just fine.

 

Our logs show these:

 

NET: HTTP request dcs:server?ACTION=del&ID=2235504 failed with error 28: Timeout was reached

INFO NET: server has stopped

NET: HTTP request dcs:checksession failed with error 28: Timeout was reached

ERROR NET: Session check failed: 503

NET: HTTP request dcs:server:update failed with error 28: Timeout was reached

ERROR NET: Server update temporarily failed. Will try again later.

 

Logs sent to BigNewy.

 

I hope we can find the cause and a solution :)

[robgraham]

This is before I tried something I've been asked to do but is the log Newy Asked for.

 

And newy before you go 'Mods on the server' Please note this:

 

1. This happens even if you have a clean server.

2. This was happening well before I readded LOTATC back into our server.

 

 

I am trying the changes I was asked to in PM and will let you know how it goes.

dcs_503error.zip

[BIGNEWY]

Thanks for the data and feedback I will pass it to the team.

[Flighter]

Thanks for the data and feedback I will pass it to the team.

 

Hi Bigenvy, thanks for your help.

 

 

I can verify the following as of current release (2.5.5.39384) :

- Sever running with presence in the browser.

- Server disappears from browser, players remain connected and playing fine.

- Someone can connect with direct IP connection.

- https://www.digitalcombatsimulator.com is reachable from web browser on server

- The logs contain the "failed with error 28: Timeout was reached" message

- Tracert finds the server (pic attached).

- dcs.exe is terminated and restarted.

- Everything returns to normal.

 

If you need logs let me know.

Has been pretty hard keeping the server(s) listed for several months now. I auto-restart the server executable as soon as all players disconnect, but sometimes they remain busy for many hours and disaster strikes...

 

Cheers.

[robgraham]

Newy,

 

Looking at the logs atm since I did the changes that c0ff asked me to do it seems to have stabilizsed.

 

Of course as I said on discord I've not had a chance to check files on the server as often as I'd like of late I've been a bit busy due to weather, illness and having to watch for fire alerts due to the first. (43c in spring isn't 'fun')

[BIGNEWY]

Newy,

 

Looking at the logs atm since I did the changes that c0ff asked me to do it seems to have stabilizsed.

 

Of course as I said on discord I've not had a chance to check files on the server as often as I'd like of late I've been a bit busy due to weather, illness and having to watch for fire alerts due to the first. (43c in spring isn't 'fun')

 

Take your time, and stay safe.

 

Feedback when you get time.

 

thank you

[c0ff]

Thanks for everyone for the feedback.

So, the solution is:

 

Add the following lines to the file (create the file if necessary)

Saved Games/DCS[.openbeta]/Config/autoexec.cfg:

net.curl_timeout = 0
net.curl_connecttimeout = 0

 

 

We fixed the timeouts in the internal version, so it will eventually come out to you.

The config file solution works right now.

[McPetterson]

soon we gonna code DCS to make it work guys

[BIGNEWY]

soon we gonna code DCS to make it work guys

 

already included in the latest open beta patch.

 

Signs are good, seems resolved.

 

thanks

[HC_Official]

already included in the latest open beta patch.

 

Signs are good, seems resolved.

 

thanks

 

 

Sadly I would not go as far as agreeing with you just yet ...... yes the servers are not dropping off the list ......

mainly because they are currently crashing a lot before they can stay up long enough to verify that they are not dropping off the list

[BIGNEWY]

Sadly I would not go as far as agreeing with you just yet ...... yes the servers are not dropping off the list ......

mainly because they are currently crashing a lot before they can stay up long enough to verify that they are not dropping off the list

 

Not all servers are seeing the access violation crash, so we have a good pool to get a validation from for server drop issue.

 

Please discuss the access violation crash in another thread, thank you

[TWC_Alamo]

Since making the additions suggested in Post #83, my servers have been rock solid. I hope that statement doesn't jinx me!

 

 

Since that has been added to the update, do we need to remove those statements from the autoexec.cfg?

Edited November 29, 2019 by TWC_Alamo

[c0ff]

Since that has been added to the update, do we need to remove those statements from the autoexec.cfg?

 

Yes.