Hello!
On Wed, Mar 21, 2018 at 05:52:20AM -0400, Grzegorz Ćwikliński wrote:
> As you said before killing nginx worker is connected with third party module
> which is Linux kernel Out Of Memory killer.
>
> Because nginx is using too much memory OOM killer score is about 800-900
> point where 10
Hello,
As you said before killing nginx worker is connected with third party module
which is Linux kernel Out Of Memory killer.
Because nginx is using too much memory OOM killer score is about 800-900
point where 1000 is maximum, which is why kernel is killing out nginx
worker, and after that f
Hello!
On Wed, Feb 28, 2018 at 05:22:14AM -0500, Andrzej Walas wrote:
> Can you answer?
The last recommendation you were given is to find out who and why
killed nginx worker process, see here:
http://mailman.nginx.org/pipermail/nginx/2018-February/055648.html
If you think nginx processes are
Can you answer?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,278589,278826#msg-278826
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi,
I don't use 3rd party modules. After update to 1.13.8 I have still many logs
like this:
[alert] 704#704: ignore long locked inactive cache entry
1ee9fd62b649e731d69f56b98e3e58a5, count:28
Sometimes:
[error] 5466#5466: *168740 readv() failed (104: Connection reset by peer)
while reading upstre
Hello!
On Mon, Feb 19, 2018 at 04:38:00AM -0500, Andrzej Walas wrote:
> Thanks for your replay I will update nginx I search again.
>
> Can you anwser on my couple questions:
> 1. Can you tell me what happend with downloaded part of files when I have:
> 1.1 [error] 16082#0: *1264804 upstream prem
Thanks for your replay I will update nginx I search again.
Can you anwser on my couple questions:
1. Can you tell me what happend with downloaded part of files when I have:
1.1 [error] 16082#0: *1264804 upstream prematurely closed connection while
reading upstream
1.2 [crit] 16082#0: *1264770 pwri
Hello!
On Fri, Feb 16, 2018 at 03:16:27AM -0500, Andrzej Walas wrote:
> After this inactive logs I have anther logs:
> [alert] 11371#0: worker process 24870 exited on signal 9
Signal 9 is SIGKILL sent to the nginx worker process. Killing
nginx worker processes will obviously result in various
Can you answer on this:
> Can you tell me what happend with downloaded part of files when I have:
> [error] 16082#0: *1264804 upstream prematurely closed connection while
> reading upstream
> [crit] 16082#0: *1264770 pwritev() has written only 49152 of
151552
> while reading upstream
> This part o
> [alert] 11371#0: worker process 24870 exited on signal 9
This is almost certainly the cause of your problems - you need to figure
out why the nginx processes are crashing and resolve that. Most likely a
3rd party module is responsible.
On Fri, Feb 16, 2018 at 10:39 AM, Andrzej Walas wrote:
>
For me 40-50 GB cache is ok, because I have multiple files like 2-5GB.
Problem in my mind is this that I have settings:
proxy_cache_path /ephemeral/nginx/cache levels=1:2
keys_zone=proxy-cache:4000m max_size=40g inactive=1d;
but I have over 40GB on disc and files older than 1 day inact
100GB of cached files sounds enormous. What kinds of files are you caching? How
large are they? How many do you have?
If you look at your access log what hit rate is your cache seeing?
Sent from my iPad
> On Feb 16, 2018, at 3:16 AM, Andrzej Walas
> wrote:
>
> After this inactive logs I have
After this inactive logs I have anther logs:
[alert] 11371#0: worker process 24870 exited on signal 9
Can you explain whats happend when I have logs like this:
[error] 9045#0: *1138267 readv() failed (104: Connection reset by peer)
while reading upstream...
I have problem like https://forum.nginx
Hello!
On Thu, Feb 15, 2018 at 08:48:11AM -0500, Andrzej Walas wrote:
> Thanks for answer. In logs I see couple logs like this:
> [alert] 11373#0: ignore long locked inactive cache entry
> dba676c7ebb90e210efc04d51aaa4858, count:11
This message indicate that the cache entry in question was
was l
Thanks for answer. In logs I see couple logs like this:
[alert] 11373#0: ignore long locked inactive cache entry
dba676c7ebb90e210efc04d51aaa4858, count:11
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,278589,278600#msg-278600
___
nginx mai
Hello!
On Thu, Feb 15, 2018 at 04:33:19AM -0500, Andrzej Walas wrote:
> Hi,
>
> I use nginx 1.12.2. I have settings like this:
> proxy_cache_path /ephemeral/nginx/cache levels=1:2
> keys_zone=proxy-cache:4000m max_size=40g inactive=1d;
> proxy_temp_path /ephemeral/ngin
Hi,
I use nginx 1.12.2. I have settings like this:
proxy_cache_path /ephemeral/nginx/cache levels=1:2
keys_zone=proxy-cache:4000m max_size=40g inactive=1d;
proxy_temp_path /ephemeral/nginx/tmp;
And I have two problems with this:
1. If during the download to the cache th
17 matches
Mail list logo
