Location not found when using /

[Valentin V. Bartenev]

On Thursday 14 May 2015 10:22:04 Guido Accardo wrote:
> Hi,
> 
>    I'm having a few problems with my routes and I'll appreciate any help
> that you could provide.
> 
> Here is my nginx configuration:
> 
> upstream internal {
>         server 10.0.0.13:9001;
>         server 10.0.0.13:9002;
>         server 10.0.0.13:9003;
>         server 10.0.0.13:9004;
>         server 10.0.0.15:9001;
>         server 10.0.0.15:9002;
>         server 10.0.0.15:9003;
>         server 10.0.0.15:9004;
>         keepalive 1024;
> }
> 
> server {
>     listen 12340;
> 
>     location / {
>         proxy_pass         http://internal;
>     }
> }
> 
> 
> Al the processes in the upstream matches the route: /process/a/N
> 
> Everything is running ok, but in a random fashion routes that worked in the
> past, such as
> /process/a/1 or /process/a/2 returns as HTTP/404 and the request never
> reaches the upstream servers. So I think is nginx itself answering with the
> 404.
> 
> Also, in the logs I see:
> 
>  /usr/local/nginx/html/process/a/1 failed (2: No such file or directory)
> 
> which has no sense given I didn't set a root and in nginx.conf.
> 
> Thank you in advance.
> 

The configuration above isn't complete.  You probably have another "server"
block, which handles requests.

  wbr, Valentin V. Bartenev