I have noticed twice now in the last 24 hours, my server is not available on the in-game server list but it is up and running and appears to be ready for logins. It's not even available in the in-game list for me even though it is on the same LAN. I also notice at the same time the main Discovery RP server is not available.
When I shutdown the server and restart then it becomes available.
We are having server stability issues at the moment. For the time being we have decided to leave it down rather than restart it every fifteen minutes. The one person who knows the server better than any of us is currently traveling in New Zealand without his lap top. As soon as he has access again he will take a look at the problem.
This is an interesting issue. Previously we believed it to be an issue specific to DiscoveryGC but now I'm confused. DiscoveryGC's server -- and to my knowledge, every default-setup discovery server -- does not use the GUN list server so it's not an issue there.
We will continue trying to figure out what the hell is going on here and will let you know when we have something. For now though all we can do is hope something we do works.
What DOES Discovery utilize for listing servers? Is it just all direct connections from the dsupdate file, which cuts a list server completely out of the equation?
And what's really odd is that flserver.de is showing all the Discovery servers going down, yet the server software all seems to be running just fine for everyone. Which leads me to believe that something is just triggering the servers to stop broadcasting their presence, and/or stop responding to network traffic totally...
Is it possible that something unrelated to Discovery, and embedded in the core of FLServer could be the culprit? Based on what I know of game servers, there's generally a core loop section to handle all timings and the like, perhaps there's an issue with the way FLServer was coded that's causing this to happen starting at this specific date?
A server does not have to connect to gun.fllistserver.com to be listed on flserver.de. You simply have to add your server to their list and they will query your server to determine status. Not sure of how often they query but it's several times an hour. The reason flserver.de is not showing servers is because they are not responding. When this happens, my server is up and running and appears to be waiting for logins. But it's not accepting logins, or responding to flserver.de queries. It doesn't even broadcast itself to my LAN because I can't see it on my client machine even though the client is on the same lan as the server.
I find it difficult to believe that something has gone wrong with flhook or flserver because there are a lot of servers running the updated software and it's just now happening. Then again when it happens I do see Paulus's Disco Portal which is running 4.86. Could this possibly be a DDOS attack?
(04-05-2014, 06:10 PM)KellyR Wrote: Could this possibly be a DDOS attack?
Kelly
I have some pretty extensive anti-DDoS protection in place on the connection I use for my server, and I checked with my provider at the time to see if anything was amiss, everything seemed fine.