Re: [Flightgear-devel] FlightGear Tracker crash
If we get to for example 50 mpservers, then there's gonna be a lot of admin involved for every "change" On Fri, May 21, 2010 at 8:34 AM, Anders Gidenstam wrote: > On Fri, 21 May 2010, Peter Morgan wrote: > > > a restart is also required after a DNS change of a server, or a new one > etc. > > > > Is there a way to "reset" an mpserver remotely? > > > > eg reloading config every hour or remote telnet command ? > > No and yes. :) > There is no way built into fgms (and adding one would require thinking > about the security implications) but I would guess that most fgms > administrators have remote access to the box that runs the server. > > IIRC fgms can almost but not quite reload the configuration file when > receiving a hangup (SIG_HUP) signal. Fixing that and/or adding the > function to re-resolve the relay names each day (or so) could be useful. > > > Something related: 06 changed IP address last weekend so servers that > haven't been restarted since need to be restarted to relay correctly. > > > Cheers, > > Anders > -- > --- > Anders Gidenstam > WWW: http://www.gidenstam.org/FlightGear/ > > > -- > > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Tracker crash
On Fri, 21 May 2010, Peter Morgan wrote: > a restart is also required after a DNS change of a server, or a new one etc. > > Is there a way to "reset" an mpserver remotely? > > eg reloading config every hour or remote telnet command ? No and yes. :) There is no way built into fgms (and adding one would require thinking about the security implications) but I would guess that most fgms administrators have remote access to the box that runs the server. IIRC fgms can almost but not quite reload the configuration file when receiving a hangup (SIG_HUP) signal. Fixing that and/or adding the function to re-resolve the relay names each day (or so) could be useful. Something related: 06 changed IP address last weekend so servers that haven't been restarted since need to be restarted to relay correctly. Cheers, Anders -- --- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Tracker crash
a restart is also required after a DNS change of a server, or a new one etc. Is there a way to "reset" an mpserver remotely? eg reloading config every hour or remote telnet command ? pete On Fri, May 14, 2010 at 9:08 AM, Gabor Toth wrote: > Hi, > > it seems, not all the MP servers are connected to the tracker currently: > > # sh /root/list_mpservers_connected.sh > mpserver02.flightgear.org > mpserver07.flightgear.org > mpserver09.flightgear.org > mpserver10.flightgear.org > mpserver12.flightgear.org > mpserver13.flightgear.org > > Maybe some of them haven't been restarted after the crash of tracker. > Please restart them. > > Thanx, > Gabor > > On Wednesday 2010 May 05 21:42:08 Gabor Toth wrote: > > Dear All, > > > > unfortunately, there was a double disk failure on Monday in the tracker > > server causing the server to crash. After replacing the disks I've been > > working to restore commercial services first, and today I could finally > > restore flightgear tracker as well. > > > > Sorry for the inconveniences, > > Regards, > > Gabor > > > > > --- > > --- ___ > > Flightgear-devel mailing list > > Flightgear-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > > > -- > > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Tracker crash
Hi, it seems, not all the MP servers are connected to the tracker currently: # sh /root/list_mpservers_connected.sh mpserver02.flightgear.org mpserver07.flightgear.org mpserver09.flightgear.org mpserver10.flightgear.org mpserver12.flightgear.org mpserver13.flightgear.org Maybe some of them haven't been restarted after the crash of tracker. Please restart them. Thanx, Gabor On Wednesday 2010 May 05 21:42:08 Gabor Toth wrote: > Dear All, > > unfortunately, there was a double disk failure on Monday in the tracker > server causing the server to crash. After replacing the disks I've been > working to restore commercial services first, and today I could finally > restore flightgear tracker as well. > > Sorry for the inconveniences, > Regards, > Gabor > > --- > --- ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
