The database recovery is smoother than my predictions. The daily backup works so I just need to focus on manually loading ~14 hours of data not covered in daily backup into the newly built database. This could be done as FGTracker server saves a copy of messages from each FGMS, and I do not expect any data loss during this incident.
By taking this opportunity, I built a primary database in Oracle Always Free Resources (VM.Standard.E2.1.Micro shape) located in Osaka, which is unthinkably slow like a Raspberry pi 3. Therefore a replica database is set up for rendering the FGTracker Web GUI, which is *still* in China. FGTracker Web GUI appears to be slow. This is because FGTracker Web GUI is hosted in Osaka (VM.Standard.E2.1.Micro shape - sloooooooooooow), and the GUI reads the replica database in China (high latency >100ms for each query and very limited bandwidth ~100-500KBbs). This is the best I can do with limited resources. Allow me to appeal for resources support again. FGTracker needs a decent server which can host ~50GB (SSD speed) of Postgresql database with at least of 8GB of dedicated ram (2-4GB should be enough if in cloud). Required CPU power should not be that much - something similar to Intel 4th Gen i3 should be good enough. PM me Hazuki in FlightGear forumhttps://forum.flightgear.org if you have any queries or you can donate resources to FGTracker. Fly safe~ Today I have to bring a bad news to the community: the SSD (ADATA) storing the flight data had failed miserably without any failing symptoms before it decided to give up.
This means: 1)Data after 16.10.2025 1400UTC is likely vanished. 2)Data before 1) should have been backed up. However I don't know if the backup works and this definitely needs time to explore and recover. What I will do is: a)Get a new SSD. Hopefully this can be done before 20.10.2025; b)Recover data in 2) from backup. Hopefully this can be finished by 27.10.2025; c)Try to fix the bad SSD; and along with c), d)Try to recover data from log file. This needs to write a program to extract data within the log file, and I am not sure if I can success on this. I expect job d) will be finished (if success)/I will give up job c) and d) by the end of October 2025. I.e. FGTracker will resume in Nov 2025, with unknown data recovered (could be from 0% to 100%). I will update this post once I have news for ya. Further to my post in Flightgear forum on 2023.06.15, with the release of XOOPS 2.5.11, I finally have the chance to move the site to server with PHP 8.2. The change from PHP 7 to PHP 8 is so enormous that I have to install XOOPS from scratch and migrate data from old instance to new instance manually, which took me 3 man days. Please report to me (Hazuki) in Flightgear forum if you found somewhere not working. FGTracker is still hosted in China, where I wish to move away from. But since no donations available, FGTracker will still be in China for a while. As neither me or anyone else are actively developing FGTracker, do not expect significant change in GUI in forseeable future. I will only provide minimum maintenance and try to maintain FGTracker online (not more than this) should I have time. As always, volunteer developer is welcome to make FGTracker modern. You may retrieve almost all data in FGTracker from the FlightGear Tracker API. In addition, Rules and Obligations when using FGTracker (fgtracker.us.to) is being reviewed and the following sub-sections are added: Please check "Rules and Obligations when using FGTracker (fgtracker.us.to)" before using FGTracker. As usual, thanks for flying with FGTracker. Freenon's .ml domain is gone and fgtracker.ml is offline since 2023-07-23. During the offline period I have searched all possibilities to obtain a sustainable (i.e. free forever) TLD but in vain. Since FGTracker is offline for a prolonged period, I decided to ask freedns.afraid.org for obtaining a subdomain. fgtracker.us.to is FGtracker's new home for forseeable future. The address does not look cool, but we have to live with this. Time is required for FGMS maintainers to propagate the new FGTracker address. Their server will not be tracked by FGTracker until they have changed their configurtation. Always check mpserverstatus v2 for latest tracking information. I was informed by Google that "low level security" SMTP service will not be available to me on or after 2022.05.30. This will affect the callsign registration as I cannot send you the verification email to your email address. If you do not receive the verification email after callsign registration, please PM me (Hazuki) in the flightgear forum. I will activate your callsign manually. |