Заполняет на VDS память apache2

12
S
На сайте с 22.09.2009
Offline
106
1886

Здравствуйте. Помогите решить данную проблему. Постоянно на vds в пределах часа идет большая нагрузка на память и занимает всю. Вроде дырку нашел в apache2

Вот конфиг:

# It is split into several files forming the configuration hierarchy outlined

# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `-- ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf.d
# | `-- *
# `-- sites-enabled
# `-- *
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
#
# In order to avoid conflicts with backup files, the Include directive is
# adapted to ignore files that:
# - do not begin with a letter or number
# - contain a character that is neither letter nor number nor _-:.
# - contain .dpkg
#
# Yet we strongly suggest that all configuration files either end with a
# .conf or .load suffix in the file name. The next Debian release will
# ignore files not ending with .conf (or .load for mods-enabled).
#
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections, and which
# of these ports are used for name based virtual hosts.
#
# * Configuration files in the mods-enabled/ and sites-enabled/ directories
# contain particular configuration snippets which manage modules or virtual
# host configurations, respectively.
#
# They are activated by symlinking available configuration files from their
# respective *-available/ counterparts. These should be managed by using our
# helpers a2enmod/a2dismod, a2ensite/a2dissite. See
# their respective man pages for detailed information.
#
# * Configuration files in the conf.d directory are either provided by other
# packages or may be added by the local administrator. Local additions
# should start with local- or end with .local.conf to avoid name clashes. All
# files in conf.d are considered (excluding the exceptions noted above) by
# the Apache 2 web server.
#
# * The binary is called apache2. Due to the use of environment variables, in
# the default configuration, apache2 needs to be started/stopped with
# /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
# work with the default configuration.


# Global configuration
#

#
# 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.2/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.
#
LockFile ${APACHE_LOCK_DIR}/accept.lock

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

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

##
## 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>
MaxKeepAliveRequests 100
KeepAliveTimeout 3
StartServers 1
MinSpareServers 1
MaxSpareServers 1
MaxClients 5
MaxRequestsPerChild 300
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadLimit: ThreadsPerChild can be changed to this maximum value during a
# graceful restart. ThreadLimit can only be changed by stopping
# and starting Apache.
# ThreadsPerChild: constant number of worker threads in each server process
# MaxClients: maximum number of simultaneous client connections
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
MaxKeepAliveRequests 100
KeepAliveTimeout 3
StartServers 1
MinSpareServers 1
MaxSpareServers 1
MaxClients 5
MaxRequestsPerChild 300
</IfModule>

# event MPM
# StartServers: initial number of server processes to start
# 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
# MaxClients: maximum number of simultaneous client connections
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_event_module>
MaxKeepAliveRequests 100
KeepAliveTimeout 3
StartServers 1
MinSpareServers 1
MaxSpareServers 1
MaxClients 5
MaxRequestsPerChild 300
</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
Satisfy 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.
#
# It is also possible to omit any default MIME type and let the
# client's browser guess an appropriate action instead. Typically the
# browser will decide based on the file's extension then. In cases
# where no good assumption can be made, letting the default MIME type
# unset is suggested instead of forcing the browser to accept
# incorrect metadata.
#
DefaultType None


