wolstech
-
Posts
17,066 -
Joined
-
Last visited
-
Days Won
618
Everything posted by wolstech
-
Dd you make sure to reassign the database user to the database? Also make sure the database user h the right password.
-
The user must be deleted and recreated, not just get a password change. After you recreate it, make sure you assign it to the database again too.
-
I've not had any issues installing something using InnoDB then converting it's DB afterwards. I'm sure applications that won't work like this do exist, but they seem to be rather rare. For most, it's more because many programs have install scripts are just coded to import tables that are defined using it...the tables themselves don't care what format they are in, and the program using them is usually none the wiser if you change the engine, provided the schema stays the same. -
Topics older than a certain date "fall off the bottom of the list" (they become hidden). You can still get to them by finding them through search though. Also, post counts don't update immediately, and in some forums, posts don't count at all, so your count may not always be a perfect reflection of your posts.
-
Please change your cPanel password, then log out and in again. After that, check that PhpMyAdmin works and that all your databases and their tables (especially InnoDB tables) are present. After that, go through your database users, delete and recreate them. Use the same password as last time (check in your software's config file for it if you don't know it). Make sure to reassign the users to their databases as well.
-
If the backup was created after the recent crash, the InnoDB tables in your database will be missing from your backup. A lot of them were lost in the recent crash (again). Not sure what the odds of us having a backup are, so I'll escalate this for you. Note though that we don't make backups for user data regularly, we may not have anything to restore. Routine backups of databases should be made through cPanel or PhpMyAdmin, and it is the user's responsibility to make them. Once you get this fixed, I would recommend converting the database tables to MyISAM so this won't happen again.
-
[Solved] Roundcube Webmail Not Connecting To Database
wolstech replied to qsgt's topic in Escalated Requests
The roundcube on cPanel is indeed broken. Escalating. -
Working for me now too. If you still see the error, please clear your cache.
-
My Website Is Not Connecting With Mysql Database
wolstech replied to rahuld147's topic in Customer Service
You need to use a backup from before the incident. -
This support request is being escalated to our root admin.
-
You're blocked by the firewall. Escalating so you can be unblocked.
-
Please check your email.
-
My Website Is Not Connecting With Mysql Database
wolstech replied to rahuld147's topic in Customer Service
InnoDB is broken again. You need to create a new database with a different name. Try restoring a backup into that database and see if it works. -
[Solved] Error Establishing A Database Connection
wolstech replied to sofija's topic in Customer Service
MySQL went corrupt. Change your cPanel password, then log out and in again. After that, delete the users for your databases, recreate them (use the same password as before, find it in your program's config file if you don't know it), and reassign them to your databases. Finally, go into PhpMyAdmin and verify that all of your databases have all their tables and that they're accessible (especially ones with an Engine of InnoDB) -
MySQL's user data went corrupt. Change your cPanel password, then log out and in again. After that, delete the users for your databases, recreate them (use the same password as before, find it in your program's config file if you don't know it), and reassign them to your databases. Finally, go into PhpMyAdmin and verify that all of your databases have all their tables and that they're accessible (especially ones with an Engine of InnoDB)
-
[Solved] Error Establishing A Database Connection
wolstech replied to NeiroNext's topic in Customer Service
MySQL's user data went corrupt. Change your cPanel password, then log out and in again. After that, delete the users for your databases, recreate them (use the same password as before, find it in your program's config file if you don't know it), and reassign them to your databases. Finally, go into PhpMyAdmin and verify that all of your databases have all their tables and that they're accessible (especially ones with an Engine of InnoDB) -
That version is only available on Johnny. I'm not sure if Stevie will ever be updated. He was supposed to be updated at one point, but then we decided to get a new server... We are planning to put (I think) 5.6 on the new server, but I don't know when that server will go live.
-
What's your username? I can email a new password to the address on your account so you can log in.
-
My Website Is Not Connecting With Mysql Database
wolstech replied to rahuld147's topic in Customer Service
Delete the user mrres then recreate it. Make sure to use the same password as last time (find it in the config file for your software), and reassign it to the database. -
Change your cPanel password (make sure to check "Synchronize MySQL password"), then log out and in. Once you do that, check PHPMyAdmin to verify that your databases are there, have all their tables in them, and that you can view the data. You also need to delete and recreate all your users, then reassign them all again.
-
Don't know. Also, the symptoms don't necessarily mean the same failure as last time. We'll need to wait until Krydos says something to find out the cause of the issue and whether we need to do anything beyond the database users and changing our password to get our sites working again. EDIT: Databases are showing in PhpMyAdmin...but all the InnoDB tables are missing...
-
This currently looks like the major incident from 2 years ago recurring. You'll need to change your cPanel password then log out and in to fix PHPMyAdmin. Your database users will need to be deleted and recreated, then reassigned to the databases. The databases themselves are likely all invisible, check in PhpMyAdmin to see if they're there. If not, wait until there's an official announcement on this incident to find out what needs to be done fix this.
-
Downtime like this is rare. MySQL issues usually fix themselves within a minute or two. Most of the time, users never even notice anything had happened other than some slowness or an error or two. The only major incident I've been here for was the InnoDB crash two years ago. All the incidents I've been here for (that didn't fix themselves) were just a day or two of downtime, usually a result of an abusive user or the server hard disk being full.
-
I do not. Haven't heard from him in several days. Normally I at least see him responding to abuse reports by email...not even that recently. He's probably extremely busy. The odd part is that it usually restarts itself when it fails. Something is probably broken since it didn't...
-
We don't provide access to WHM. And as marko said, MySQL is down. Your solution is to wait unfortunately. There's nothing you (or even I) can do to fix it. It has to be fixed by krydos.
