Author Topic: Gameservers stop being listed on masterserver after network issues  (Read 1520 times)

tomreyn

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
and by the way: the engineers just said goodbey to the masterserver while still running. but i can't connect to them via ip, so they are defininitly dead. i will change the start script to run with the verbose command

Right, there is a partial network connectivity outage today at Hetzner, the company running the data center where the server hosting our services is located.

When the masterserver happens to be unavailable temporarily due to network connectivity issues or due to issues on the server itself, gameservers stop being listed on it. This is somewhat logical, since if this happens the masterserver will not receive the 'alive ping' from the server for a while, consider it to have timed out, and remove it off the server list. When the server then keeps sending 'alive pings' again it is no longer in the list of active servers and those are thus discarded. The proper solution to this issue is probably that the gameserver should retry to get listed if the masterserver tells it that its alive pings are not OK.

Generally we should consider using session IDs.
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

treba

  • Guest
Re: Gameservers stop being listed on masterserver after network issues
« Reply #1 on: 14 February 2012, 15:46:17 »
ah well, this explains why both, the masterserver and the engineer, were not reachable at the same time. didn't know you also use a hetzner server

 

anything