So this message can be interpreted:
> NOTICE: [pool www] child 25826 exited with code 0 after 864.048588 seconds
> from start
The code 0 means that the child exited normally 864 seconds after it had
started. In other words,
it chose to die (probably after serving 800 or 2500 requests).
Now if
I forget to mention. during night, there wont be any visitors. It is only
for specific regions. website will be busy during the morning time.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,276892,276910#msg-276910
___
nginx mailing list
ngin
I am getting these kind of warning in php fpm log
NOTICE: [pool www] child 25826 exited with code 0 after 864.048588 seconds
from start
NOTICE: [pool www] child 6580 started
Sir, I am still looking for a way to monitor nginx performance. But i am not
able to find the solution in internet.
Can you
php fpm status
pool: www
process manager: dynamic
start time: 17/Oct/2017:00:55:44 -0400
start since: 2077
accepted conn:183360
listen queue: 0
max listen queue: 0
listen queue len: 0
idle processes: 28
active processes: 3
t
Sir reading some info, i guess i cant tell any number blindly without test.
I think
I can first try to give these values
max_children = 100
start server = 34
spareserver min and max = 20 & 50
We have around 20GB free Ram all the time. Why can't we use it for php-fpm?
Are those values safe to c
Agree,
Can you email me offline. I might have a few ideas on how to assist.
Peter
peter _ booth @ me.com
> On Oct 16, 2017, at 3:55 PM, agriz wrote:
>
> Sir,
>
> Thank you for your reply.
>
> This is a live server.
> It is an NPO (non profit organisation).
> I pay for the server and maint
I am in the field now.
I asked my friend to get the info you asked.
This is what i received
php-fpm is using unix sockets (I know this. I configured this)
tcp0 0 TIME_WAIT
tcp0 0 TIME_WAIT
tcp0 0 TIME_WAIT
tcp0 0 ESTABLI
We should see memory and cpu for this server. I suspect a variety of issues.
Is php-fpm using a Unix socket with Nginx? That would help you remove tcp
sockets internally.
This likely needs to be much higher but depends on your hardware, cpu/memory.
Maybe 500?
pm.max_children = 50
The below
Sir,
Thank you for your reply.
This is a live server.
It is an NPO (non profit organisation).
I pay for the server and maintaining it. We cant afford to a admin.
It will be a great help if you can solve this.
People are visiting for registering complains and viewing our activity.
all php pages a
You said this
> On Oct 16, 2017, at 3:30 PM, Peter Booth wrote:
>
> If i change the values, it hangs with 3k or 5k visitors.
> This one handle 5k to 8k
what hangs? the host or the nginx worker processes or the PHP or the mysql?
You need to capture some diagnostic information over time to see wh
Advice
- instead of tweaking values, first work out what is happening,
locate the bottleneck, then try adjusting things when you have a theory
First QN you need to answer:
For your test, is your system as a whole overloaded?
As in, for he duration of the test is the #req/se supported constant?
worker_processes 4;
worker_rlimit_nofile 4;
events {
worker_connections 4096;
#accept_mutex on;
#accept_mutex_delay 500ms;
multi_accept on;
use epoll;
}
pm.max_children = 50
pm.start_servers = 4
pm.min_spare_servers = 4
pm.max_spare_servers = 32
pm.max_requests = 2500 //m
Try to change pm.max_requests up to 2048.
To much pm.max_children = 400
2017-10-16 20:52 GMT+03:00 agriz :
> Reduced to 4k visitors from 10k :(
>
> Posted at Nginx Forum: https://forum.nginx.org/read.
> php?2,276892,276898#msg-276898
>
> ___
> nginx mai
Reduced to 4k visitors from 10k :(
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,276892,276898#msg-276898
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Just start with the default ones.
Verstuurd vanaf mijn iPhone
> Op 16 okt. 2017 om 19:32 heeft agriz het
> volgende geschreven:
>
> Sir,
>
> Can you give me a rough values?
> I will play with them.
>
> Posted at Nginx Forum:
> https://forum.nginx.org/read.php?2,276892,276896#msg-276896
>
>
Sir,
Can you give me a rough values?
I will play with them.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,276892,276896#msg-276896
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Maybe lower fpm specs and raise nginx spec?
Verstuurd vanaf mijn iPhone
> Op 16 okt. 2017 om 18:59 heeft agriz het
> volgende geschreven:
>
> PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
> 22093 nginx 20 0 393060 11848 3828 S 31.9 0.0 10:17.70 php-fpm:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
22093 nginx 20 0 393060 11848 3828 S 31.9 0.0 10:17.70 php-fpm:
pool www
1495 mysql 20 0 4793852 318444 9824 S 23.6 1.0 796:41.59
/usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql
--plugin-di
How many core do you have?
On Oct 16, 2017 19:37, "agriz" wrote:
> I am struggling to handle a traffic of 10K+ It will reach a lot. But my bad
> configuration is limiting them.
>
> www.conf
>
> pm.max_children = 400
> pm.start_servers = 40
> pm.min_spare_servers = 40
> pm.max_spare_servers = 70
I am struggling to handle a traffic of 10K+ It will reach a lot. But my bad
configuration is limiting them.
www.conf
pm.max_children = 400
pm.start_servers = 40
pm.min_spare_servers = 40
pm.max_spare_servers = 70
pm.max_requests = 800
nginx.conf
worker_processes 3;
events {
worker_connecti
On Sunday 15 October 2017 09:51:27 Ruben wrote:
> When setting max_fails=0 for all server directives used in upstream module.
> So for example:
>
> upstream chat-servers {
> hash $arg_chatName;
> server chat-1 max_fails=0;
> server chat-2 max_fails=0;
> server chat-3 max_fails=0;
> }
>
>
Hello!
On Mon, Oct 16, 2017 at 11:29:57AM -0400, Charles Orth via nginx wrote:
> Do we know when the next stable version is schedule to be released using
> 1.13 code base?
Next stable branch, 1.14.x, based on 1.13.x mainline, is expected
to appear around next April, as usual.
Next stable versi
On 16/10/2017 18:29, Charles Orth via nginx wrote:
> Hi Folks,
>
> Do we know when the next stable version is schedule to be released
> using 1.13 code base?
>
You can use April 2018 as a good estimation for 1.13 -> 1.14 switchover.
Just in case: it is ok to use -mainline in production.
--
Max
Hi Folks,
Do we know when the next stable version is schedule to be released using
1.13 code base?
Charles
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
24 matches
Mail list logo