URGENT: 503 error!!!

Alright, lately I have been getting this on my website.


Personally I thought it would be my shoutbox that was giving me this problem. So I uninstalled my old shoutbox. Then I installed a new shoutbox.

Right after I installed the new shoutbox I still received that annoying error message. I checked my statistics and I have a lot of space and all that. So I finally checked my e-mail. I have received this from my host.

We have conducted a detailed investigation of the reason for the high resource consumption and it turned out that your website executes slow queries towards its database, which eventually hogs the server. The server tries to execute your slow queries while making other processes stay in the queue until some memory is freed. While they are waiting however, they stack up and further deteriorate the problem.

The reasons for such slow queries can be several:

1. Large database
2. Not well written scripts
3. Large number of internal links that query the database directly.

Upon further investigation, it turned out that the following queries in your account are slow and heavily consume server resources:

Recent slow queries:

# Time: 071020 11:28:06
# User@Host: sfoshowd_sfoshow[sfoshowd_sfoshow] @ localhost []
# Query_time: 3 Lock_time: 0 Rows_sent: 10 Rows_examined: 208014
use sfoshowd_Forum;
select s.*, count(s.sid) as `TS`, u.username, u.usergroupid from shout s
left join user u on (u.userid = s.s_by)
--
# Time: 071020 13:42:21
# User@Host: sfoshowd_sfoshow[sfoshowd_sfoshow] @ localhost []
# Query_time: 4 Lock_time: 0 Rows_sent: 10 Rows_examined: 208055
use sfoshowd_Forum;
select s.*, count(s.sid) as `TS`, u.username, u.usergroupid from shout s
left join user u on (u.userid = s.s_by)
--
# Time: 071020 13:42:45
# User@Host: sfoshowd_sfoshow[sfoshowd_sfoshow] @ localhost []
# Query_time: 8 Lock_time: 0 Rows_sent: 10 Rows_examined: 208055
select s.*, count(s.sid) as `TS`, u.username, u.usergroupid from shout s
--
# Time: 071020 13:42:48
# User@Host: sfoshowd_sfoshow[sfoshowd_sfoshow] @ localhost []
# Query_time: 3 Lock_time: 0 Rows_sent: 7 Rows_examined: 311673
select s.*, u.username, u.usergroupid from shout s
--
# Time: 071020 13:43:20
# User@Host: sfoshowd_sfoshow[sfoshowd_sfoshow] @ localhost []
# Query_time: 15 Lock_time: 0 Rows_sent: 10 Rows_examined: 208057
select s.*, count(s.sid) as `TS`, u.username, u.usergroupid from shout s
--
# Time: 071020 13:43:24
# User@Host: sfoshowd_sfoshow[sfoshowd_sfoshow] @ localhost []
# Query_time: 4 Lock_time: 0 Rows_sent: 10 Rows_examined: 207712
select s.*, u.username, u.usergroupid from shout s
--
# Time: 071020 13:43:44
# User@Host: sfoshowd_sfoshow[sfoshowd_sfoshow] @ localhost []
# Query_time: 4 Lock_time: 0 Rows_sent: 10 Rows_examined: 208057
select s.*, count(s.sid) as `TS`, u.username, u.usergroupid from shout s
--
# Time: 071020 13:43:46
# User@Host: sfoshowd_sfoshow[sfoshowd_sfoshow] @ localhost []
# Query_time: 2 Lock_time: 0 Rows_sent: 10 Rows_examined: 207712
select s.*, u.username, u.usergroupid from shout s
--
# Time: 071020 16:23:52
# User@Host: sfoshowd_sfoshow[sfoshowd_sfoshow] @ localhost []
# Query_time: 7 Lock_time: 0 Rows_sent: 10 Rows_examined: 208191
use sfoshowd_Forum;
select s.*, count(s.sid) as `TS`, u.username, u.usergroupid from shout s
left join user u on (u.userid = s.s_by)

Database size in Kb:
56752 - sfoshowd_Forum

In order to optimize the performance of your website, we recommend you to delete entries from your "shout" table to improve the connection speed with the database. Thus, the MySQL queries will become faster.

If this problem with your website is not resolved in 7 days we may need to SUSPEND YOUR ACCOUNT.

Please do NOT reply to this email. You can add comments on this issue by logging to your Customer Area (https://www.siteground.com/login_page.htm) and comment the ticket that has been automatically open on your behalf in connection to this case.

Now my question is if anyone can help me and tell me how I can delete these "MySQL queries" that are slowing down my site so I can enjoy and be on my website with out the annoying 503 error.
By the way, I thought that by removing my old shoutbox that it should be out now, but I guess not. So keep in mind that I installed a lighter newer shoutbox and I am still getting the error.

[Paul M]

You need to clear out your shout table, it has over 200,000 records.

Just run this SQL query ;

TRUNCATE shout ;

[Train]

Can you tell me step by step how to do so? Cause I can't do it on my forum seeing how I uninstalled it and put a new lighter version. But may you please tell me step by step how to? Thanks in advanced.

-Train

[Lynne]

What do you use to access your mysql tables? Do you use CPanel or phpMyAdmin or the vbulletin Admin CP to make queries? I think you can take your pick and run the query that Paul posted above and that will basically empty your shoutbox table so that all the previous conversations will be deleted and you will start fresh with an empty shoutbox.

[Paul M]

<a href="http://www.vbulletin.com/docs/html/maintenance_query" target="_blank">http://www.vbulletin.com/docs/html/maintenance_query</a>

[Train]

Is there a way to do this besides in the admincp? And I don't think you guys understand (maybe you do) but, I had that error when I had my old shoutbox. I removed my old one and put a newer lighter one and STILL get that error, just not as much.. so do I still run it?

[lighti]

Yes,

[Lynne]

Originally Posted by Train

Is there a way to do this besides in the admincp? And I don't think you guys understand (maybe you do) but, I had that error when I had my old shoutbox. I removed my old one and put a newer lighter one and STILL get that error, just not as much.. so do I still run it?

But it doesn't look like you deleted all the posts from the old shoutbox before you installed the new one.

[Train]

Ok, I tried doing this all and got these..

http://img105.imageshack.us/img105/6367/scenz043lh8.png

http://img89.imageshack.us/img89/4157/scenz045fo3.png

http://img236.imageshack.us/img236/1491/scenz047zi5.png

[Paul M]

Either you no longer have a shout table (in which case you no longer have a problem), or you use table prefixes. Check your list of table names in the next option (Repair / Optimise Tables)