HelioHost Posted August 12, 2015 Posted August 12, 2015 The time has come to fix Mysql on Stevie. For far too long both Johnny and Stevie had broken installations of Mysql that would occasionally crash and restart. Sometimes the crashes would only occur once every twelve hours, or sometimes several crashes would occur back to back. Either way any amount of Mysql downtime is too much. The inconsistency and the randomness of the crashes made this problem very hard to diagnose, but now we have the solution in hand. After careful consideration and extensive testing we developed a fix. That fix was implemented on the Johnny server first, and we are pleased to announce that Johnny hasn't had a single Mysql crash in over two months. Not only has there been no downtime, but we have also re-enabled innodb support on Johnny. Since the fix has worked so well we've decided to go ahead with implementing the fix on Stevie too. The upside is we should now have nearly 100% Mysql uptime to match Stevie's nearly 100% html/php uptime. The downside is that some Mysql databases might become temporarily invisible to their accounts/users. We would like to emphasize that no data whatsoever was lost in the fix on Johnny, and we see no reason why Stevie would be any different. That said, we do recommend (as always) to take backups of your Mysql databases. If you happen to be one of the users that end up with an invisible database you have two options. First, you can delete the invisible database, recreate it, and restore your backup. Otherwise, if you fail to take a backup as we suggest you need only post on the Customer Service subforum http://www.helionet.org/index/forum/45-customer-service/ clearly stating your username, and the names of the affected database(s). An admin will then be able to restore to you visibility of the affected data with no loss of information. Also keep in mind that the data will become invisible to any database users that you may have created, but you can fix this yourself once your database is visible to your root account by deleting, recreating, and reassigning permissions to your database user. If you have any questions about this upcoming upgrade please let us know by asking in our questions subforum located at http://www.helionet.org/index/forum/48-questions/ As always thanks for being a part of the Heliohost community. It's users like you that will keep us going for many years to come. 2
McCozza Posted October 3, 2015 Posted October 3, 2015 So this must explain why I my websites can't connect to the databases shali_wacc, shali_wh and shali_watford. For example 'http://wacc.herts.heliohost.org' website gets this kind of error now and since August, Error The website encountered an unexpected error. Please try again later. Error messagePDOException: SQLSTATE[28000] [1045] Access denied for user 'shali_wacc'@'localhost' (using password: YES) in lock_may_be_available() (line 167 of/home/shali/public_html/wacc/includes/lock.inc).
wolstech Posted October 3, 2015 Posted October 3, 2015 Change the password for database user named shali_wacc, then update your software's config file and it will work again.
Recommended Posts