Re: RE: Possible memory leak?

Thanks Reinis! That's some really great info and from the short tests that I've run so far I think this is going to be the solution. I used this command as the test: pid="$(cat /run/nginx.pid)"; kill -USR2 $pid; sleep 10; kill -QUIT $pid And here is what happened with the reload: 37.0 MiB + 1

Re: Possible memory leak?

That should do it, AFAIK a process cannot give back memory already allocated to the system. I would be more than interested to know more about a different technique that doesn't involve a fork system call. Em quinta-feira, 28 de fevereiro de 2019 19:28:00 BRT, Reinis Rozitis escreveu:

RE: Possible memory leak?

> My question still stands though, is there a way to solve that particular > issue? It is > causing us problems when the ram that Nginx is using doubles. Theoretically if that’s a problem you could instead of a reload send USR2 and QUIT to the nginx process (http://nginx.org/en/docs/control.html

RE: Rewrite does not work

> > I've added the following rewrite line in the Config website: > > rewrite ^tagged\/(.*)$ /?p=blog&blog_tag_name=$1 break; > > It is supposedly called by the following URL: /tagged/Server be redirected to > the > following internally: /blog?blog_name=&blog_tag_name=Server If the rewrite dir

Re: Possible memory leak?

Thanks Maxim! I really appreciate your time! As for what I was referring to a memory leak, I guess I'm just referring to the effects I'm seeing across a number of systems with highly different configurations. I'm not an expert so I'll defer to you on that. :) My question still stands though, i

Re: Possible memory leak?

Hello! On Thu, Feb 28, 2019 at 03:54:24PM -0500, wkbrad wrote: > Maxim Dounin Wrote: > --- > > so allocator will not be able to release no-longer-needed > > memory (previously used by the original configuration) to the > > system. > > Thanks

Rewrite does not work

Hello forum members, I have the following problem and I hope someone can help me. I've added the following rewrite line in the Config website: rewrite ^tagged\/(.*)$ /?p=blog&blog_tag_name=$1 break; It is supposedly called by the following URL: /tagged/Server be redirected to the following int

Re: Possible memory leak?

Maxim Dounin Wrote: --- > so allocator will not be able to release no-longer-needed > memory (previously used by the original configuration) to the > system. Thanks Maxim! That sounds like the very definition of a memory leak to me. :) But I

Re: Possible memory leak?

Hello! On Thu, Feb 28, 2019 at 01:43:18PM -0500, wkbrad wrote: > We're running Nginx version 1.15.8 but we've been seeing similar issues with > other versions too and on all of our servers that have a high number of > vhosts. > > The issue is that when you do an nginx reload it ends up using alm

Possible memory leak?

We're running Nginx version 1.15.8 but we've been seeing similar issues with other versions too and on all of our servers that have a high number of vhosts. The issue is that when you do an nginx reload it ends up using almost 2x the ram as it was previously. Here is a test I ran. ---

Re: question about not found

> On 28 Feb 2019, at 15:53, Maxim Dounin wrote: > > Hello! > > On Thu, Feb 28, 2019 at 03:30:22PM +0200, Christos Chatzaras wrote: > >>> On 28 Feb 2019, at 15:06, Christos Chatzaras wrote: >>> On 28 Feb 2019, at 14:47, Christos Chatzaras wrote: If I try to visit an image t

Re: question about not found

Hello! On Thu, Feb 28, 2019 at 03:30:22PM +0200, Christos Chatzaras wrote: > > On 28 Feb 2019, at 15:06, Christos Chatzaras wrote: > > > >> On 28 Feb 2019, at 14:47, Christos Chatzaras wrote: > >> > >> If I try to visit an image that doesn't exist I get: > >> > >> "404 Not Found" > >> > >>

Re: question about not found

> On 28 Feb 2019, at 15:06, Christos Chatzaras wrote: > > > >> On 28 Feb 2019, at 14:47, Christos Chatzaras wrote: >> >> If I try to visit an image that doesn't exist I get: >> >> "404 Not Found" >> >> If I add a location / { } then I get: >> >> "File not found" >> >> In both cases usi

Re: question about not found

> On 28 Feb 2019, at 14:47, Christos Chatzaras wrote: > > If I try to visit an image that doesn't exist I get: > > "404 Not Found" > > If I add a location / { } then I get: > > "File not found" > > In both cases using curl -I http://www.example.com/image.png >

question about not found

If I try to visit an image that doesn't exist I get: "404 Not Found" If I add a location / { } then I get: "File not found" In both cases using curl -I http://www.example.com/image.png I get: HTTP/1.1 404 Not Found Server: nginx Date: Thu, 28 Feb 2019 12:46:

Nginx front-end and back-end socket details

Hi, Is there a way to get back-end service socket details matching to each front-end? My requirement is; User(78.12.34.12) connects to Nginx(23.34.12.53:80) Then Nginx(172.16.2.2) connects to back-end service(172.16.2.3:8080) How can I get above socket details, by filtering front-end socket,