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

[HC_Official]

I did notice that these incidents .... some where 7 days apart ..... almost like pattern of something happening periodically

[BIGNEWY]

I did notice that these incidents .... some where 7 days apart ..... almost like pattern of something happening periodically

 

interesting will mention it to the team

[LazyBoot]

We (hoggit) just had all our servers drop off the list at more or less the same time

2019-10-31 20:03:56.506 ERROR   NET: HTTP request dcs:checksession failed with error 28: Timeout was reached
2019-10-31 20:03:56.506 ERROR   NET: Session check failed: 503
2019-10-31 20:04:06.505 ERROR   NET: HTTP request dcs:server:update failed with error 28: Timeout was reached
2019-10-31 20:04:06.780 ERROR   NET: Server update temporarily failed. Will try again later.

[HC_Official]

yep same here, both servers did it pretty much at same time , looks like a SNAFU at ED side ?

 

2019-10-31 19:02:45.580 ERROR NET: HTTP request dcs:server:update failed with error 28: Timeout was reached

2019-10-31 19:02:45.587 ERROR NET: Server update temporarily failed. Will try again later.

 

note BST / GMT time diff

 

 

someone trip over a plug in ED office ?

Edited October 31, 2019 by HC_Official

[HC_Official]

any idea why this happened last night ?

[HC_Official]

it is that time of the week again folks

 

 

2019-11-04 22:42:09.924 ERROR NET: HTTP request dcs:checksession failed with error 28: Timeout was reached

2019-11-04 22:42:09.924 ERROR NET: Session check failed: 503

2019-11-04 22:42:39.906 ERROR NET: HTTP request dcs:server:update failed with error 28: Timeout was reached

2019-11-04 22:42:39.922 ERROR NET: Server update temporarily failed. Will try again later.

 

 

this time both servers doing it

[Mustang]

104th server has just done the same, it's up but gone from the list.

[BIGNEWY]

104th server has just done the same, it's up but gone from the list.

 

Thanks Mustang.

 

It is worth noting the master server went down briefly yesterday.

 

We are still investigating the server drop out, as soon as I get some feedback from the team I will pass it on.

[HC_Official]

2019-11-08 09:49:50.447 ERROR NET: HTTP request dcs:checksession failed with error 28: Timeout was reached

2019-11-08 09:49:50.447 ERROR NET: Session check failed: 503

 

 

it is happening again ... on both look slike ED master server has pooped itself ... again

Edited November 8, 2019 by HC_Official

[HC_Official]

anyone else got this ?

[BIGNEWY]

2019-11-08 09:49:50.447 ERROR NET: HTTP request dcs:checksession failed with error 28: Timeout was reached

2019-11-08 09:49:50.447 ERROR NET: Session check failed: 503

 

 

it is happening again ... on both look slike ED master server has pooped itself ... again

 

Team maybe making some tweaks and changes while investigating the drop outs.

 

As soon as I have an update from the team I will pass it on.

 

thank you

[HC_Official]

This is happening again since yesterdays patch ..... but there are NO errors in the dcs.log

[HC_Official]

Ok checked server list .... not a lot of players and not a lot of servers being displayed

 

 

Edited November 14, 2019 by HC_Official

[HC_Official]

checked server log got this message when IP connection attempt (which failed)

2019-11-14 22:52:45.167 INFO NET: spawning client[2]

2019-11-14 22:52:45.191 WARNING NET: Max message size exceeded!

2019-11-14 22:52:45.191 ERROR NET: Failed assert `capped_sz == sz` at Projects\AsyncNet\src\DsbNet\DsbServer.cpp:1092

2019-11-14 22:52:45.191 ERROR NET: Message 37121 was truncated from 66321 bytes

Edited November 14, 2019 by HC_Official

[Catweedle]

After a couple of tries I also cannot find the Havoc Company in the server list after several refreshes; it worked a couple of hours ago, though.

