Isolated MySQL Database Issues

[GatorDHanna]

Dear Customers,

A recent upgrade to MySQL 5.1 has resulted in a limited number of customers experiencing problems connecting to and accessing their SQL databases. The issues are limited to a small number of customers on a small proportion of our servers. A vast majority of HostGator's customers are not at all affected by these upgrades.

Username Truncation Issues:

The upgrade to MySQL 5.1 was supposed to be transparent and trivial from a user perspective, but MySQL 5.1 fixed a bug that resulted in the truncation of MySQL usernames to a maximum of 16 characters, including the required cPanel username and underscore preceding the database name. With these requirements in mind, MySQL usernames should be six or fewer characters.

The difference in usernames has caused customers with MySQL usernames exceeding 16 characters to experience problems connecting to their database.

Solution for Username Truncation Issues:

Customers can fix this issue themselves if they are familiar with the various scripts they are using on their web site. To fix a WordPress installation, for example, please do the following:

1. Login to your cPanel and go to the MySQL page
2. Look at the usernames of any databases that are not working and note that username. The username has already been updated to reflect the character limit.
3. Go into your WordPress installation's wp-config.php file and update the file to reflect the truncated MySQL username.

Most scripts have corresponding configuration files and the process to update the usernames is very similar (for example, Joomla's is called configuration.php). Once the username is updated to reflect what is showing on the MySQL page, it will fix the problem.

If you are unsure of how to do this or uncomfortable doing so, please do not hesitate to contact our support team.

Isolated Database Corruption Issues:

A separate issue that is not directly related to the above issue is also affecting a small number of customers who had corrupt databases before the MySQL upgrade. Customers who had previously corrupt databases will have problems connecting to and using their databases. To rectify these problems, our support team can restore databases from our backups and will do so free of charge.

Contacting Our Support Team:

Both of these issues are easy to rectify quickly and easily. Please contact our support team via email at support@hostgator.com and include your affected domain names and any other relevant details that can help our support team in resolving your issues.

Fixes for these issues only take a few moments and like all of our support operations, are being done 24/7. Our system administrators are prioritizing these issues and getting a large number of fixes done very quickly.

[usaexpor]

my database is toast after the recent upgrade. curiously only my innodb tables were affected. if they were stored as myisam than they were fine. i have an open ticket for this issue if someone could help that would be great!

Ticket ID: LBG-4296931

[Pazeh]

with the simple logic of longer username = securer username, wonder why they decided to truncate it to 16 characters!!

[sysdev]

My database is toast as well. Ticket LHW-4297322.

We received absolutely ZERO notification via email that this upgrade was going to happen.

curiously only my innodb tables were affected. if they were stored as myisam than they were fine. i have an open ticket for this issue if someone could help that would be great!

Same thing here. PHPMyAdmin shows that there are 81 tables there for my database, but only 13 MYISAM tables are showing up.

[sysdev]

Was the "mysql_upgrade" command performed against the databases after the database server was upgraded?

See the following MySQL documentation:
http://dev.mysql.com/doc/refman/5.1/...l-upgrade.html

Let it be noted as well that my username is only six characters long and I am still having these problems.

[usaexpor]

brand new DB issue today (NKB-4496326) ..... sometime this evening my db "reverted" itself back to the version from the 7th....the day i previously had a problem with corrupted db. ahh....i'm glad i have a backup THIS time, (only it's at work).

last time i got a pretty quick response and host gator did apologize but db performance was the reason i honestly chose hostgator over godaddy in the first place. i never really have issues but this one is embarassing me in front of my boss who is demanding i switch to a more reliable service.

now hopefully this stuff gets cleared up but i can't recommend hosting a db with hostgator without a very regular cron backup!!

[digitaltoast]

I'm having an issue for the last couple of weeks as far as I know of. It's documented in this conversation with the plugin's author.
It's a Wordpress plugin which has been working fine for over a year. Now suddenly this:

"Despite having loads of bans in place previously, I'm suddenly unable to add any new bans. I get the error:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'range, reason, redirect, thetime, timespan) VALUES ('1467098134', '1467098' at line 3

The database seems fine, nothing needs repair, and there's nothing in the error log.
I've disabled and re-enabled the plugin, too.

Easyban 1.3.2 Wordpress 2.3.1 PHP Version 5.2.9 MySQL 5.1.30"

After a LOT of trying to debug things myself and with the author, I posted the following ticket to HG support:

"Hi there; I'm going nuts trying to figure out a problem - it's been happening a couple of weeks now, and I eventually gave up and posted a question on the authors site - please see the issue here
http://forum.at.meandmymac.net/topic...es=7#post-1126
He says I need to ask you to turn on mysql logging for me, so we can try and work out the problem. I've been looking at all available logs and stuff, but I've now drawn a blank. This isn't happening to other users of the plugin, so we think it must be related to hostgator".

At this point, I'd not seen this thread. Support replied with:

"Unfortunately, we will not be able to enable query logging for your account, as we will then have to enable query logging for all accounts. This would quickly fill the disk and raise IO latency on the server significantly. Please let us know if you have any questions."

Finally, after browsing the forums a bit, I found this thread.
So, some questions: None of the DB usernames are > 16 characters (one is exactly 16).
Should support have suggested it might be the issue in this thread?
And...biggest question of all, how can I debug this issue if I can't get logging turned on?

[striddy]

Originally Posted by digitaltoast

I'm having an issue for the last couple of weeks as far as I know of. It's documented in this conversation with the plugin's author.
It's a Wordpress plugin which has been working fine for over a year. Now suddenly this:

How about banning the IP's in your .htaccess file? Saves database queries and therefore server resources.

Also, "Wordpress 2.3.1" Can I recommend you immediately upgrade wordpress. That version is quite old and may not be secure.

[digitaltoast]

Originally Posted by striddy

How about banning the IP's in your .htaccess file? Saves database queries and therefore server resources.

Well, yes, *I* could, but the EASY part of easyban means lesser users can add bans too - and also, the reason and duration can be set.
It also doesn't get to the more serious underlying mysql issue.

Originally Posted by striddy

Also, "Wordpress 2.3.1" Can I recommend you immediately upgrade wordpress. That version is quite old and may not be secure.

Ooop! Bit of a bad typo on my part - I meant 2.7.1 - well spotted.

Thanks for the other suggestion, too.

[citawds]

The above post is spam which has been reported.

Steve

[asgard]

Could someone please have a look at my site?

http://www.geekchixxx.com

Have been working on it most of tonight but then poof! it started to load pages slowly and then all of a sudden I am getting MySQL errors to do with my Wordpress database.

The main comment in all the error msgs is: [MySQL server has gone away]

[GvilleRick]

If you haven't done so already you should open a ticket with support. The forum is primarily peer support. The site did load slowly for me. There could be a problem with an account abusing resources and support should have a look.

[asgard]

Doing so now Gville, thanks.

[asgard]

Speaking with someone called Chris Bo via Live Chat *head desk* its 1:14AM I don't need this LOL
p.s. not blaming him for the lateness, just not needing my site going down is all. Just to clarify.

[asgard]

Crisis averted. Mods can you please delete my msgs.

[striddy]

@ asgard - Not related to MySQL but just a friendly tip. You might consider reducing some of your images to make them smaller in file size. Those with slow connections will really struggle to load your site in a respectable time frame.

Your home page and images are over 2Mb in size.

See this link for more info:

http://tools.pingdom.com/?url=http:/...e=0&save=false

[andersonpim]

Where can i find a group about procedures and fucntions. I am using , but is very difficult to maintence because everythink i need to send to hostgator

Thanks

[alainmarsol]

Thanks friends.
I have got some very interesting information from this forum.
---------------
brumisateur ventilateur