on-the-fly conf reload retrieves errors

[Lorenzo Raffio]

Ignore, I found the explanation

On 30/dic/2012, at 21:33, Lorenzo Raffio <multiformeingegno at gmail.com> wrote:

> I tried to run a "nginx -c /etc/nginx/nginx.conf" but I got:
> nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> nginx: [emerg] still could not bind()
> [Exit 1]
> 
> Then I run a fuser -k 80/tcp ; service nginx restart. I tried again with nginx -c /etc/nginx/nginx.conf but still the same [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
> 
> Why is this happening?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20121230/1103ef89/attachment-0001.html>