[Kang]

Yes, looking for my favourite server:

Not showing up... (23:56:18)

 

At the exact same time, though, I can connect through IP:

On the server just fine. (23:55:15)

[HC_Official]

Havoc Server IP (partial work around as IP connect is also partially broken)

 

 

94.23.215.203:30108

[BIGNEWY]

Hi all,

 

We are investigating.

 

Please note we will have infrastructure maintenance work on Tuesday, November 19, 2019 from 04:00 to 06:00 UTC. All users will not be able to connect to DCS Master server and all account sessions will be reset.

 

This work will help improve the master server, and hopefully the stability of the server list.

 

thank you

[c0ff]

checked server log got this message when IP connection attempt (which failed)

2019-11-14 22:52:45.167 INFO NET: spawning client[2]

2019-11-14 22:52:45.191 WARNING NET: Max message size exceeded!

2019-11-14 22:52:45.191 ERROR NET: Failed assert `capped_sz == sz` at Projects\AsyncNet\src\DsbNet\DsbServer.cpp:1092

2019-11-14 22:52:45.191 ERROR NET: Message 37121 was truncated from 66321 bytes

 

This is a bug with syncing too many craters. Does not affect connection (apart from craters being absent on clients). Fixed internally.

[malcheus]

Havoc Server IP (partial work around as IP connect is also partially broken)

 

 

94.23.215.203:30108

 

When I try to connect I get "server offline".

 

I'm only seeing five servers in the server list :cry:

[HC_Official]

When I try to connect I get "server offline".

 

I'm only seeing five servers in the server list :cry:

 

 

are you running Beta or release version of DCS ?

[BIGNEWY]

Hi all

 

with the work on the master server completed at the beginning of the week we are looking for feedback regarding servers dropping from the list.

 

So far it seems good from the feedback I have already had.

 

Please let me know.

[robgraham]

nope happening still had the same error spitting out on our second server just now until i restarted it newy.

 

As I've said before it is something to do with when a server times out because you then get the Error 28 - 503 error.

503 is typically a Webserver/HTTP error code for SERVER ERROR.

 

It's basically like it's going 'Hey I don't KNOW you, I'm not going to talk to you anymore'.. And it can't be as we've all pointed out a actual 'routing' issue because we can have servers on the exact same machine working fine, and others not.

Edited November 22, 2019 by robgraham

[BIGNEWY]

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

[robgraham]

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've given them before but ok i'll wait for it to happen which might not be long it seems to be doing it on and off atm (i've just been restarting the server instances tongiht though because I've been testing another bug) though we've given you literally the ONLY lines that the dcs.log file spits out that are not the same as a normal log and we've all done so again and again Newy, the exact same set that we've all posted for the last several weeks across 8 pages.

 

the lines haven't changed it's always this set the date/time just changes

 

ERROR   NET: HTTP request dcs:server:update failed with error 28: Timeout was reached
ERROR   NET: Server update temporarily failed. Will try again later.
ERROR   NET: Session check failed: 503

 

and again if it was a ROUTING issue we should see it on all server instances, at the same time as I an others have pointed out we are not seeing this, we can have multiple instances on the same machine, using the same network and out of those 1 server might be missing from the list and spitting out the above errors, or 3 out of 4 might be doing it.

 

At which point the only method to fix it is to Restart that server instance, at that point it will instantly show up in the list again, even if said error happened like 1 second before in the logs.

 

If every server instance did it all at the same time I would happily agree with you that it could be a 'network' issue, but that isn't the symptom.

 

And this is really why DCS especailly in -server mode needs to basically make new log's each time it's started rather then just dcs.log if it spat out a new log each time we wouldn't run the risk of overwriting an error log for when you request it, a lot of us just want to get our servers back up and displaying correctly so we restart, not thinking about getting the log and renaming it.. and it doesn't always save a dcs.old log either.

Edited November 22, 2019 by robgraham