Day 9: MariaDB Troubleshooting | Kodekloud Engineer | check Description for troubleshooting steps
#day9 of 100 days of DevOps
one task a day for 100 days to sharpen our devops skills.
KodeKloud Engineer Website : https://engineer.kodekloud.com/signup...
=================================================
Step 1 : login to DB server from jump host. From here -- https://kodekloudhub.github.io/kodekl... search for peter/db server to get login details of db server
step 2 : Check status of mariadb with this command --- sudo systemctl status mariadb
Check logs to get some idea for the failure
(for me it is due to different owner for mariadb folder . Mariadb is running on mysql)
use --- journalctl -xe | grep mariadb to check yours
step 3: check /var/log/mariadb/mariadb.log for detailed log using cat.
step 4: run cd /var/run ; ls -la and w.r.to mariadb folder make sure both username and group name musst be mysql if not change it .
(This is the error in my case )
run --- chown mysql:mysql mariadb
step 5: now run --- sudo systemctl restart mariadb ( you will get no output)
step 6: check status by using -- sudo systemctl status mariadb ( It should be active and running state)
That's it. Congratulations🎉🎉, you have successfully completed troubleshooting of mariadb down .
Extremely sorry for the inconvenience again...
====================================
Some other helpful commands for troubleshooting
df -h --To check disk space
free -m / top -- To check for memory space
ls -ld /var/lib/mysql -- To check permission issues
sudo netstat -tulnp | grep 3306
sudo ufw status
To check port issues.