Jump to content

High CPU load on php-fpm7.0


Recommended Posts

Hi, everyone!

Can anybody help me to tune my virtual server? Configuration: 2 cores, 8 Gb, SSD, nginx, PHP 7, Redis. ~80 online users.

CPU average load is 4.03 5.28 5.2, sometimes it can be up to 12...

Снимок экрана 2016-11-06 в 16.23.50.png

pm.max_children = 200
pm.start_servers = 70
pm.min_spare_servers = 60
pm.max_spare_servers = 80
pm.max_requests = 500

 

Link to comment
Share on other sites

pm = dynamic

nginx.conf

user www-data;
worker_processes auto;
pid /run/nginx.pid;

events {
	use epoll;
	worker_connections 1024;
	multi_accept on;
}

http {

	##
	# Basic Settings
	##

	sendfile on;
	tcp_nopush on;
	tcp_nodelay on;
	keepalive_timeout 65s;
	types_hash_max_size 2048;
	server_tokens off;

	reset_timedout_connection on;
	client_body_timeout 10;
	send_timeout 2;

	server_names_hash_bucket_size 64;
	# server_name_in_redirect off;

	include /etc/nginx/mime.types;
	default_type application/octet-stream;

	client_max_body_size 20M;

	##
	# SSL Settings
	##

	ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
	ssl_prefer_server_ciphers on;

	##
	# Logging Settings
	##

	# access_log /var/log/nginx/access.log;
	access_log off;
	error_log /var/log/nginx/error.log crit;

	# Enable gzip compression.
	gzip on;

	# Compression level (1-9).
	# 5 is a perfect compromise between size and CPU usage, offering about
	# 75% reduction for most ASCII files (almost identical to level 9).
	gzip_comp_level    5;

	# Don't compress anything that's already small and unlikely to shrink much
	# if at all (the default is 20 bytes, which is bad as that usually leads to
	# larger files after gzipping).
	gzip_min_length    256;

	# Compress data even for clients that are connecting to us via proxies,
	# identified by the "Via" header (required for CloudFront).
	gzip_proxied       any;

	# Tell proxies to cache both the gzipped and regular version of a resource
	# whenever the client's Accept-Encoding capabilities header varies;
	# Avoids the issue where a non-gzip capable client (which is extremely rare
	# today) would display gibberish if their proxy gave them the gzipped version.
	gzip_vary          on;

	# Compress all output labeled with one of the following MIME-types.
	gzip_types
		application/atom+xml
		application/javascript
		application/json
		application/ld+json
		application/manifest+json
		application/rss+xml
		application/vnd.geo+json
		application/vnd.ms-fontobject
		application/x-font-ttf
		application/x-web-app-manifest+json
		application/xhtml+xml
		application/xml
		font/opentype
		image/bmp
		image/svg+xml
		image/x-icon
		text/cache-manifest
		text/css
		text/plain
		text/vcard
		text/vnd.rim.location.xloc
		text/vtt
		text/x-component
		text/x-cross-domain-policy;
	# text/html is always compressed by gzip module

	##
	# Virtual Host Configs
	##

	include /etc/nginx/conf.d/*.conf;
	include /etc/nginx/sites-enabled/*;
}


#mail {
#	# See sample authentication script at:
#	# http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
#	# auth_http localhost/auth.php;
#	# pop3_capabilities "TOP" "USER";
#	# imap_capabilities "IMAP4rev1" "UIDPLUS";
#
#	server {
#		listen     localhost:110;
#		protocol   pop3;
#		proxy      on;
#	}
#
#	server {
#		listen     localhost:143;
#		protocol   imap;
#		proxy      on;
#	}
#}

mysqltuner output:

[OK] Currently running supported MySQL version 5.7.16-0ubuntu0.16.04.1-log
[OK] Operating on 64-bit architecture
 
-------- Storage Engine Statistics -----------------------------------------------------------------
[--] Status: +ARCHIVE +BLACKHOLE +CSV -FEDERATED +InnoDB +MEMORY +MRG_MYISAM +MyISAM +PERFORMANCE_SCHEMA 
[--] Data in MyISAM tables: 1G (Tables: 2)
[--] Data in InnoDB tables: 8G (Tables: 262)
[OK] Total fragmented tables: 0
 
-------- Security Recommendations ------------------------------------------------------------------
[OK] There are no anonymous accounts for any database users
[OK] All database users have passwords assigned
[--] Bug #80860 MySQL 5.7: Avoid testing password when validate_password is activated
 
-------- CVE Security Recommendations --------------------------------------------------------------
[OK] NO SECURITY CVE FOUND FOR YOUR VERSION
 
-------- Performance Metrics -----------------------------------------------------------------------
[--] Up for: 4h 22m 25s (4M q [261.148 qps], 115K conn, TX: 56G, RX: 1G)
[--] Reads / Writes: 97% / 3%
[--] Binary logging is disabled
[--] Physical Memory     : 7.8G
[--] Max MySQL memory    : 2.2G
[--] Other process memory: 3.4G
[--] Total buffers: 2.1G global + 1.1M per thread (151 max threads)
[--] P_S Max memory usage: 72B
[--] Galera GCache Max memory usage: 0B
[OK] Maximum reached memory usage: 2.1G (27.33% of installed RAM)
[OK] Maximum possible memory usage: 2.2G (28.46% of installed RAM)
[OK] Overall possible memory usage with other process is compatible with memory available
[OK] Slow queries: 0% (1K/4M)
[OK] Highest usage of available connections: 43% (66/151)
[OK] Aborted connections: 0.00%  (2/115490)
[!!] name resolution is active : a reverse name resolution is made for each new connection and can reduce performance
[OK] Query cache is disabled by default due to mutex contention on multiprocessor machines.
[OK] Sorts requiring temporary tables: 0% (477 temp sorts / 355K sorts)
[!!] Joins performed without indexes: 3452
[!!] Temporary tables created on disk: 57% (17K on disk / 29K total)
[OK] Thread cache hit rate: 99% (510 created / 115K connections)
[!!] Table cache hit rate: 0% (416 open / 142K opened)
[OK] Open file limit used: 0% (6/1K)
[OK] Table locks acquired immediately: 98% (6K immediate / 6K locks)
 
-------- Performance schema ------------------------------------------------------------------------
[--] Performance schema is enabled.
[--] Memory used by P_S: 72B
[--] Sys schema is installed.
 
-------- ThreadPool Metrics ------------------------------------------------------------------------
[--] ThreadPool stat is disabled.
 
-------- MyISAM Metrics ----------------------------------------------------------------------------
[!!] Key buffer used: 19.0% (3M used / 16M cache)
[!!] Key buffer size / total MyISAM indexes: 16.0M/764.2M
[!!] Read Key buffer hit rate: 91.5% (8M cached / 752K reads)
[!!] Write Key buffer hit rate: 24.1% (6K cached / 5K writes)
 
-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] InnoDB is enabled.
[--] InnoDB Thread Cucurrency: 0
[OK] InnoDB File per table is activated
[!!] InnoDB buffer pool / data size: 2.0G/8.9G
[!!] Ratio InnoDB log file size / InnoDB Buffer pool size (2.34375 %): 48.0M/2.0G should be equal 25%
[!!] InnoDB buffer pool instances: 8
[--] Number of InnoDB Buffer Pool Chunk : 16 for 8 Buffer Pool Instance(s)
[OK] Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances
[OK] InnoDB Read buffer efficiency: 99.98% (1055516170 hits/ 1055699533 total)
[!!] InnoDB Write Log efficiency: 68.17% (251812 hits/ 369390 total)
[OK] InnoDB log waits: 0.00% (0 waits / 117578 writes)
 
-------- AriaDB Metrics ----------------------------------------------------------------------------
[--] AriaDB is disabled.
 
-------- TokuDB Metrics ----------------------------------------------------------------------------
[--] TokuDB is disabled.
 
-------- XtraDB Metrics ----------------------------------------------------------------------------
[--] XtraDB is disabled.
 
-------- RocksDB Metrics ---------------------------------------------------------------------------
[--] RocksDB is disabled.
 
-------- Spider Metrics ----------------------------------------------------------------------------
[--] Spider is disabled.
 
-------- Connect Metrics ---------------------------------------------------------------------------
[--] Connect is disabled.
 
-------- Galera Metrics ----------------------------------------------------------------------------
[--] Galera is disabled.
 
-------- Replication Metrics -----------------------------------------------------------------------
[--] Galera Synchronous replication: NO
[--] No replication slave(s) for this server.
[--] This is a standalone server.
 
-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
    MySQL started within last 24 hours - recommendations may be inaccurate
    Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
    Adjust your join queries to always utilize indexes
    When making adjustments, make tmp_table_size/max_heap_table_size equal
    Reduce your SELECT DISTINCT queries which have no LIMIT clause
    Increase table_open_cache gradually to avoid file descriptor limits
    Read this before increasing table_open_cache over 64: http://bit.ly/1mi7c4C
    Beware that open_files_limit (1024) variable 
    should be greater than table_open_cache (431)
Variables to adjust:
    join_buffer_size (> 256.0K, or always use indexes with joins)
    tmp_table_size (> 16M)
    max_heap_table_size (> 16M)
    table_open_cache (> 431)
    key_buffer_size (> 764.2M)
    innodb_buffer_pool_size (>= 8G) if possible.
    innodb_log_file_size should be equals to 1/4 of buffer pool size (=512M) if possible.
    innodb_buffer_pool_instances(=2)

 

Link to comment
Share on other sites

You don't have much ram to run easily/fast Innodb :(

 

you may try:

 

pm.max_children = 200
pm.start_servers = 10
pm.min_spare_servers = 5
pm.max_spare_servers = 198
pm.max_requests = 1000

 

join_buffer_size = 768K
tmp_table_size = 128M
max_heap_table_size = 128M
table_open_cache = 16350
key_buffer_size = 800M
innodb_buffer_pool_size = 6G
innodb_buffer_pool_instances=6

restart php and mysql and report back how it goes :)

My values above are a bit high for what you have but after reporting back we will see exactly what it can be done...

But it will be great if you can get a server with higher ram and increase the:

innodb_buffer_pool_size = 9G
innodb_buffer_pool_instances=9

That's a basic recommendation as optimization of php and mysql needs a lot more ....

Link to comment
Share on other sites

1 hour ago, ASTRAPI said:

join_buffer_size = 768K tmp_table_size = 128M max_heap_table_size = 128M table_open_cache = 16350 key_buffer_size = 800M innodb_buffer_pool_size = 6G innodb_buffer_pool_instances=6

 

I put into /etc/mysql/mysql.cnf. So now it looks like this:

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#

!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/mysql.conf.d/

[mysqld]
# innodb_flush_log_at_trx_commit = 2
thread_cache_size                = 16
innodb_flush_method              = O_DIRECT
slow_query_log = 1
slow_query_log_file = /var/log/mysql/slow-queries.log
long_query_time = 1

join_buffer_size = 768K
tmp_table_size = 128M
max_heap_table_size = 128M
table_open_cache = 16350
key_buffer_size = 800M
innodb_buffer_pool_size = 6G
innodb_buffer_pool_instances=6

 

That's so sad that 2 cores and 8 Gb of RAM are not enough for an average forum on PHP...

Link to comment
Share on other sites

Innodb needs more ram.

If you use MyISAM for a small forum it will perform better with a low ram vps...

Does it performs better now after my changes and restarting the php and mysql?

Keep in mind that we try to do some basic settings here just to get it better but for full performance for your vps there are a lot more settings to adjust and if you want super speed then you must avoid shared resources solutions like vps servers....

Link to comment
Share on other sites

Before doing anything else, you need to check your access logs for nginx and make sure you aren't under a random DDOS attack.  I've seen (and helped deal with) several sites that were suffering random WPPingback DDOS attacks.  Also if you have a rogue searchbot hitting you it can run the PHP processes up.

Link to comment
Share on other sites

33 minutes ago, ASTRAPI said:

Does it performs better now after my changes and restarting the php and mysql?

I need more time to check because a day peak has passed a few hours ago.

@Tracy Perry, my forum is very specific and regional, so I don't think it's under DDoS. But by the way currently, I don't have a firewall. Do I need it?

And also my hoster Hetzner claimed DDoS protection included.

Link to comment
Share on other sites

10 minutes ago, motomac said:

I need more time to check because a day peak has passed a few hours ago.

@Tracy Perry, my forum is very specific and regional, so I don't think it's under DDoS. But by the way currently, I don't have a firewall. Do I need it?

And also my hoster Hetzner claimed DDoS protection included.

Doesn't matter your location or that the forum is regional.  Your server is open to the entire world.   There are some groups that use a blackmail technique in that they perform a small DDOS attack against sites and then send an email to the owner of the domain "mentioning" that they were targeted and for a "small fee" they won't target them again.
One of the sites I assisted with this was a very small forum that was just starting.  He just happened to apparently piss someone off that he knew that got mad when he started a competitive site.  Never could "prove" it was him, but from some of the bragging he did, a reasonable person knew who it was.

And yes, if you are running a VPS or a dedi, you need a firewall.  Even with the claims of DDOS protection from your provider you should still utilize one.  I'm with OVH and I still use one.  Not to mention, most of the providers DDOS do not protect against a Layer 7 attack - which the WPPingback one is.

You can find out quickly if it's a WPPingback one by viewing your access logs and doing a grep for WordPress and if you see numerous similar to this 

GET /?4137049=6431829 HTTP/1.0" 403 0 "-" "WordPress/3.8; http://www.mtbgearreview.com"

then you will need to make arrangements to block them.  

If you are using nginx then in your vhost definition for your site you can add 

if ($http_user_agent ~ WordPress) { return 444; }

into the vhost stanza.  That will cause nginx to drop any inbound connections that use the WordPress agent string (which all the WP Pingback attacks do).
The only time this may cause an issue is if you actually have a WordPress site that utilizes them legitimately.

Link to comment
Share on other sites

78.138.164.167 - - [03/Nov/2016:06:37:01 +0100] "GET /forum/113-%D0%B4%D0%BE%D0%BC%D0%B0-%D0%BA%D0%BE%D1%82%D1%82%D0%B5%D0%B4%D0%B6%D0%B8-%D0%B8-%D0%B4%D0%B0%D1%87%D0%B8.xml HTTP/1.1" 404 178 "https://site.ru/forum/113-%D0%B4%D0%BE%D0%BC%D0%B0-%D0%BA%D0%BE%D1%82%D1%82%D0%B5%D0%B4%D0%B6%D0%B8-%D0%B8-%D0%B4%D0%B0%D1%87%D0%B8.xml" "FeedWordPress/2016.0420 (aggregator:feedwordpress; WordPress/4.6.1 + SimplePie/1.3.1; Allow like Gecko; +http://feedwordpress.radgeek.com/) at \xD0\xBD\xD0\xB5\xD1\x82-\xD0\xB0\xD0\xB3\xD0\xB5\xD0\xBD\xD1\x82\xD0\xB0.\xD1\x80\xD1\x84"

362 requests like this for one day. Is it a lot?

Link to comment
Share on other sites

54 minutes ago, motomac said:

78.138.164.167 - - [03/Nov/2016:06:37:01 +0100] "GET /forum/113-%D0%B4%D0%BE%D0%BC%D0%B0-%D0%BA%D0%BE%D1%82%D1%82%D0%B5%D0%B4%D0%B6%D0%B8-%D0%B8-%D0%B4%D0%B0%D1%87%D0%B8.xml HTTP/1.1" 404 178 "https://site.ru/forum/113-%D0%B4%D0%BE%D0%BC%D0%B0-%D0%BA%D0%BE%D1%82%D1%82%D0%B5%D0%B4%D0%B6%D0%B8-%D0%B8-%D0%B4%D0%B0%D1%87%D0%B8.xml" "FeedWordPress/2016.0420 (aggregator:feedwordpress; WordPress/4.6.1 + SimplePie/1.3.1; Allow like Gecko; +http://feedwordpress.radgeek.com/) at \xD0\xBD\xD0\xB5\xD1\x82-\xD0\xB0\xD0\xB3\xD0\xB5\xD0\xBD\xD1\x82\xD0\xB0.\xD1\x80\xD1\x84"

362 requests like this for one day. Is it a lot?

Yeah, but they are using a WordPress feed aggregator and pulling RSS feeds from your site.  I'd probably look at throttling them - especially since the RSS feed they are apparently trying to get is giving a 404 error back to them.

Link to comment
Share on other sites

200 Childrens is overkill for your server. I have tested that many times, for example in a 4 core vps, if i launch an small ddos attack that will use 100 childrens, the site becomes unusable, because it simple can't handle so many php-fpm childrens. I have done the same test with a Dedicated Server from OVH with 12 cores, and it handles it perfectly fine. It all depends on the hardware.

Also, Innodb is very smart, really smart. If you can only give 4Gb to Innodb and your Database is 9GB, there is no real problem, because Innodb will cache the pages that are used the most. In every forum, 99% of the users will only see the new content and not the old content.

Link to comment
Share on other sites

Quote

200 Childrens is overkill for your server.

I agree but i recommend that just to avoid any max children limitations as i think he will not have so much traffic to need all of them and crash the server....

The value of 100 is ok but it is good to check the logs also...

For Innodb i prefer to give equal number of data size as the prices for dedicated servers with huge rams are very low :)

The user has already a few options to test so we can wait and see how it goes ....

Link to comment
Share on other sites

1 hour ago, ASTRAPI said:

but i recommend that just to avoid any max children limitations as i think he will not have so much traffic to need all of them and crash the server.

OOM issues are never nice.  Makes for a dirty shutdown of MySQL quite frequently, and if using MyISAM tables then you have issues.

Link to comment
Share on other sites

It looks like high CPU load happens only in some certain moments. For example, right now I have

Server Load: 1,67 1,62 1,56

and

Who's Online   84 Members, 5 Anonymous, 0 Guests.

Снимок экрана 2016-11-15 в 14.47.17.png

Maybe some events like email sending (postfix) or cron tasks consume a lot of CPU?

P.S. I still don't see any requests related to "wordpress" in access logs.

Link to comment
Share on other sites

Most of entries in php7.0-fpm.log now are:

[20-Nov-2016 19:03:12] NOTICE: [pool www] child 32714 exited with code 0 after 4548.596745 seconds from start
[20-Nov-2016 19:03:12] NOTICE: [pool www] child 1055 started

but sometimes there is something like:

[20-Nov-2016 17:47:13] WARNING: [pool www] child 29493 exited on signal 11 (SIGSEGV) after 15980.167763 seconds from start
[20-Nov-2016 17:47:13] NOTICE: [pool www] child 32559 started
[20-Nov-2016 17:47:13] WARNING: [pool www] child 29328 exited on signal 11 (SIGSEGV) after 16239.157749 seconds from start
[20-Nov-2016 17:47:13] NOTICE: [pool www] child 32562 started
[20-Nov-2016 17:47:13] WARNING: [pool www] child 29506 exited on signal 11 (SIGSEGV) after 15979.287588 seconds from start
[20-Nov-2016 17:47:13] NOTICE: [pool www] child 32570 started
[20-Nov-2016 17:47:13] WARNING: [pool www] child 29555 exited on signal 11 (SIGSEGV) after 15974.307255 seconds from start
[20-Nov-2016 17:47:13] NOTICE: [pool www] child 32581 started
[20-Nov-2016 17:47:13] WARNING: [pool www] child 29329 exited on signal 11 (SIGSEGV) after 16236.967375 seconds from start
[20-Nov-2016 17:47:13] NOTICE: [pool www] child 32583 started
[20-Nov-2016 17:47:13] WARNING: [pool www] child 29447 exited on signal 11 (SIGSEGV) after 15985.580007 seconds from start
[20-Nov-2016 17:47:13] NOTICE: [pool www] child 32584 started
[20-Nov-2016 17:47:13] WARNING: [pool www] child 29416 exited on signal 11 (SIGSEGV) after 15988.605189 seconds from start
[20-Nov-2016 17:47:13] NOTICE: [pool www] child 32585 started
[20-Nov-2016 17:47:13] WARNING: [pool www] child 29404 exited on signal 11 (SIGSEGV) after 15989.618626 seconds from start
[20-Nov-2016 17:47:13] NOTICE: [pool www] child 32586 started
[20-Nov-2016 17:47:14] WARNING: [pool www] child 31530 exited on signal 11 (SIGSEGV) after 4959.847799 seconds from start
[20-Nov-2016 17:47:14] NOTICE: [pool www] child 32589 started
[20-Nov-2016 17:47:14] WARNING: [pool www] child 29422 exited on signal 11 (SIGSEGV) after 15987.748278 seconds from start
[20-Nov-2016 17:47:14] WARNING: failed processes threshold (10 in 60 sec) is reached, initiating reload
[20-Nov-2016 17:47:15] NOTICE: reloading: execvp("/usr/sbin/php-fpm7.0", {"/usr/sbin/php-fpm7.0", "--nodaemonize", "--fpm-config", "/etc/php/7.0/fpm/php-fpm.conf"})
[20-Nov-2016 17:47:15] NOTICE: using inherited socket fd=8, "/run/php/php7.0-fpm.sock"
[20-Nov-2016 17:47:15] NOTICE: using inherited socket fd=8, "/run/php/php7.0-fpm.sock"
[20-Nov-2016 17:47:15] NOTICE: fpm is running, pid 18497
[20-Nov-2016 17:47:15] NOTICE: ready to handle connections
[20-Nov-2016 17:47:15] NOTICE: systemd monitor interval set to 10000ms
[20-Nov-2016 17:47:15] WARNING: [pool www] child 32616 exited on signal 11 (SIGSEGV) after 0.163030 seconds from start
[20-Nov-2016 17:47:15] NOTICE: [pool www] child 32620 started
[20-Nov-2016 17:47:15] WARNING: [pool www] child 32609 exited on signal 11 (SIGSEGV) after 0.188494 seconds from start
[20-Nov-2016 17:47:15] NOTICE: [pool www] child 32621 started
[20-Nov-2016 17:47:15] WARNING: [pool www] child 32612 exited on signal 11 (SIGSEGV) after 0.220964 seconds from start
[20-Nov-2016 17:47:15] NOTICE: [pool www] child 32622 started
[20-Nov-2016 17:47:16] WARNING: [pool www] child 32611 exited on signal 11 (SIGSEGV) after 0.402830 seconds from start
[20-Nov-2016 17:47:16] NOTICE: [pool www] child 32623 started
[20-Nov-2016 17:47:16] WARNING: [pool www] child 32614 exited on signal 11 (SIGSEGV) after 0.441524 seconds from start
[20-Nov-2016 17:47:16] NOTICE: [pool www] child 32624 started
[20-Nov-2016 17:47:16] WARNING: [pool www] child 32623 exited on signal 11 (SIGSEGV) after 0.119896 seconds from start
[20-Nov-2016 17:47:16] NOTICE: [pool www] child 32625 started
[20-Nov-2016 17:47:16] WARNING: [pool www] child 32619 exited on signal 11 (SIGSEGV) after 0.488761 seconds from start
[20-Nov-2016 17:47:16] NOTICE: [pool www] child 32626 started
[20-Nov-2016 17:47:16] WARNING: [pool www] child 32617 exited on signal 11 (SIGSEGV) after 0.711754 seconds from start
[20-Nov-2016 17:47:16] NOTICE: [pool www] child 32629 started
[20-Nov-2016 17:47:16] WARNING: [pool www] child 32622 exited on signal 11 (SIGSEGV) after 0.677355 seconds from start
[20-Nov-2016 17:47:16] NOTICE: [pool www] child 32630 started
[20-Nov-2016 17:47:16] WARNING: [pool www] child 32626 exited on signal 11 (SIGSEGV) after 0.399369 seconds from start
[20-Nov-2016 17:47:16] WARNING: failed processes threshold (10 in 60 sec) is reached, initiating reload
[20-Nov-2016 17:47:16] NOTICE: reloading: execvp("/usr/sbin/php-fpm7.0", {"/usr/sbin/php-fpm7.0", "--nodaemonize", "--fpm-config", "/etc/php/7.0/fpm/php-fpm.conf"})
[20-Nov-2016 17:47:16] NOTICE: using inherited socket fd=8, "/run/php/php7.0-fpm.sock"
[20-Nov-2016 17:47:16] NOTICE: using inherited socket fd=8, "/run/php/php7.0-fpm.sock"
[20-Nov-2016 17:47:16] NOTICE: fpm is running, pid 18497
[20-Nov-2016 17:47:16] NOTICE: ready to handle connections
[20-Nov-2016 17:47:16] NOTICE: systemd monitor interval set to 10000ms
[20-Nov-2016 17:47:16] WARNING: [pool www] child 32638 exited on signal 11 (SIGSEGV) after 0.140971 seconds from start
[20-Nov-2016 17:47:16] NOTICE: [pool www] child 32641 started
[20-Nov-2016 17:47:17] WARNING: [pool www] child 32636 exited on signal 11 (SIGSEGV) after 0.215062 seconds from start
[20-Nov-2016 17:47:17] NOTICE: [pool www] child 32642 started
[20-Nov-2016 17:47:17] WARNING: [pool www] child 32641 exited on signal 11 (SIGSEGV) after 0.457725 seconds from start
[20-Nov-2016 17:47:17] NOTICE: [pool www] child 32657 started
[20-Nov-2016 17:47:17] WARNING: [pool www] child 32637 exited on signal 11 (SIGSEGV) after 0.993108 seconds from start
[20-Nov-2016 17:47:17] NOTICE: [pool www] child 32662 started
[20-Nov-2016 17:47:17] WARNING: [pool www] child 32640 exited on signal 11 (SIGSEGV) after 1.006668 seconds from start
[20-Nov-2016 17:47:17] NOTICE: [pool www] child 32663 started
[20-Nov-2016 17:47:17] WARNING: [pool www] child 32634 exited on signal 11 (SIGSEGV) after 1.100500 seconds from start
[20-Nov-2016 17:47:17] NOTICE: [pool www] child 32664 started
[20-Nov-2016 17:47:18] WARNING: [pool www] child 32632 exited on signal 11 (SIGSEGV) after 1.378146 seconds from start
[20-Nov-2016 17:47:18] NOTICE: [pool www] child 32665 started
[20-Nov-2016 17:47:18] WARNING: [pool www] child 32635 exited on signal 11 (SIGSEGV) after 1.384378 seconds from start
[20-Nov-2016 17:47:18] NOTICE: [pool www] child 32666 started
[20-Nov-2016 17:47:18] WARNING: [pool www] child 32631 exited on signal 11 (SIGSEGV) after 1.392042 seconds from start
[20-Nov-2016 17:47:18] NOTICE: [pool www] child 32667 started
[20-Nov-2016 17:47:18] WARNING: [pool www] child 32642 exited on signal 11 (SIGSEGV) after 1.716617 seconds from start
[20-Nov-2016 17:47:18] WARNING: failed processes threshold (10 in 60 sec) is reached, initiating reload
[20-Nov-2016 17:47:18] NOTICE: reloading: execvp("/usr/sbin/php-fpm7.0", {"/usr/sbin/php-fpm7.0", "--nodaemonize", "--fpm-config", "/etc/php/7.0/fpm/php-fpm.conf"})
[20-Nov-2016 17:47:18] NOTICE: using inherited socket fd=8, "/run/php/php7.0-fpm.sock"
[20-Nov-2016 17:47:18] NOTICE: using inherited socket fd=8, "/run/php/php7.0-fpm.sock"
[20-Nov-2016 17:47:18] NOTICE: fpm is running, pid 18497
[20-Nov-2016 17:47:18] NOTICE: ready to handle connections
[20-Nov-2016 17:47:18] NOTICE: systemd monitor interval set to 10000ms
[20-Nov-2016 17:47:18] WARNING: [pool www] child 32670 exited on signal 11 (SIGSEGV) after 0.074567 seconds from start
[20-Nov-2016 17:47:18] NOTICE: [pool www] child 32680 started
[20-Nov-2016 17:47:19] WARNING: [pool www] child 32671 exited on signal 11 (SIGSEGV) after 0.172228 seconds from start
[20-Nov-2016 17:47:19] NOTICE: [pool www] child 32681 started
[20-Nov-2016 17:47:19] WARNING: [pool www] child 32674 exited on signal 11 (SIGSEGV) after 0.340762 seconds from start
[20-Nov-2016 17:47:19] NOTICE: [pool www] child 32682 started
[20-Nov-2016 17:47:19] WARNING: [pool www] child 32676 exited on signal 11 (SIGSEGV) after 0.532094 seconds from start
[20-Nov-2016 17:47:19] NOTICE: [pool www] child 32683 started
[20-Nov-2016 17:47:19] WARNING: [pool www] child 32675 exited on signal 11 (SIGSEGV) after 0.574432 seconds from start
[20-Nov-2016 17:47:19] NOTICE: [pool www] child 32684 started

and

[20-Nov-2016 13:20:44] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 42 total children
[20-Nov-2016 13:20:45] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 0 idle, and 47 total children
[20-Nov-2016 13:20:46] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 52 total children
[20-Nov-2016 13:20:47] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 57 total children
[20-Nov-2016 13:20:48] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 62 total children
[20-Nov-2016 13:20:49] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 67 total children
[20-Nov-2016 13:20:50] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 72 total children
[20-Nov-2016 13:20:51] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 77 total children
[20-Nov-2016 13:20:52] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 82 total children
[20-Nov-2016 13:20:53] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 87 total children
[20-Nov-2016 13:20:54] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 92 total children
[20-Nov-2016 13:20:55] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 97 total children
[20-Nov-2016 13:20:56] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 102 total children
[20-Nov-2016 13:20:57] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 107 total children
[20-Nov-2016 13:20:58] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 112 total children
[20-Nov-2016 13:20:59] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 117 total children
[20-Nov-2016 13:21:00] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 122 total children
[20-Nov-2016 13:21:01] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 127 total children
[20-Nov-2016 13:21:02] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 132 total children
[20-Nov-2016 13:21:03] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 137 total children
[20-Nov-2016 13:21:04] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 4 idle, and 142 total children

What does it mean and what should I do?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...