Menu
News topics
RSS Feed

« 1 ... 3 4 5 (6) 7 »
Posted by Hazuki on 2012/6/9 12:23:48 (727 reads)

The Tracker DB cannot be reached for some resaon. I PMed ahven and asked him to check what's going on with his server. Please be patient until the problem is fixed.

 

EDIT: 2012-06-16 18:46+08 Looks like the upstream server is not recoverable. I am now contacting the owner of mpserverXX to re-direct the data traffic to a new server. This site will no longer update until the traffic has been re-directed by the owner of mpserverXX.

 

EDIT: 2012-06-21 21:51+08 Now the tracker only tracks fgfs connecting to this site (mpserver15.flightgear.org). Please change the setting accordingly if you want your flights be tracked. (see below)

Posted by Hazuki on 2012/4/29 12:00:00 (609 reads)

Today I have replaced the DB storage from HDD to SSD and the result was impressive. A page which needed 3 minute to generate now it only takes less than 30 sec. Some over 80% of time is saved.

 

BTW, in these few days the tracker trackes mpserver01's flights. In case you can't get you flight tracked, mpserver08 might still be your (only) friend.

Posted by Hazuki on 2012/4/9 8:31:14 (703 reads)

Your flights not getting tracked? Connect to mpserver08.flightgear.org might help!

Posted by Hazuki on 2012/1/9 7:20:00 (687 reads)

When the tracker site seems slow (should be always though XD), please access it a moment later (e.g. 10 min). I don't think you'll expect a 5 year old desktop will run fast with a 28GB Database right?

 

Do not refresh the page again, again and again! Doing so will only boost up the load of the server.

 

The main problem is slow I/O of Hard disk.I am seeking a idle SSD at my end but apperentely no luck. When it comes, the site will revive.

Posted by Hazuki on 2011/12/13 2:50:00 (748 reads)

Since 2011-12-13 04:53+08 the Tracker site (http://fgtracker.ahven.eu/flightgear/) cannot communicate with the Master DB (which is the first guy receiving the Data from MP network). We are investigating the issue but probably DDos is encountered.

 

EDIT 16:36+08: A connection flood is confirmed and the flood is now under control. We expect that the service resumes normal now.