php fpm monitoring

First, the pool of PHP-FPM The PHP-FPM configuration file php-fpm.conf can be set to multiple pool, where one pool resource is exhausted, causing other sites to be unable to access resources, reporting a 502 error. It is necessary to

The pool of PHP-FPMPHP-FPM configuration file php-fpm.conf can set multiple pool, in which one pool resource is exhausted, will cause other sites to not access resources, reported 502 error. It is necessary to separate the sites, using separate pool

On several offline servers that are not very busy, the number of PHP-FPM processes is found to be more than 500, and some processes run for several months. The following troubleshooting was performed to determine if there is a problem with the

How to Use the supervisor to guard the main php-fpm process for Automatic Restart of php-fpm, supervisorphp-fpm Recently, a colleague has a monitoring requirement for the php-fpm process, that is, if the master process of the php-fpm unexpectedly

Php-fpm startup ?????? Php5.3.3 the source code starts to contain php-fpm. you don't need to fix it any more. you just need to unlock the source code and directly configure it, for php-fpm compilation parameters,-enable-fpm-with-fpm-user =

PHP-FPM configuration and usage summary, php-fpm configuration Summary Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.   PHP-FPM configuration and use

Recently, a colleague has a guardianship requirement for the PHP-FPM process, i.e. if the master process of PHP-FPM quits unexpectedly (possibly crash, it could be a false kill), then the master process is expected to be pulled automatically to

First, process tracking The code is as follows Copy Code # Top//Find process PID with high CPU usage# Strace-p PID//tracking process# LL/PROC/PID/FD//See which files the process is working on There will be

Recently, a colleague has a guardianship requirement for the PHP-FPM process, i.e. if the master process of PHP-FPM quits unexpectedly (possibly crash, it could be a false kill), then the master process is expected to be pulled automatically to

Fault detection1. Other first, top look at the CPU, RAM, swap which is more tense.By analysis, you can see a total of 602 processes, of which 601 processes hibernate. This seems to be something wrong, the kernel process is about 80, plus memcached,