Forum: NGINX error unlink() nginx 1.2.6

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?

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

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

Hello guys

I'm having this problem too in version 3.1.14 and never do delete these
files manually. How can I solve this?

Maxim, if you say the message is too scary, then why don't we change the
level of this log message from critical to notice?

Cheers
Michael

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

Hello!

On Sat, Mar 09, 2013 at 07:52:40PM -0500, michael.heuberger wrote:

> Hello guys
>
> I'm having this problem too in version 3.1.14 and never do delete these
> files manually. How can I solve this?

Even if you did not delete files manually, the message still
indicate files were somehow removed out of nginx control.  You
may want to dig further to find out how files were removed.

> Maxim, if you say the message is too scary, then why don't we change the
> level of this log message from critical to notice?

The notice is certainly too low, as this isn't something which
should happen under normal conditions.

--
Maxim Dounin
http://nginx.org/en/donation.html

Hello!

After I read the thread, I am wondering what is the recommended way to 
purge nginx cache?

Regards,
Kiril

Hello!

On Mon, Mar 11, 2013 at 09:58:28AM +0200, Kiril Kalchev wrote:

> After I read the thread, I am wondering what is the recommended way to purge 
nginx cache?

Recommended way is to assume you can't purge the cache, much like
you can't purge caches in client's browsers and/or intermediate
forward proxies.  A week ago I've explained this to Michael here:

http://mailman.nginx.org/pipermail/nginx/2013-Marc...

--
Maxim Dounin
http://nginx.org/en/donation.html

Thank you very much, and sorry for the repeated question. I will dig 
deeper before asking next time.

Regards,
Kiril