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

SAnet · 2014-10-15T11:02:57.0000000Z

Здравствуйте. Помогите решить данную проблему. Постоянно на 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

185

G-and-Y

16 октября 2014, 04:53

#11

как бы раздел бесплатных советов.

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

/ru/forum/comment/13067532

1

Абузо-устойчивые впс ( http://vps-hosting.lv/?p=13408 )

S

106

SAnet

16 октября 2014, 06:51

#12

G-and-Y:
как бы раздел бесплатных советов.

Тс почитайте, после настройки забыл что такой падение впс, только настраивайте под свой обьем памяти.
/ru/forum/comment/13067532

Спасибо большое, щас буду разбираться :)

S

106

SAnet

6 ноября 2014, 04:28

#13

G-and-Y:
как бы раздел бесплатных советов.

Тс почитайте, после настройки забыл что такой падение впс, только настраивайте под свой обьем памяти.
/ru/forum/comment/13067532

Хорошо.Вроде все перенастроил. Но объявился косяк следующий, ест под 100% память Mysql

Вот его конфиг:

key_buffer		= 16M

max_allowed_packet	= 16M

thread_stack		= 192K

thread_cache_size       = 8

query_cache_limit	= 1M

query_cache_size        = 16M

table_open_cache = 400

table_definition_cache = 400

myisam-recover         = BACKUP

А вот сами процессы:

W

8

wimbo

6 ноября 2014, 06:43

#14

mysql -uroot -p -e "SHOW PROCESSLIST;"

или лучше

mysql -uroot -p -e "SHOW FULL PROCESSLIST;"

И смотрите кто сжирает так MySQL :)

S

106

SAnet

6 ноября 2014, 06:56

#15

wimbo:
mysql -uroot -p -e "SHOW PROCESSLIST;"
или лучше
mysql -uroot -p -e "SHOW FULL PROCESSLIST;"
И смотрите кто сжирает так MySQL :)

db-null, time-0, state-0, info-проц

Пустота)

---------- Добавлено 06.11.2014 в 11:05 ----------

Посмотрел - mysqltuner.pl

Вот дабы что выдал)

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +ARCHIVE +BLACKHOLE +CSV -FEDERATED +InnoDB +MRG_MYISAM
[--] Data in MyISAM tables: 5M (Tables: 307)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)
[--] Data in MEMORY tables: 0B (Tables: 6)
[!!] InnoDB is enabled but isn't being used
[!!] Total fragmented tables: 5

-------- Security Recommendations -------------------------------------------
[OK] All database users have passwords assigned

-------- Performance Metrics -------------------------------------------------
[--] Up for: 15m 1s (1K q [1.967 qps], 380 conn, TX: 1M, RX: 280K)
[--] Reads / Writes: 91% / 9%
[--] Total buffers: 276.0M global + 5.6M per thread (151 max threads)
[OK] Maximum possible memory usage: 1.1G (72% of installed RAM)
[OK] Slow queries: 0% (0/1K)
[OK] Highest usage of available connections: 1% (2/151)
[OK] Key buffer size / total MyISAM indexes: 100.0M/4.2M
[OK] Key buffer hit rate: 97.3% (7K cached / 194 reads)
[OK] Query cache efficiency: 22.1% (263 cached / 1K selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 99 sorts)
[!!] Joins performed without indexes: 46
[OK] Temporary tables created on disk: 22% (95 on disk / 417 total)
[OK] Thread cache hit rate: 99% (2 created / 380 connections)
[OK] Table cache hit rate: 23% (368 open / 1K opened)
[OK] Open file limit used: 30% (678/2K)
[OK] Table locks acquired immediately: 100% (954 immediate / 954 locks)

-------- Recommendations -----------------------------------------------------
General recommendations:
Add skip-innodb to MySQL configuration to disable InnoDB
Run OPTIMIZE TABLE to defragment tables for better performance
MySQL started within last 24 hours - recommendations may be inaccurate
Adjust your join queries to always utilize indexes
Variables to adjust:
join_buffer_size (> 3.0M, or always use indexes with joins)

W

8

wimbo

6 ноября 2014, 08:24

#16

Т.е. у Вас ни одного процесса в MySQL и он грузит 100% CPU?

S

106

SAnet

6 ноября 2014, 08:54

#17

wimbo:
Т.е. у Вас ни одного процесса в MySQL и он грузит 100% CPU?

Так точно. Сам удивлен.

185

G-and-Y

6 ноября 2014, 10:21

#18

Так грузит проц или память? Если память то уменшите параметры согласно для мускуля, у меня тоже потребшяемый обьем памятимускуля вырос но зато стабильность работы.

S

106

SAnet

6 ноября 2014, 13:08

#19

G-and-Y:
Так грузит проц или память? Если память то уменшите параметры согласно для мускуля, у меня тоже потребшяемый обьем памятимускуля вырос но зато стабильность работы.

Проц грузит

В 2023 году 36,9% всех DDoS-атак пришлось на сферу финансов

Как снизить ДРР до 4,38% и повысить продажи с помощью VK Рекламы