>
> My advice is :
>
>  - try to use TCP/IP for communication between FPM and NginX

I read that UNIX socket is better.

On Thu, Jul 26, 2018 at 4:05 PM, Georgi Naplatanov <go...@oles.biz> wrote:
> On 07/26/2018 03:37 PM, Gokan Atmaca wrote:
>>> Can you attach your PHP-FPM configuration file and NginX virtual host
>>> section for the site?
>>
>> Hello
>>
>> Debian stable (strech).
>>
>> packages:
>>  php7.2-fpm
>> 7.2.6-1+0~20180611145758.22+stretch~1.gbpe20e8b     amd64
>> server-side, HTML-embedded scripting language (FPM-CGI binary)
>> nginx                           1.10.3-1+deb9u1
>>              all          small, powerful, scalable web/proxy server
>>
>> Fpm config:
>>
>> [www]
>> user = www-data
>> group = www-data
>> listen = /run/php/php7.2-fpm.sock
>> listen.owner = www-data
>> listen.group = www-data
>> pm = dynamic
>> pm.max_children = 5000
>> pm.start_servers = 4000
>> pm.min_spare_servers = 4000
>> pm.max_spare_servers = 50> --- Nginx config:
>
> The configuration is set for very high load. You've used Unix sockets.
>
> My advice is :
>
>  - try to use TCP/IP for communication between FPM and NginX
>
> Kind regards
> Georgi
>
>>
>> server {
>>     listen 80;
>>
>>     root /home/website/;
>>     index index.php index.html index.htm;
>>     client_max_body_size 256M;
>>     server_name yyyyy.br
>>
>>
>>
>> location = /favicon.ico {
>>                 log_not_found off;
>>                 access_log off;
>>        }
>>
>>
>> if ($http_user_agent ~* LWP::Simple|wget|libwww-perl) {
>>               return 403;
>>      }
>>
>>
>> location ~* \.(?:jpg|jpeg|gif|png|ico|cur|gz|svg|svgz|mp4|ogg|ogv|webm|htc)$ 
>> {
>>      expires 365d;
>>      add_header Cache-Control "public";
>>    }
>>
>>
>> location ~* \.(?:css|js)$ {
>>   expires 1y;
>>   access_log off;
>>   add_header Cache-Control "public";
>> }
>>
>>
>>  location / {
>>             try_files $uri $uri/ /index.php?q=$uri&$args;
>>
>>
>>         }
>>
>> location /my{
>>      allow x.x.x.x;
>>      allow x.x.x.x;
>>      if ($scheme = http) {  return 301 https://$host$request_uri;}
>>      deny all;
>>      error_page 403  error403.html;
>>      try_files $uri $uri/ /index.php?q=$uri&$args;
>> }
>>
>>  location ~ \.php$ {
>>                 try_files $uri =404;
>>                 fastcgi_split_path_info ^(.+\.php)(/.+)$;
>>                 fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
>>                 fastcgi_index index.php;
>>                 fastcgi_param SCRIPT_FILENAME $request_filename;
>>                 include fastcgi_params;
>>         }
>>
>> gzip on;
>> gzip_disable "msie6";
>> gzip_comp_level 9;
>> gzip_min_length 1100;
>> gzip_buffers 16 8k;
>> gzip_proxied any;
>> gzip_types
>>     text/plain
>>     text/css
>>     text/js
>>     text/xml
>>     text/javascript
>>     application/javascript
>>     application/x-javascript
>>     application/json
>>     application/xml
>>     application/xml+rss;
>>
>> On Thu, Jul 26, 2018 at 2:56 PM, Georgi Naplatanov <go...@oles.biz> wrote:
>>> On 07/26/2018 12:45 PM, Gokan Atmaca wrote:
>>>>> What happened after you did what the warning message suggested to do?
>>>>
>>>> 502 gateway timeout
>>>
>>> Can you attach your PHP-FPM configuration file and NginX virtual host
>>> section for the site?
>>>
>>> Which Debian branch are you using - stable, testing or unstable? Where
>>> did you get PHP 7.2 packages from ?
>>>
>>> Kind regards
>>> Georgi
>>>
>>>> On Thu, Jul 26, 2018 at 11:50 AM, Markus Schönhaber
>>>> <debian-u...@list-post.mks-mail.de> wrote:
>>>>> Gokan Atmaca, Do 26 Jul 2018 08:46:46 CEST:
>>>>>
>>>>>> we are receiving an error as below. what is the cause of the problem?
>>>>>> (32g ram , 240g ssd , xeon 8 cor cpu)
>>>>>>
>>>>>> WARNING: [pool www] seems busy (you may need to increase
>>>>>> pm.start_servers, or pm.min/max_spare_servers), spawning 32 children,
>>>>>> there are 1 idle, and 143 total children
>>>>>
>>>>> What happened after you did what the warning message suggested to do?
>>>>>
>>>>> --
>>>>> Regards
>>>>>   mk
>>>>>
>>>>
>>>
>

Reply via email to