Hi,
There was a block placed on my database for my wordpress site, www.trainforhoops.com.
Is this something you would be able to help me resolve and get my site back online.
In the "Advanced project options..." I pasted the email my webhost sent me to alert of the situation. It will give you a better idea of the scope of the project.
## Deliverables
Hello,
This message is to advise you of a temporary block placed on your database. The database was found to be consuming an inordinate amount of processor time, to the point of degrading overall system performance. While we do limit each account to no more than 25% of a system's CPU in our terms of service, we do not actively disable accounts until they greatly exceed that number, which is what happened in this case. Requests to this database may become degraded by limiting the maximum number of queries or connections for a limited amount of time, or if there are sustained issues, ultimately we may be forced to block access to this database until the issue has been resolved.
Resolving this situation may be as simple as adding additional indexes to your database, optimizing the queries used, or something equally easy. If not, it may simply be a matter of moving this database to dedicated services, as it may have outgrown a shared environment.
If you believe you have a solution to this overuse, we are happy to discuss the situation with you and possibly reinstate the database on the server. Otherwise, we will be happy to assist you with the upgrade process if a dedicated server is the most appropriate solution. Thank you, and we look forward to hearing from you shortly.
~~~
Excessive MySQL activity is caused by (a) a long-running process that locks a table, causing other queries to back up, (b) a query that is not optimized ][example: select all from ... and involving a large or complex query], (c) huge table copies/maintenance during peak hours.
NOTE:, the following are just possible fixes or suggestions, and are not endorsed or supported by HostGator. They are included in the hope that they may apply to your situation, and/or help you reduce the amount of resources your SQL queries consume. As always, it's best to backup any data before making any changes or adjustments.
First and foremost, you may need to optimize your tables. The frequency depends on the size and usage of the database, but most databases would benefit from doing something like this on a yearly basis: a) Enter your phpMyAdmin/MySQL control panel. Click on the database (not the table, the database name), and on the right hand column your tables should be listed. Scroll down till you see the .Check all. link. Click on that link, make sure all database tables are checked and then from the drop-down next to it, and carefully select .Optimize table..
Additionally, adding indexes to your table(s) may improve performance. If you're not sure what you're doing, it's best not to modify any table; caution is recommended. There are various articles ([[login to view URL]<wbr />[login to view URL]<wbr /> to-Optimize-Your-MySQL-<wbr />[login to view URL]][1] and[http://www.databasejournal.<wbr />com/features/mysql/article.<wbr />php/ 1382791/Optimizing-MySQL-<wbr />[login to view URL]][2]). It may be best to Google for something like [Your Software Name] MySQL indexes for suggestions.
If you reply back to this with your IP address ([[login to view URL]<wbr />shtml][3]) we will be more than happy to go ahead enable HTTP access for you, so that you can safely work on the script without it causing further issues. Please let us know how you would like to proceed.
CPU_TIME:1 table_rows_read:98429 SELECTS:236 ROWS_UPDATED:116 ROWS_FETCHED:0 BUSY_TIME:3607 ONNECTED_TIME:3747 BYTES_SENT:184343398 BYTES_RECEIVED:4830046 WAIT_TIME:3606
Top table row reads:
DB_USER: ceasor_ceasor -- TOTAL_CONNECTIONS: 30 -- CONNECTED_TIME: 3747 -- CPU_TIME: 1 -- TABLE_ROW_READS: 98429 -- SELECT_COMMANDS: 236 -- UPDATE_COMMANDS: -- BUSY_TIME: 3607 -- BYTES_SENT: 184343398 -- BYTES_RECEIVED: 4830046 -- WAIT_TIME (IO): 3606
Top WAIT (IO) TIME:
DB_USER: ceasor_ceasor -- TOTAL_CONNECTIONS: 30 -- CONNECTED_TIME: 3747 -- CPU_TIME: 1 -- TABLE_ROW_READS: 98429 -- SELECT_COMMANDS: 236 -- UPDATE_COMMANDS: -- BUSY_TIME: 3607 -- BYTES_SENT: 184343398 -- BYTES_RECEIVED: 4830046 -- WAIT_TIME (IO): 3606
ceasor 17152 32.0 0.2 56120 35220 ? SN 13:00 0:00 /usr/bin/php /home/ceasor/public_html/<wbr style="font-size: 13px; background-color: #ffffff; font-family: arial, sans-serif;" />[login to view URL]
ceasor 17159 0.0 0.2 51664 30256 ? RN 13:00 0:00 /usr/bin/php /home/ceasor/public_html/wp-<wbr style="font-size: 13px; background-color: #ffffff; font-family: arial, sans-serif;" />[login to view URL]
Wed Feb 1 13:00:36 CST 2012
Running Processes:
ceasor 17152 32.0 0.2 56120 35220 ? SN 13:00 0:00 /usr/bin/php /home/ceasor/public_html/<wbr style="font-size: 13px; background-color: #ffffff; font-family: arial, sans-serif;" />[login to view URL]
ceasor 17159 0.0 0.2 52964 31436 ? RN 13:00 0:00 /usr/bin/php /home/ceasor/public_html/wp-<wbr style="font-size: 13px; background-color: #ffffff; font-family: arial, sans-serif;" />[login to view URL]
Running Queries:
*************************** 1. row ***************************
USER: ceasor_ceasor
DB: ceasor_trainhoops
STATE:
TIME: 0
COMMAND: Sleep
INFO: NULL
*************************** 2. row ***************************
USER: ceasor_ceasor
DB: ceasor_trainhoops
STATE:
TIME: 0
COMMAND: Sleep
INFO: NULL
Current Site Requests:
[login to view URL] [[login to view URL]][4] /wp-includes/js/jquery/ui.<wbr style="font-size: 13px; background-color: #ffffff; font-family: arial, sans-serif;" />[login to view URL]
[login to view URL] [[login to view URL]][4] /feed/
[login to view URL] [[login to view URL]][4] /wp-includes/js/jquery/ui.<wbr style="font-size: 13px; background-color: #ffffff; font-family: arial, sans-serif;" />[login to view URL]
[login to view URL] [[login to view URL]][4] /wp-includes/js/jquery/ui.<wbr style="font-size: 13px; background-color: #ffffff; font-family: arial, sans-serif;" />[login to view URL]
[login to view URL] [[login to view URL]][4] /wp-includes/js/jquery/ui.<wbr style="font-size: 13px; background-color: #ffffff; font-family: arial, sans-serif;" />[login to view URL]
[login to view URL] [[login to view URL]][4] /wp-includes/js/jquery/ui.<wbr style="font-size: 13px; background-color: #ffffff; font-family: arial, sans-serif;" />[login to view URL]
[login to view URL] [[login to view URL]][4] /[login to view URL]
[login to view URL] [[login to view URL]][4] /[login to view URL]
[login to view URL] [[login to view URL]][4] /[login to view URL]
[login to view URL] [[login to view URL]][4] /[login to view URL]
[login to view URL] [[login to view URL]][4] /[login to view URL]
[login to view URL] [[login to view URL]][4] /[login to view URL]
[login to view URL] [[login to view URL]][4] /[login to view URL]
[login to view URL] [[login to view URL]][4] /?p=577
[login to view URL] [[login to view URL]][4] /feed/