If there is no error in the nginx log then my guess is that it's coming from
supervisord. Maybe if you try curl -v http://localhost:8080/ the headers
sent back will have a clue.
On Tue, Nov 23, 2010 at 9:34 PM, Jurie-Jan Botha <juriejanbo...@gmail.com>wrote:
> Sorry for not mentioning. No messages in either the Nginx or Supervisord
> error logs. I've increased the Supervisord log level to debug. Perhaps I
> should increase the debug level on Nginx too.
>
>
> On 23 November 2010 22:22, Roger Hoover <roger.hoo...@gmail.com> wrote:
>
>> Is there anything in the nginx error log?
>>
>> On Tue, Nov 23, 2010 at 12:05 PM, Jurie-Jan Botha <
>> juriejanbo...@gmail.com> wrote:
>>
>>> I've searched high and low for some tips on running Supervisord on a Unix
>>> domain socket behind Nginx but I can seem to find anything to help me
>>> resolve the problem I'm currently facing.
>>>
>>> According to what I've seen running with the following Nginx
>>> configuration should work:
>>>
>>> server {
>>> listen 8080;
>>> server_name supervisor;
>>>
>>> location / {
>>> proxy_pass http://unix:/home/www/supervisor/supervisord.sock:/;
>>> #proxy_pass http://127.0.0.1:9001/;
>>> }
>>> }
>>>
>>>
>>> But I get the following back:
>>>
>>> <head>
>>> <title>Error response</title>
>>> </head>
>>> <body>
>>> <h1>Error response</h1>
>>> <p>Error code 500.
>>> <p>Message: Internal Server Error.
>>> </body>
>>>
>>> Not sure where it's coming from.
>>>
>>> The permissions on my sockets are right, and when I run supervisord with
>>> the 'inet_http_server' settings it works fine.
>>>
>>> Any tips would be apreciated. Thanks
>>>
>>> _______________________________________________
>>> Supervisor-users mailing list
>>> Supervisor-users@lists.supervisord.org
>>> http://lists.supervisord.org/mailman/listinfo/supervisor-users
>>>
>>>
>>
>
_______________________________________________
Supervisor-users mailing list
Supervisor-users@lists.supervisord.org
http://lists.supervisord.org/mailman/listinfo/supervisor-users
