A lot of crit error in logs

I use nginx for reverse proxy on front of apache2. I get a lot of crit
messages in logs like this.

2010/04/16 17:20:32 1730#0: *468039 rename() “/webhost/tmp/0004372283”
to “/webhost/tmp/xxxxxxx/” failed (20: Not a directory) while reading
upstream, client: xxxxxxxxxxx, server: ., request: “GET
/xxxxxxxx/?&manset_id=&baslangic=2510 HTTP/1.1”, upstream:
http://xxxxxxxxxxx:8080/xxxxxxxxxxxx/?&manset_id=&baslangic=2510”,
host: “xxxxxxxxxx.com

here is my config.

user www-data;
worker_processes 4;

error_log /logs/nginx/error.log;
pid /var/run/nginx.pid;

events {
worker_connections 1024;
}

http {
include /etc/nginx/mime.types;
default_type application/octet-stream;

log_format  main  '$remote_addr - $remote_user [$time_local] 

$request ’
'"$status"
$body_bytes_sent “$http_referer” ’
‘"$http_user_agent"
“$http_x_forwarded_for”’;

access_log  /logs/nginx/access.log main;

tcp_nodelay        on;

Size Limits

client_body_buffer_size 128K;
client_header_buffer_size 128K;
client_max_body_size 1M;
large_client_header_buffers 1 1k;

Timeouts

client_body_timeout 60;
client_header_timeout 60;
expires 0;
keepalive_timeout 60 60;
send_timeout 60;

General Options

ignore_invalid_headers on;

keepalive_requests 100;

limit_zone gulag $binary_remote_addr 5m;
recursive_error_pages on;
sendfile on;
server_name_in_redirect off;
server_tokens off;

gzip on;

gzip_static on;

gzip_buffers 16 8k;
gzip_comp_level 6 ;
gzip_http_version 1.0;
gzip_proxied any;
gzip_min_length 0;
gzip_types application/x-shockwave-flash text/plain text/html
text/css application/javascript application/x-javascript text/xml
application/xml application/xml+rss text/javascript;
gzip_vary on;

upstream xxxxxxxxxxx  {

    server  xxxxxxxxxxxxxxxxxx:8080;

}

server {

            server_name *.*;
            root /webhost/tmp/;

location /
{
proxy_pass http://xxxxxxx;

}

}

proxy_store on;
proxy_redirect off;
proxy_temp_path /webhost/tmp;
proxy_store_access user:rw group:rw all:r; # set cache access
permissions
proxy_set_header Host $host; # Forward IP headers to Apache
proxy_set_header X-Real-IP $remote_addr; # Forward IP headers to Apache
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # Forward
IP headers to Apache

include /etc/nginx/conf.d/*.conf;

include /etc/nginx/sites-enabled/*;

}

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

Hi,

That error is because /webhost/tmp/0004372283 is a file but
/webhost/tmp/xxxxxxx/ is a directory which is being tried to rename.

I wonder what is trying to rename a file to directory ?

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

Hello!

On Fri, Apr 16, 2010 at 10:28:10AM -0400, solarisik wrote:

I use nginx for reverse proxy on front of apache2. I get a lot of crit messages in logs like this.

2010/04/16 17:20:32 1730#0: *468039 rename() “/webhost/tmp/0004372283” to “/webhost/tmp/xxxxxxx/” failed (20: Not a directory) while reading upstream, client: xxxxxxxxxxx, server: ., request: “GET /xxxxxxxx/?&manset_id=&baslangic=2510 HTTP/1.1”, upstream: “http://xxxxxxxxxxx:8080/xxxxxxxxxxxx/?&manset_id=&baslangic=2510”, host: “xxxxxxxxxx.com

here is my config.

[…]

            root /webhost/tmp/;

[…]

proxy_store on;
proxy_redirect off;
proxy_temp_path /webhost/tmp;

You are configured proxy_store to /webhost/tmp/. And you have
other files in this directory, at least nginx’s own proxy_temp
and/or other files already saved by previous proxy_store requests
(which is likely to cause conflicts due to your site structure).

Additionally, you are trying to save directory index accesses
without mapping them to files via custom proxy_store strings.
This will not work (though will cause different error).

And, after all, you don’t use proxy_store results at all.

Let me guess: you don’t need proxy_store at all, right?

Maxim D.

Thank you maxim

I also want to store files, I just change server conf /webhost/tmp/xxxx
and there is no error message at all.

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

hello

early decision, my image server crit error gone but my app server error
stil exist. I think the problem is my app server not use .html .htm like
web page structure. /backup/tmp/0000000844 files are not appear any more
but error in logs still exist.

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