Just thought I would come back to this thread and post a few more things. What I did above fixed a lot of my issues by mysql would still crash from time to time. It wasn't a big deal, because i had a script that ran and checked if it was down and would restart it. It only happened once or twice a month probably. Anyway, it's still probably not a good idea to have mysql server crash even if rarely.
Recently, I found some time to look into securing a few things on the server and I came across the prefork and MaxRequestWorkers setting. I thought I would post a link to these two articles for anyone else experiencing memory issues and crashes.
If you leave your web server setup with the defaults, it's probably no good. I found that given the average memory used by the httpd process, I should only allow about 20-30 httpd processes, anything more and my server starts to thrash. I probably should have learned about this sooner. Anyway, since configuring this (based on the website articles pasted below), I haven't had my mysql server or web server crash since.
https://fuscata.com/kb/set-maxclients-apache-prefork
https://www.maketecheasier.com/optimizin...he-part-1/
Hope others will find this useful.
Recently, I found some time to look into securing a few things on the server and I came across the prefork and MaxRequestWorkers setting. I thought I would post a link to these two articles for anyone else experiencing memory issues and crashes.
If you leave your web server setup with the defaults, it's probably no good. I found that given the average memory used by the httpd process, I should only allow about 20-30 httpd processes, anything more and my server starts to thrash. I probably should have learned about this sooner. Anyway, since configuring this (based on the website articles pasted below), I haven't had my mysql server or web server crash since.
https://fuscata.com/kb/set-maxclients-apache-prefork
https://www.maketecheasier.com/optimizin...he-part-1/
Hope others will find this useful.
