homepage Welcome to WebmasterWorld Guest from 54.167.174.90
register, free tools, login, search, pro membership, help, library, announcements, recent posts, open posts,
Become a Pro Member
Home / Forums Index / Hardware and OS Related Technologies / Website Technology Issues
Forum Library, Charter, Moderators: phranque

Website Technology Issues Forum

    
Account Suspended - What Is To Be Done
anand84

WebmasterWorld Senior Member 5+ Year Member



 
Msg#: 4097315 posted 9:09 am on Mar 14, 2010 (gmt 0)

Hi

I just got a mail from my webhost saying that my account is suspended..Here is the entire transcript of the mail

Sir,
your wordpress usage has outgrown and is the prime cause of crashing mysql server every single day.
please know this much usage cannot be handled by shared hosting as there's a limit of 20% CPU resource usage on
our shared plans.

your mysql queries are just not fit to get handled by any shared plan,you should move this account to a
VPS hosting atleast if not a dedicated server.
your mysql process list is attached below which shows 75 active requests which is beyond resources which can be allocated to
a shared account.

5
9 hostaccount_wrdp1 localhost hostaccount_wrdp1 Query 714 Opening tables SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id WHER
17 hostaccount_wrdp1 localhost hostaccount_wrdp1 Query 704 Opening tables SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'
1825 hostaccount_wrdp4 localhost hostaccount_wrdp4 Query 690 Opening tables SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'
26 hostaccount_fanboi localhost hostaccount_dbname Query 689 Opening tables SELECT * FROM tbl_config
43 hostaccount_wrdp1 localhost hostaccount_wrdp1 Query 672 Opening tables SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'
47 hostaccount_wrdp1 localhost hostaccount_wrdp1 Query 667 Opening tables SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'
62 hostaccount_wrdp4 localhost hostaccount_wrdp4 Query 651 Opening tables SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'
65 hostaccount_wrdp1 localhost hostaccount_wrdp1 Query 648 Opening tables SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'
76 hostaccount_wrdp1 localhost hostaccount_wrdp1 Query 638 Opening tables SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'
83 hostaccount_wrdp1 localhost hostaccount_wrdp1 Query 635 Opening tables SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'
91 hostaccount_wrdp1 localhost NULL Init DB 624 NULL NULL
94 hostaccount_wrdp1 localhost NULL Init DB 623 NULL NULL
100 hostaccount_wrdp4 localhost NULL Init DB 614 NULL NULL
109 hostaccount_wrdp1 localhost NULL Init DB 601 NULL NULL
114 hostaccount_wrdp1 localhost NULL Init DB 591 NULL NULL
116 hostaccount_wrdp1 localhost NULL Init DB 589 NULL NULL
118 hostaccount_wrdp1 localhost NULL Init DB 587 NULL NULL
122 hostaccount_wrdp4 localhost NULL Init DB 577 NULL NULL
125 hostaccount_wrdp4 localhost NULL Init DB 576 NULL NULL
133 hostaccount_wrdp4 localhost NULL Init DB 555 NULL NULL
137 hostaccount_wrdp1 localhost NULL Init DB 552 NULL NULL
142 hostaccount_wrdp4 localhost NULL Init DB 548 NULL NULL
147 hostaccount_wrdp1 localhost NULL Init DB 541 NULL NULL
148 hostaccount_wrdp1 localhost NULL Init DB 541 NULL NULL
152 hostaccount_wrdp1 localhost NULL Init DB 535 NULL NULL
154 hostaccount_wrdp1 localhost NULL Init DB 534 NULL NULL
157 hostaccount_wrdp1 localhost NULL Init DB 533 NULL NULL
161 hostaccount_wrdp4 localhost NULL Init DB 524 NULL NULL
163 hostaccount_wrdp1 localhost NULL Init DB 520 NULL NULL
169 hostaccount_wrdp4 localhost NULL Init DB 512 NULL NULL
171 hostaccount_wrdp1 localhost NULL Init DB 510 NULL NULL
174 hostaccount_wrdp1 localhost NULL Init DB 506 NULL NULL
176 hostaccount_wrdp4 localhost NULL Init DB 503 NULL NULL
183 hostaccount_wrdp1 localhost NULL Init DB 499 NULL NULL
188 hostaccount_wrdp4 localhost NULL Init DB 497 NULL NULL
207 hostaccount_wrdp1 localhost NULL Init DB 480 NULL NULL
210 hostaccount_wrdp1 localhost NULL Init DB 478 NULL NULL
211 hostaccount_wrdp1 localhost NULL Init DB 476 NULL NULL
238 hostaccount_wrdp1 localhost NULL Init DB 438 NULL NULL
239 hostaccount_wrdp4 localhost NULL Init DB 437 NULL NULL
256 hostaccount_wrdp4 localhost NULL Init DB 401 NULL NULL
270 hostaccount_wrdp1 localhost NULL Init DB 155 NULL NULL
271 hostaccount_wrdp1 localhost NULL Init DB 155 NULL NULL
272 hostaccount_wrdp1 localhost NULL Init DB 154 NULL NULL
280 hostaccount_wrdp1 localhost NULL Init DB 147 NULL NULL
281 hostaccount_wrdp1 localhost NULL Init DB 147 NULL NULL
282 hostaccount_wrdp1 localhost NULL Init DB 147 NULL NULL
283 hostaccount_wrdp4 localhost NULL Init DB 147 NULL NULL
286 hostaccount_fanboi localhost NULL Init DB 145 NULL NULL
289 hostaccount_wrdp1 localhost NULL Init DB 142 NULL NULL
294 hostaccount_wrdp4 localhost NULL Init DB 138 NULL NULL
298 hostaccount_wrdp1 localhost NULL Init DB 134 NULL NULL
300 hostaccount_wrdp1 localhost NULL Init DB 132 NULL NULL
312 hostaccount_wrdp1 localhost NULL Init DB 117 NULL NULL
313 hostaccount_fanboi localhost NULL Init DB 115 NULL NULL
316 hostaccount_wrdp1 localhost NULL Init DB 113 NULL NULL
317 hostaccount_wrdp1 localhost NULL Init DB 111 NULL NULL
318 hostaccount_wrdp1 localhost NULL Init DB 110 NULL NULL
319 hostaccount_wrdp1 localhost NULL Init DB 110 NULL NULL
320 hostaccount_wrdp1 localhost NULL Init DB 109 NULL NULL
322 hostaccount_wrdp1 localhost NULL Init DB 107 NULL NULL
323 hostaccount_wrdp1 localhost NULL Init DB 106 NULL NULL
326 hostaccount_wrdp1 localhost NULL Init DB 104 NULL NULL
338 hostaccount_wrdp1 localhost NULL Init DB 92 NULL NULL
352 hostaccount_wrdp1 localhost NULL Init DB 78 NULL NULL
363 hostaccount_fanboi localhost NULL Init DB 66 NULL NULL
364 hostaccount_wrdp1 localhost NULL Init DB 63 NULL NULL
366 hostaccount_wrdp4 localhost NULL Init DB 61 NULL NULL
375 hostaccount_wrdp4 localhost NULL Init DB 48 NULL NULL
380 hostaccount_wrdp1 localhost NULL Init DB 41 NULL NULL
381 hostaccount_wrdp1 localhost NULL Init DB 38 NULL NULL
396 hostaccount_wrdp1 localhost NULL Init DB 19 NULL NULL
401 hostaccount_wrdp1 localhost NULL Init DB 12 NULL NULL
411 hostaccount_wrdp1 localhost NULL Init DB 2 NULL NULL


