New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fairly recent installation, no aircraft visible, checking and found MySQL is stopped #408
Comments
I think it would be far better to find why MariaDB exit ;) |
Agreed, but this seems rather generic of a db corruption, which could be a matter of a power interruption, and likely not application related. (I could be wrong though!) Here is the head of error.log for mysql. (I figure the first error is likely most important).
-- the ffffff just repeats as it's a page dump. then, following the page dump:
|
True, this seems in really bad state... |
Installation: Pi3, Raspibian Stretch, separate Pi from FlightAware receiver (using PiAware 3.5.3)
When I went to the IP of FAM, it loads but shows 0 aircraft. I thought that was odd, so I started poking around. Rebooted. Noticed this repeating pattern in /var/log/daemon.log:
Starting MariaDB database server...
mariadb.service: Main process exited, code=killed, status=6/ABRT
Looking in var/log/mysql, I see a 7GB error.log file where this thing has been wedged for a few days and is generating tons of error output.
It's probably easier to reinstall a blank database than recover, and the installation is new enough that the value of the historical info is not really significant.
What's the best approach to take to lay down a fresh db and get FAM up and running again?
The text was updated successfully, but these errors were encountered: