Working with a client last week I noted in my analysis, “The mysql server was restarted on Thursday and so the [updated] my.cnf settings seems current”. This occurred between starting my analysis on Wednesday and delivering my findings on Friday.
# more /var/lib/mysql/ip-104-238-102-213.secureserver.net.err 160609 17:04:43 [Note] /usr/sbin/mysqld: Normal shutdown
The client however stated they did not restart MySQL and would not do that at 5pm which is still a high usage time of the production system. This is unfortunately not an uncommon finding, that a production system had an outage and that the client did not know about it and did not instigate this.
There are several common causes and the “DevOps” mindset for current production systems has made this worse.
- You have managed hosting and they perform software updates with/without your knowledge. I have for example worked with several Rackspace …