Do you think there is anyway I can optimize the site? I am feeling weird because today is supposed to be a day when my traffic is less than half of normal weekdays and I really don't understand how the account could overrun the limits today..

 

StoutFiles

WebmasterWorld Senior Member 5+ Year Member



 
Msg#: 4097315 posted 9:12 am on Mar 14, 2010 (gmt 0)

I would just get a dedicated server, unless you enjoy downtime and the fear of possible downtime.

anand84

WebmasterWorld Senior Member 5+ Year Member



 
Msg#: 4097315 posted 9:29 am on Mar 14, 2010 (gmt 0)

Hi Stoutfiles

My website is not big..I hardly get 2000 visitors on a peak day..I am curious if my webhost is just trying to fool me into signing into a VPS or dedicated server hosting..

Do you see anything from the email he had sent that can give an indication of this?

lammert

WebmasterWorld Senior Member lammert us a WebmasterWorld Top Contributor of All Time 5+ Year Member



 
Msg#: 4097315 posted 1:46 pm on Mar 14, 2010 (gmt 0)

It is difficult to say from this logfile if it causes a heavy load on the server. But the message "your wordpress usage has outgrown and is the prime cause of crashing mysql server every single day" is a red alert to me. No site on a shared hosting configuration with 2000 visitors each day should be able to bring a MySQL server on its knees. That is either a signal of bad configuration of the server, overselling, or the statement is only there to threaten you in a higher paying hosting plan.

Running a WordPress blog myself, I can hardly believe that with this amount of users they can claim that you are reaching the 20% CPU resource limit. 2000 visitors with each 4 pages gives one pageview every 10 seconds. 20% CPU resources would indicate at least 2 seconds CPU processing per generated page. Unless your blog is full of resource intensive third party plugins, that is hard to believe.

The only exception to this rule is when you use WordPress with static pages, not in blog mode. WordPress was originally a piece of blog software where posts are ordered on date and time. That part of the software is extremely efficient. Somewhere around version 2.0 the possibility of static pages was added to accommodate for about pages, privacy policy pages etc. Static pages are not stored in the regular posts structure, but in another way which happens to be extremely inefficient as soon as the number of static pages increases to about 100 and permalinks are used to reference to them.

There has been a thread about this recently in the supporters side of this board at [webmasterworld.com...]

If you don't want to move your site to another hosting situation, you can try to improve the current situation by switching on caching. With caching WordPress tries to store frequently used parts of pages in static files. Whenever these parts are needed, they are just read from disk instead of queried from the database which reduces CPU usage and increases page load speed.

anand84

WebmasterWorld Senior Member 5+ Year Member



 
Msg#: 4097315 posted 2:07 pm on Mar 14, 2010 (gmt 0)

Thank you Lammert,

I too have a hard time believing that the host has to say. Incidentally, I had received this in a mail yesterday


Your php query doesn't complete in even 1000seconds where allowed limit is 90seconds.
You need to optimize the program you use for this site.
Time: Sat Mar 13 01:21:37 2010 -0600
Account: #*$!XX
Resource: Process Time
Exceeded: 1041 > 90 (seconds)
Executable: php5
Command Line: php5


I am not a technical person, but I really don't think PHP queries on my wordpress blog can take that long a time. WP Caching is a great idea, wonder why I did not think of it..

Thanks again..

pageoneresults

WebmasterWorld Senior Member pageoneresults us a WebmasterWorld Top Contributor of All Time 10+ Year Member



 
Msg#: 4097315 posted 2:14 pm on Mar 14, 2010 (gmt 0)

That is either a signal of bad configuration of the server, overselling, or the statement is only there to threaten you in a higher paying hosting plan.


Wait! I'd like to add one more to that...

Or a signal that there may be something wrong in your configuration and you're causing the processor to max out. I've seen it happen many times, something in the app causes the processor to hit 100% and next thing you know, WHAM!

Are you sure there is nothing broken in whatever apps you may be providing to your visitors?

How many plugins do you have installed?

Are you monitoring your traffic? Are you possibly getting slammed by bots who are using up bandwidth and processing resources?

lammert

WebmasterWorld Senior Member lammert us a WebmasterWorld Top Contributor of All Time 5+ Year Member



 
Msg#: 4097315 posted 5:49 pm on Mar 14, 2010 (gmt 0)

A script going nuts is indeed a possibility. 1041 seconds is a really large amount for a script. This looks like an internal loop in the script which is not terminating. The visitor which triggered that action probably left the site long before the execution was finished.

Did the hosting company tell you which script is causing these problems? If it is a plugin, you might safe a lot of CPU resources by temporarily switching off that plugin. If it is in the main stream WP, it is probably known behavior and fixes or workarounds might be available.

Global Options:
 top home search open messages active posts  
 

Home / Forums Index / Hardware and OS Related Technologies / Website Technology Issues
rss feed

All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
Home ¦ Free Tools ¦ Terms of Service ¦ Privacy Policy ¦ Report Problem ¦ About ¦ Library ¦ Newsletter
WebmasterWorld is a Developer Shed Community owned by Jim Boykin.
© Webmaster World 1996-2014 all rights reserved