On Mon, Dec 09, 2013 at 08:24:30AM -0500, Peleke wrote:

Hi there,

> One problem seems to be that it is not possible to stop nginx:

That is probably worth fixing independent of anything else.

Issue whatever "kill" or "nginx -s stop" commands you need to, to be
able to get it to reliably stop and start.

> user 14:08:55 ~: curl -v http://adminer.domain.tld
> * getaddrinfo(3) failed for adminer.domain.tld:80
> * Couldn't resolve host 'adminer.domain.tld'
> * Closing connection #0
> curl: (6) Couldn't resolve host 'adminer.domain.tld'

Your client can't resolve the hostname to the IP address, so nginx never
sees the request.

Fix your dns (or other name resolution) and it should work.

f
--
Francis Daly francis@daoine.org

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx