Proxy_cache_path growing beyond max_size

Hi,

I’ve read documentation about proxy_cache_path, proxy_temp_path and
client_body_temp_path directives but I’m a bit confused about proxy
cache size and clean up cache manager process. Using tools like skipfish
to test website security give me lot of 404 errors, which is a normal,
but setting proxy_cache_valid to a tiny value, around 1m, always causes
cache increased beyond limits. So, here is my settings:

proxy_cache_path /var/cache/proxy/proxy_cache levels=2:2:2
keys_zone=cache_local:2m max_size=200m inactive=1d;
client_body_temp_path /var/cache/proxy/client_body_temp 2 2 2
proxy_temp_path /var/cache/proxy/proxy_temp 2 2 2;

proxy_cache_path always grows above 200m and fill up entire FS until it
runs out of space. Is cache manager process should keep it with enough
space, right? What am I doing wrong ?

Regards.

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,214067,214067#msg-214067

morpheu Wrote:

So, here is my settings:
up entire FS until it runs out of space. Is cache
manager process should keep it with enough space,
right? What am I doing wrong ?

Regards.

I’ve been seeing this today aswell. The cache manager process isn’t
running.

2011/08/24 15:50:20 [notice] 10723#0: signal 1 (SIGHUP) received,
reconfiguring
2011/08/24 15:50:20 [notice] 10723#0: reconfiguring
2011/08/24 15:50:20 [notice] 10723#0: using the “epoll” event method
2011/08/24 15:50:20 [notice] 10723#0: start worker processes
2011/08/24 15:50:20 [notice] 10723#0: start worker process 14266
2011/08/24 15:50:20 [notice] 10723#0: start worker process 14267
2011/08/24 15:50:20 [notice] 10723#0: start cache manager process 14268
2011/08/24 15:50:20 [alert] 14268#0: epoll_ctl(1, 0) failed (1:
Operation not permitted)
2011/08/24 15:50:20 [alert] 14268#0: failed to register channel handler
while initializing push module worker (1: Operation not permitted)
2011/08/24 15:50:20 [notice] 10723#0: start cache loader process 14269
2011/08/24 15:50:21 [notice] 13923#0: gracefully shutting down
2011/08/24 15:50:21 [notice] 13924#0: gracefully shutting down
2011/08/24 15:50:20 [alert] 14269#0: epoll_ctl(1, 0) failed (1:
Operation not permitted)
2011/08/24 15:50:20 [alert] 14269#0: failed to register channel handler
while initializing push module worker (1: Operation not permitted)
2011/08/24 15:50:21 [notice] 10723#0: signal 17 (SIGCHLD) received
2011/08/24 15:50:21 [notice] 10723#0: cache manager process 14268 exited
with code 2
2011/08/24 15:50:21 [alert] 10723#0: cache manager process 14268 exited
with fatal code 2 and can not be respawn
2011/08/24 15:50:21 [notice] 10723#0: signal 17 (SIGCHLD) received
2011/08/24 15:50:21 [notice] 10723#0: cache loader process 14269 exited
with code 2
2011/08/24 15:50:21 [notice] 10723#0: signal 29 (SIGIO) received

proxy_cache_path /var/www/cache/downloads levels=1:1:1
keys_zone=downloads:1m max_size=6144m inactive=45m;
proxy_cache_valid 200 25m;
proxy_cache_valid 404 1m;

What’s really quite odd is the disk usage doesn’t just go up, it goes
down occasionally too!

This is nginx-extras-1.1.0-1 from debian testing.

Mike

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,214067,214262#msg-214262

Hello!

On Thu, Aug 25, 2011 at 11:31:36AM -0400, gaima wrote:

setting proxy_cache_valid to a tiny value, around

2011/08/24 15:50:20 [alert] 14268#0: failed to register channel handler
while initializing push module worker (1: Operation not permitted)

This looks like push module related problem.

Maxim D.

I have the same problem running nginx 1.0.6 from dotdeb.org

2011/09/16 13:08:50 [alert] 12610#0: epoll_ctl(1, 0) failed (1:
Operation not permitted)
2011/09/16 13:08:50 [alert] 12610#0: failed to register channel handler
while initializing push module worker (1: Operation not permitted)
2011/09/16 13:08:50 [alert] 12611#0: epoll_ctl(1, 0) failed (1:
Operation not permitted)
2011/09/16 13:08:50 [alert] 12611#0: failed to register channel handler
while initializing push module worker (1: Operation not permitted)
2011/09/16 13:08:50 [alert] 12608#0: cache manager process 12610 exited
with fatal code 2 and can not be respawn

There are several posts in the Internet concerning the same problem but
there is no solution :confused:

https://github.com/slact/nginx_http_push_module/issues/33
http://forum.nginx.org/read.php?21,185003,185003#msg-185003

I have the same problem here. How can we fix it?

Is this problem known by the developers?

Caching in general is working but without having a working cache manager
I am afraid of running out of disk space…

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,214067,215296#msg-215296

Hello!

On Fri, Sep 16, 2011 at 07:37:18AM -0400, philipp wrote:

I have the same problem here. How can we fix it?

Is this problem known by the developers?

Caching in general is working but without having a working cache manager
I am afraid of running out of disk space…

Recompiling nginx without third party push module will solve it.
If you want this to be fixed, you may want to CC push module
author.

Maxim D.

Hello,

Am 16.09.2011 13:13, schrieb Philipp H.:

2011/09/16 13:08:50 [alert] 12608#0: cache manager process 12610 exited
with fatal code 2 and can not be respawn

There are several posts in the Internet concerning the same problem but
there is no solution :confused:

https://github.com/slact/nginx_http_push_module/issues/33
http://forum.nginx.org/read.php?21,185003,185003#msg-185003

if you cant fix this issue, take a look at the new
http-push-stream-module

https://github.com/wandenberg/nginx-push-stream-module

since version 0.3.0 it also supports long-polling and polling.

Alexander K.