vb.org Archive - URGENT: 503 error!!!

vb.org Archive (https://vborg.vbsupport.ru/index.php)

- General Hosting/Server Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=197)

- - URGENT: 503 error!!! (https://vborg.vbsupport.ru/showthread.php?t=161319)

URGENT: 503 error!!!

Alright, lately I have been getting this on my website.
http://img504.imageshack.us/img504/8130/scenz033ei0.png

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.

Quote:

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.

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

Just run this SQL query ;

Code:

TRUNCATE shout ;

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

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.

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

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?

Quote:

Originally Posted by Train (Post 1370444)

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

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)

Quote:

Originally Posted by Paul M (Post 1370493)

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)

What exactly do you want me to do Optimize Tables & Repair Tables?

What I said.

Quote:

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)

I don't see anything in there. :(
Any other suggestions so my site won't get that annoying 503 error once in a while?

I don't know enough about mysql, but if he *is* using table prefixes and the queries are not using a table prefix (like in the first post it doesn't look like there are any table prefixes used), could that be why they are showing as slow queries or problem queries - because there is not table called just shout?

If the problem is table prefixes, you need to go into the code for your shout box and replace "FROM shout" with "FROM ".$TABLE_PREFIX."shout"

Also, do you have access to phpMyAdmin to see your mySQL tables?

Yes I have access to phpMyAdmin to see my mySQL tables..

Also just a reminder I installed a NEW shoutbox guys.. I WAS running vbshout 2.0, now im on Inferno vBShout. So.. just a reminder so you don't have me doing work I don't need to..

Quote:

If the problem is table prefixes, you need to go into the code for your shout box and replace "FROM shout" with "FROM ".$TABLE_PREFIX."shout"

For my new shoutbox? Cause if I uninstalled my old one wouldn't it be removed? Also how would I do this.

Go inside your administrators control panel. Click on the Maintenance navigation box and then click on "Repair / Optimize Tables". Once that is done it will give you a list of all your tables. Once you have that list click look at it and compare the first entry (should be the same) to the one below:

access

If it is something like "vb_access" you use a table prefix. Once you have determined that go back and alter the query Paul M gave you to look like this:

[sql]TRUNCATE PREFIXshout;[/sql]

Just replace PREFIX with the prefix you found before the "access" in the last step. This should solve your problem.

Are you sure that your new shoutbox is not also using a table called 'shout'? I know that from my work on trackers, many of them will have tables with the same names and same column names (cuz they all make sense to have these names), so it may be that many shoutbox hacks use a table called 'shout'. When you uninstalled the old hack, did you remove the tables it installed when you installed it?

[sql]TRUNCATE infernoshout[/sql]

They have inferno in front of the shout box.

It would have been more helpful if you'd specified which two shout mods you used from the start. Since you are now using Infernoshout (which does not use the same table as your previous shout) the first part of my reply was correct.

Quote:

Originally Posted by 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)

When you removed vb shout, the offending table (below) was deleted.

Quote:

# 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)

X vBulletin 3.8.12 by vBS Debug Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (1)bbcode_code_printable (7)bbcode_quote_printable (1)footer (1)gobutton (1)header (1)headinclude (6)option (1)post_thanks_navbar_search (1)printthread (19)printthreadbit (1)spacer_close (1)spacer_open Phrase Groups Available: global postbit showthread	Included Files: ./printthread.php ./global.php ./includes/init.php ./includes/class_core.php ./includes/config.php ./includes/functions.php ./includes/class_hook.php ./includes/modsystem_functions.php ./includes/class_bbcode_alt.php ./includes/class_bbcode.php ./includes/functions_bigthree.php Hooks Called: init_startup init_startup_session_setup_start init_startup_session_setup_complete cache_permissions fetch_threadinfo_query fetch_threadinfo fetch_foruminfo style_fetch cache_templates global_start parse_templates global_setup_complete printthread_start bbcode_fetch_tags bbcode_create bbcode_parse_start bbcode_parse_complete_precache bbcode_parse_complete printthread_post printthread_complete
Messages:

Phrase Groups Available:

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.01691 seconds Memory Usage 1,790KB Queries Executed 10 (?)
More Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (1)bbcode_code_printable (7)bbcode_quote_printable (1)footer (1)gobutton (1)header (1)headinclude (6)option (1)post_thanks_navbar_search (1)printthread (19)printthreadbit (1)spacer_close (1)spacer_open Phrase Groups Available: global postbit showthread	Included Files: ./printthread.php ./global.php ./includes/init.php ./includes/class_core.php ./includes/config.php ./includes/functions.php ./includes/class_hook.php ./includes/modsystem_functions.php ./includes/class_bbcode_alt.php ./includes/class_bbcode.php ./includes/functions_bigthree.php Hooks Called: init_startup init_startup_session_setup_start init_startup_session_setup_complete cache_permissions fetch_threadinfo_query fetch_threadinfo fetch_foruminfo style_fetch cache_templates global_start parse_templates global_setup_complete printthread_start bbcode_fetch_tags bbcode_create bbcode_parse_start bbcode_parse_complete_precache bbcode_parse_complete printthread_post printthread_complete
Messages: