• ello!

    since 2 months I have problems with the server

    i install cloduflare to reduce the load, and it works greate beacause the load go from 5 to 1

    but wordpress mu still have pics of load that make crash the server

    So. I decided move the biggest site (androidzone.org 40000 user per day) to a new hosting: VPS from liquidweb (2Gb 1 CPU)

    then i delete all plugins, and all themes, except Platinum SEO Pack and Savrix Android Market

    The load is normal (0.6) but still have pics, one or to times at day that crash apache or server

    now i’ve deactivate wp cron by adding define(‘DISABLE_WP_CRON’, true);

    things seem normal in the course of 1 hour

    but what is the problem that is causing this? how to find it?

    this is the logs in one pic of high load

    11678 (Trace) (Kill) 	kandom 	4 	
    
     23.0 	
    
     0.8 	/usr/bin/php /home/kandom/public_html/index.php
    11698 (Trace) (Kill) 	kandom 	4 	
    
     17.0 	0.4 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11696 (Trace) (Kill) 	kandom 	4 	
    
     17.0 	0.0 	[php] <defunct>
    11713 (Trace) (Kill) 	kandom 	4 	
    
     17.0 	0.0 	[php]
    11699 (Trace) (Kill) 	kandom 	4 	
    
     16.0 	0.4 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11708 (Trace) (Kill) 	kandom 	4 	
    
     16.0 	0.4 	/usr/bin/php /home/kandom/public_html/index.php
    11711 (Trace) (Kill) 	kandom 	4 	
    
     16.0 	0.4 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11714 (Trace) (Kill) 	kandom 	4 	
    
     16.0 	0.3 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11679 (Trace) (Kill) 	kandom 	4 	
    
     16.0 	0.0 	[php] <defunct>
    11684 (Trace) (Kill) 	kandom 	4 	
    
     16.0 	0.0 	[php] <defunct>
    11710 (Trace) (Kill) 	kandom 	4 	
    
     16.0 	0.0 	[php] <defunct>
    11715 (Trace) (Kill) 	kandom 	4 	
    
     16.0 	0.0 	[php] <defunct>
    11709 (Trace) (Kill) 	kandom 	4 	
    
     15.0 	0.4 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11706 (Trace) (Kill) 	kandom 	4 	
    
     15.0 	0.3 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11707 (Trace) (Kill) 	kandom 	4 	
    
     15.0 	0.3 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11717 (Trace) (Kill) 	kandom 	4 	
    
     15.0 	0.3 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11720 (Trace) (Kill) 	kandom 	4 	
    
     13.0 	0.2 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11719 (Trace) (Kill) 	kandom 	4 	
    
     12.0 	0.2 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11722 (Trace) (Kill) 	kandom 	4 	
    
     12.0 	0.2 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11721 (Trace) (Kill) 	kandom 	4 	
    
     11.0 	0.2 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11725 (Trace) (Kill) 	kandom 	4 	
    
     9.0 	0.2 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11727 (Trace) (Kill) 	kandom 	4 	
    
     8.0 	0.2 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11732 (Trace) (Kill) 	kandom 	4 	
    
     8.0 	0.2 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11733 (Trace) (Kill) 	kandom 	4 	
    
     6.0 	0.2 	/usr/bin/php /home/kandom/public_html/wp-includes/ms-files.php
    11735 (Trace) (Kill) 	kandom 	4 	
    
     6.0 	0.2 	/usr/bin/php /home/kandom/public_html/wp-cron.php
    11457 (Trace) (Kill) 	kandom 	4 	
    
     2.2 	0.0 	[php] <defunct>
    11481 (Trace) (Kill) 	kandom 	4 	
    
     2.1 	0.0 	[php] <defunct>
    11362 (Trace) (Kill) 	kandom 	4 	
    
     1.3 	0.0 	[php] <defunct>

Viewing 1 replies (of 1 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    1) Talk to your webhost and ask them to help optimize your server.

    2) Turn on caching. A liquidweb VPS can install APC, which is great. Use that with W3TC.

Viewing 1 replies (of 1 total)
  • The topic ‘high load crash server’ is closed to new replies.