On Mon, Nov 29, 2010 at 4:37 PM, Maxim Dounin <mdounin@mdounin.ru> wrote:
> Hello!
>
> On Mon, Nov 29, 2010 at 02:19:50PM +0100, Saimon Moore wrote:
>
>> Hi Maxim,
>>
>> I did and there's nothing (new) in there... :(
>
> So the most likely reason is that you forgot to reload nginx
> config.  It should complain there why it wasn't able to parse your
> config and/or open configured listening sockets.  Even if you were
> smart enough to redirect stderr to something like /dev/null.

As expected my bad. Sorry for the noise.
You were on the right track. I had two configs setup in
sites-available. The one I was interested in wasn't symlinked in
sites-enabled. duh.

Thanks again...

>
> Another possible reason is that you have wrong binary running and
> it tries to read configs from another place.
>
> Full restart should resolve both mentioned issues.
>
> Maxim Dounin
>
> p.s. Please do not top-post.  Thank you.
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>



--
Saimon Moore
Freelance Web Developer
(Available for hire - For details visit http://saimonmoore.net)

Skype: saimonmoore
Yahoo IM: saimonmoore
Google IM: saimonmoore

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