Stevie Mysql Fixed

[HelioHost]

Mysql on Stevie will no longer crash as we mentioned in our last news post http://www.helionet.org/index/topic/21518-stevie-mysql/

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.

The fix has now been implemented on the Stevie server. Let us know if you need help restoring access to your databases.

[wolstech]

@domotica: Your post has been split and moved to Escalated Requests: http://www.helionet.org/index/topic/22279-invisible-database/

[Krydos]

@topgeardavid Your post has been moved to http://www.helionet.org/index/topic/22346-solved-invisible-databases/

[zai2728]

now i can't set ip for remote MSQL