Hello!
On Sat, Dec 29, 2012 at 06:43:24AM -0500, bat21 wrote:
> the error.log file I get the error: 12/29/2012 12:40:39 [crit] 16489 # 0:
> unlink () "/ var/cache/cafe2/2/9e/5d7f005ef7a1b948e522a3b8ed5959e2" failed
> (2: No such file or directory)
> the folder has permissions 777. how to fix this?
Such errors appear if cache files are deleted by some external
means, e.g. manually, while nginx is running. Obvious fix is to
avoid deleting cache files.
The message is probably a bit too scary, this condition is
actually handled more or less normally by nginx - the only
unwanted results of deleting cache files is the message itself and
the total cache size being incorrect till the message (this may be
a problem if you rely on a cache max size set via
"proxy_cache_path ... max_size=N").
--
Maxim Dounin
http://nginx.com/support.html
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Sat, Dec 29, 2012 at 06:43:24AM -0500, bat21 wrote:
> the error.log file I get the error: 12/29/2012 12:40:39 [crit] 16489 # 0:
> unlink () "/ var/cache/cafe2/2/9e/5d7f005ef7a1b948e522a3b8ed5959e2" failed
> (2: No such file or directory)
> the folder has permissions 777. how to fix this?
Such errors appear if cache files are deleted by some external
means, e.g. manually, while nginx is running. Obvious fix is to
avoid deleting cache files.
The message is probably a bit too scary, this condition is
actually handled more or less normally by nginx - the only
unwanted results of deleting cache files is the message itself and
the total cache size being incorrect till the message (this may be
a problem if you rely on a cache max size set via
"proxy_cache_path ... max_size=N").
--
Maxim Dounin
http://nginx.com/support.html
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx