Pages : 1
#1 Le 11/11/2009, à 16:51
- Pepou06
[Résolu] Charge CPU de mon serveur sous ubuntu
Bonjour,
Voilà j'ai une dedibox qui héberge trois sites ayant des scripts php :
http://www.carabinsnicois.fr => joomla + phpbb3
http://www.nice-anatomie.fr => cmsms
http://www.nice-externes.fr => des scripts maisons
La charge CPU de ma dedibox est quasiment toujours à 100%, et pendant les heures de pointe, les sites ne sont même plus accessibles.
En ce moment, 11 heures du matin :
top - 12:34:52 up 15 min, 1 user, load average: 149.07, 109.01, 52.18
Tasks: 262 total, 151 running, 111 sleeping, 0 stopped, 0 zombie
Cpu(s): 99.7%us, 0.3%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1999400k total, 936108k used, 1063292k free, 19872k buffers
Swap: 1044216k total, 0k used, 1044216k free, 435388k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
5915 www-data 20 0 232m 8564 1812 R 1.3 0.4 0:03.08 apache2
5992 www-data 20 0 232m 8572 1812 R 1.3 0.4 0:02.96 apache2
5994 www-data 20 0 232m 8580 1820 R 1.3 0.4 0:02.68 apache2
5996 www-data 20 0 232m 8560 1812 R 1.3 0.4 0:02.67 apache2
5751 www-data 20 0 232m 8832 2012 R 1.0 0.4 0:04.86 apache2
5755 www-data 20 0 235m 18m 8644 R 1.0 1.0 0:06.31 apache2
5760 www-data 20 0 232m 8668 1884 R 1.0 0.4 0:05.88 apache2
5762 www-data 20 0 232m 8672 1884 R 1.0 0.4 0:05.66 apache2
5763 www-data 20 0 234m 17m 8624 R 1.0 0.9 0:05.70 apache2
5767 www-data 20 0 236m 20m 9956 R 1.0 1.1 0:05.78 apache2
5795 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:04.89 apache2
5803 www-data 20 0 232m 8580 1820 R 1.0 0.4 0:04.77 apache2
5856 www-data 20 0 232m 8584 1820 R 1.0 0.4 0:03.94 apache2
5865 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:03.74 apache2
5867 www-data 20 0 232m 8576 1812 R 1.0 0.4 0:03.90 apache2
5868 www-data 20 0 232m 8576 1812 R 1.0 0.4 0:03.80 apache2
5871 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:03.64 apache2
5872 www-data 20 0 232m 8584 1820 R 1.0 0.4 0:03.70 apache2
5895 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:03.51 apache2
5896 www-data 20 0 232m 8584 1820 R 1.0 0.4 0:03.52 apache2
5901 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:03.29 apache2
5916 www-data 20 0 232m 8820 1996 R 1.0 0.4 0:02.94 apache2
5917 www-data 20 0 232m 8588 1820 R 1.0 0.4 0:03.03 apache2
5923 www-data 20 0 232m 8580 1820 R 1.0 0.4 0:03.16 apache2
5929 www-data 20 0 232m 8564 1812 R 1.0 0.4 0:03.10 apache2
5937 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:03.25 apache2
5938 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:02.96 apache2
5977 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:02.99 apache2
5984 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:02.89 apache2
5988 www-data 20 0 232m 8568 1812 R 1.0 0.4 0:02.88 apache2
5995 www-data 20 0 232m 8580 1820 R 1.0 0.4 0:02.56 apache2
5999 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:02.70 apache2
6000 www-data 20 0 232m 8580 1820 R 1.0 0.4 0:02.73 apache2
6007 www-data 20 0 232m 8772 1964 R 1.0 0.4 0:02.63 apache2
6014 www-data 20 0 232m 8752 1960 R 1.0 0.4 0:02.50 apache2
6015 www-data 20 0 232m 8752 1960 R 1.0 0.4 0:02.48 apache2
6022 www-data 20 0 232m 8568 1812 R 1.0 0.4 0:02.31 apache2
6076 www-data 20 0 232m 8576 1812 R 1.0 0.4 0:01.97 apache2
6111 www-data 20 0 232m 8584 1820 R 1.0 0.4 0:01.81 apache2
6131 www-data 20 0 232m 8584 1820 R 1.0 0.4 0:01.80 apache2
6185 www-data 20 0 232m 8580 1820 R 1.0 0.4 0:01.81 apache2
6195 www-data 20 0 232m 8584 1820 R 1.0 0.4 0:01.69 apache2
6196 www-data 20 0 232m 8568 1812 R 1.0 0.4 0:01.60 apache2
6198 www-data 20 0 232m 8572 1812 R 1.0 0.4 0:01.56 apache2
5749 www-data 20 0 238m 33m 20m R 0.7 1.7 0:06.88 apache2
5750 www-data 20 0 237m 25m 13m R 0.7 1.3 0:06.89 apache2
5757 www-data 20 0 236m 21m 10m R 0.7 1.1 0:06.68 apache2
5764 www-data 20 0 235m 18m 8668 R 0.7 1.0 0:05.52 apache2Voici mon /etc/apache2/apache2.conf :
#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/var/log/apache2/foo.log"
# with ServerRoot set to "" will be interpreted by the
# server as "//var/log/apache2/foo.log".
#
### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/etc/apache2"
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#<IfModule !mpm_winnt.c>
#<IfModule !mpm_netware.c>
LockFile /var/lock/apache2/accept.lock
#</IfModule>
#</IfModule>
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5
##
## Server-Pool Size Regulation (MPM specific)
##
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
StartServers 5
MinSpareServers 5
MaxSpareServers 15
MaxClients 150
MaxRequestsPerChild 1500
</IfModule>
# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 1000
</IfModule>
# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}
#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#
AccessFileName .htaccess
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ~ "^\.ht">
Order allow,deny
Deny from all
</Files>
#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain
#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog /var/log/apache2/error.log
#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn
# Include module configuration:
Include /etc/apache2/mods-enabled/*.load
Include /etc/apache2/mods-enabled/*.conf
# Include all the user configurations:
Include /etc/apache2/httpd.conf
# Include ports listing
Include /etc/apache2/ports.conf
# La directive ServerLimit permet d'overrider la valeur par default qui vous limite à 256 clients
ServerLimit 256
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
#
# Define an access log for VirtualHosts that don't define their own logfile
CustomLog /var/log/apache2/other_vhosts_access.log vhost_combined
#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#
#
# Putting this all together, we can internationalize error responses.
#
# We use Alias to redirect any /error/HTTP_<error>.html.var response to
# our collection of by-error message multi-language collections. We use
# includes to substitute the appropriate text.
#
# You can modify the messages' appearance without changing any of the
# default HTTP_<error>.html.var files by adding the line:
#
# Alias /error/include/ "/your/include/path/"
#
# which allows you to create your own set of files by starting with the
# /usr/share/apache2/error/include/ files and copying them to /your/include/path/,
# even on a per-VirtualHost basis. The default include files will display
# your Apache version number and your ServerAdmin email address regardless
# of the setting of ServerSignature.
ServerSignature Off
ServerTokens Prod
#
# The internationalized error documents require mod_alias, mod_include
# and mod_negotiation. To activate them, uncomment the following 30 lines.
# Alias /error/ "/usr/share/apache2/error/"
#
# <Directory "/usr/share/apache2/error">
# AllowOverride None
# Options IncludesNoExec
# AddOutputFilter Includes html
# AddHandler type-map var
# Order allow,deny
# Allow from all
# LanguagePriority en cs de es fr it nl sv pt-br ro
# ForceLanguagePriority Prefer Fallback
# </Directory>
#
# ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
# ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
# ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
# ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
# ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
# ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
# ErrorDocument 410 /error/HTTP_GONE.html.var
# ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
# ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
# ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
# ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
# ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
# ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
# ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
# ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
# ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
# ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var
# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.
# Include generic snippets of statements
Include /etc/apache2/conf.d/
# Include the virtual host configurations:
Include /etc/apache2/sites-enabled/
<Directory "/home/">
</Directory>
#
# Directives to allow use of AWStats as a CGI
#
Alias /awstats-icon/ /usr/share/awstats/icon/
<Directory /usr/share/awstats/icon>
Options None
AllowOverride None
Order allow,deny
Allow from all
</Directory>Ma configuration php => Accessible ici http://yannick.walrave.free.fr/save/testos.php
J'ai eAccelerator installé et fonctionnel sur le serveur.
Et quelques statistiques sur les trois sites hébergés :
http://yannick.walrave.free.fr/save/aws … abins.html
http://yannick.walrave.free.fr/save/aws … tomie.html
http://yannick.walrave.free.fr/save/aws … ernes.html
Voilà, si vous avez des conseils pour améliorer tout ça !!
Merci d'avance !
Dernière modification par slasher-fun (Le 15/11/2009, à 23:29)
Hors ligne
#2 Le 11/11/2009, à 17:34
- bez856
Re : [Résolu] Charge CPU de mon serveur sous ubuntu
Salut,
Alors je ne suis pas un pro dans les charges trop importantes de CPU mais ça m'est déjà arrivé donc peut-être que mon expérience te servira.
Est-ce suite à une mise à joiur du site que les charges se sont mises à s'envoler comme ça ?
Pour ma part il s'agissait d'un script php qui bouclait à l'infini sur le coupage d'une chaine de caractère au-delà de sa taille. Ce qui faisait que le serveur s'emballait et le serveur était inaccessible aussi au bout d'un moment . . .
Hors ligne
#3 Le 11/11/2009, à 17:36
- Pepou06
Re : [Résolu] Charge CPU de mon serveur sous ubuntu
Oui, j'ai installer la dernière version de joomla (qui est sortie il y a 2 jours je crois) !
Je vais voir de ce coté là !
Hors ligne
#4 Le 11/11/2009, à 17:40
- bez856
Re : [Résolu] Charge CPU de mon serveur sous ubuntu
Est-ce normal qu'actuellement ton serveur soit complètement in-joignable ?
Hors ligne
#5 Le 11/11/2009, à 17:59
- Pepou06
Re : [Résolu] Charge CPU de mon serveur sous ubuntu
Je désactive de temps en temps apache2 pour changer quelques paramètres, je fais des essais..
Hors ligne
#6 Le 14/11/2009, à 18:34
- Pepou06
Re : [Résolu] Charge CPU de mon serveur sous ubuntu
Voilà ce que j'ai dans error.log d'apache2 à chaque fois que le serveur sature :
[Sat Nov 14 15:28:35 2009] [warn] child process 25850 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:35 2009] [warn] child process 24930 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:35 2009] [warn] child process 25973 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:35 2009] [warn] child process 25534 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:35 2009] [warn] child process 25540 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:35 2009] [warn] child process 26120 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:37 2009] [warn] child process 25850 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:37 2009] [warn] child process 24930 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:37 2009] [warn] child process 25973 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:37 2009] [warn] child process 25534 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:37 2009] [warn] child process 25540 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:37 2009] [warn] child process 26120 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:39 2009] [warn] child process 25850 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:39 2009] [warn] child process 24930 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:39 2009] [warn] child process 25973 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:39 2009] [warn] child process 25534 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:39 2009] [warn] child process 25540 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:39 2009] [warn] child process 26120 still did not exit, sending a SIGTERM
[Sat Nov 14 15:28:41 2009] [error] child process 25850 still did not exit, sending a SIGKILL
[Sat Nov 14 15:28:41 2009] [error] child process 24930 still did not exit, sending a SIGKILL
[Sat Nov 14 15:28:41 2009] [error] child process 25973 still did not exit, sending a SIGKILL
[Sat Nov 14 15:28:41 2009] [error] child process 25534 still did not exit, sending a SIGKILL
[Sat Nov 14 15:28:41 2009] [error] child process 25540 still did not exit, sending a SIGKILL
[Sat Nov 14 15:28:41 2009] [error] child process 26120 still did not exit, sending a SIGKILL
Hors ligne
#7 Le 15/11/2009, à 23:23
- Pepou06
Re : [Résolu] Charge CPU de mon serveur sous ubuntu
Problème réglé grâce à Xcache ! Bien plus performant que eaccelerator dans mon cas.
http://doc.ubuntu-fr.org/xcache
Hors ligne
Pages : 1