The MySQL errorlog is an important point of reference when administering a MySQL Server. We can grasp much about the state of our MySQL instance by the informational and error messages written out to it by our MySQL daemon. Our monitoring suite is set up to check the mysqld error log file periodically for any new nasties logged and then it alerts us if there’s anything to know about. Recently I was asked to investigate some replication outage alerts a colleague had received overnight. One of the primary directions I took was the error log file. This is where I would expect find any evidence of replication being stopped or crashes etc – I was looking for anything that could fill me in on the causes of replication alerts. When I ran the command to tail the log I was shocked to see the log was totally empty. Read the rest of this entry . . .
MySQL Administrator's Bible by Sheeri K. Cabral
Oracle RAC Workload Management whitepaper by Alex Gorbachev
8 Rules for Designing More Secure Applications with MySQL by Augusto Bott and Nick Westerlund
pythian: RT @FN_Press2: Schooner Information Technology Teams with Pythian to Deliver Advanced Support and High... http://finanznachrichten.de/20
more
DBA, Brookfield Energy
We are very satisfied by the service given to us by Andre and Shakir in support of our recent data quality and reorganization initiative.... more