#
# 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 ${APACHE_LOG_DIR}/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 mods-enabled/*.load
Include mods-enabled/*.conf

# Include list of ports to listen on and which to use for name based vhosts
Include ports.conf

Glueon
На сайте с 26.07.2013
Offline
172
#1

Какова смысловая нагрузка скриншота htop'a? Чего там аномального?

Какой у вас memory_limit стоит?

Есть много IP-сетей в аренду под прокси, парсинг, рассылки (optin), vpn и хостинг. Телега: @contactroot ⚒ ContactRoot команда опытных сисадминов (/ru/forum/861038), свой LIR: сдаем в аренду сети IPv4/v6 (/ru/forum/1012475).
S
На сайте с 22.09.2009
Offline
106
#2

16M Мало, много?)

Andreyka
На сайте с 19.02.2005
Offline
822
#3

Глупости вы пишите.

Зачем вам нужна память, кроме как заполнять ее программами и разными данными?

Пусть себе заполняет.

Не стоит плодить сущности без необходимости
S
На сайте с 22.09.2009
Offline
106
#4

Так у меня сервак лежит сразу как на 100% забита память.

Glueon
На сайте с 26.07.2013
Offline
172
#5

Она забивается на 100%?

16мб - это мало. У вас примерно 1ГБ свободной памяти, значит память забивается при одновременном обращении 64 клиентов. Такая нагрузка бывает? 3.84e3 запросов в минуту.

kxk
На сайте с 30.01.2005
Offline
990
kxk
#6

SAnet, Дам 1, но дельный совет - поставьте Nginx как Reverse-Proxy

Ваш DEVOPS
S
На сайте с 22.09.2009
Offline
106
#7
Glueon:
Она забивается на 100%?

16мб - это мало. У вас примерно 1ГБ свободной памяти, значит память забивается при одновременном обращении 64 клиентов. Такая нагрузка бывает? 3.84e3 запросов в минуту.

Вы знаете, я сайт поднял ток. возможно так и есть. Я держу 3 сайта на системе Joomla.

Хотя по я.метрики не вижу большой посещаемости.

---------- Добавлено 15.10.2014 в 17:23 ----------

kxk:
SAnet, Дам 1, но дельный совет - поставьте Nginx как Reverse-Proxy

Да робит. Я его сразу поставил.

W
На сайте с 02.10.2014
Offline
8
#8

Скриншот ниочем.

Нужно анализировать логи апача из-за чего забивается память.

Так же смотреть список процессов, трейснуть. короче разбираться нормально нужно.

обращайтесь если что

S
На сайте с 22.09.2009
Offline
106
#9
wimbo:
Скриншот ниочем.
Нужно анализировать логи апача из-за чего забивается память.
Так же смотреть список процессов, трейснуть. короче разбираться нормально нужно.
обращайтесь если что

[Tue Oct 14 17:18:33 2014] [notice] caught SIGTERM, shutting down

[Tue Oct 14 17:18:34 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Tue Oct 14 17:18:34 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations
[Tue Oct 14 17:19:02 2014] [notice] caught SIGTERM, shutting down
[Tue Oct 14 17:19:04 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Tue Oct 14 17:19:04 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Tue Oct 14 17:19:41 2014] [notice] caught SIGTERM, shutting down
[Tue Oct 14 17:20:05 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Tue Oct 14 17:20:06 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Tue Oct 14 17:33:25 2014] [notice] caught SIGTERM, shutting down
[Tue Oct 14 17:33:47 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Tue Oct 14 17:33:47 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Tue Oct 14 17:35:15 2014] [notice] caught SIGTERM, shutting down
[Tue Oct 14 17:35:17 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Tue Oct 14 17:35:17 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Tue Oct 14 17:40:54 2014] [notice] Graceful restart requested, doing restart
[Tue Oct 14 17:40:54 2014] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Tue Oct 14 17:40:54 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Tue Oct 14 17:41:16 2014] [notice] Graceful restart requested, doing restart
[Tue Oct 14 17:41:16 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Wed Oct 15 08:11:42 2014] [warn] child process 2864 still did not exit, sending a SIGTERM
[Wed Oct 15 08:11:42 2014] [warn] child process 2955 still did not exit, sending a SIGTERM
[Wed Oct 15 08:11:42 2014] [warn] child process 4859 still did not exit, sending a SIGTERM
[Wed Oct 15 08:11:43 2014] [notice] caught SIGTERM, shutting down
[Wed Oct 15 08:13:24 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Wed Oct 15 08:13:31 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Wed Oct 15 08:21:05 2014] [notice] caught SIGTERM, shutting down
[Wed Oct 15 08:21:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Wed Oct 15 08:21:06 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Wed Oct 15 08:23:00 2014] [notice] caught SIGTERM, shutting down
[Wed Oct 15 08:23:01 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Wed Oct 15 08:23:01 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Wed Oct 15 08:23:53 2014] [notice] caught SIGTERM, shutting down
[Wed Oct 15 08:23:54 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Wed Oct 15 08:23:54 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Wed Oct 15 09:48:40 2014] [notice] Graceful restart requested, doing restart
[Wed Oct 15 09:48:40 2014] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Wed Oct 15 09:48:40 2014] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Wed Oct 15 09:48:40 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Wed Oct 15 14:02:20 2014] [notice] caught SIGTERM, shutting down
[Wed Oct 15 14:02:21 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Wed Oct 15 14:02:21 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Wed Oct 15 14:02:24 2014] [error] server reached MaxClients setting, consider raising the MaxClients setting
[Wed Oct 15 14:24:27 2014] [notice] caught SIGTERM, shutting down
[Wed Oct 15 14:24:28 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Wed Oct 15 14:24:28 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Wed Oct 15 14:46:15 2014] [notice] caught SIGTERM, shutting down
[Wed Oct 15 14:46:16 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Wed Oct 15 14:46:16 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u14 configured -- resuming normal operations
[Wed Oct 15 16:15:46 2014] [error] server reached MaxClients setting, consider raising the MaxClients setting
Andreyka
На сайте с 19.02.2005
Offline
822
#10

Смешной вы человек, ТС

Скидываете информацию по чайной ложечке и думаете, что кто-то бесплатно будет вам настраивать VDS?

12

Авторизуйтесь или зарегистрируйтесь, чтобы оставить комментарий