So the 500 is coming from supervisord. 2010/11/24 21:26:52 [debug] 6595#0: *22 http proxy status 500 "500 Internal Server Error" 2010/11/24 21:26:52 [debug] 6595#0: *22 http proxy header: "Date: Wed, 24 Nov 2010 19:26:52 GMT" 2010/11/24 21:26:52 [debug] 6595#0: *22 http proxy header: "Content-Length: 146" 2010/11/24 21:26:52 [debug] 6595#0: *22 http proxy header: "Content-Type: text/html" 2010/11/24 21:26:52 [debug] 6595#0: *22 http proxy header: "Server: Medusa/1.12"
On Wed, Nov 24, 2010 at 11:30 AM, Jurie-Jan Botha <juriejanbo...@gmail.com> wrote: > Edho: Tried that. Gives me a 'invalid URL prefix' message when trying to > start up the nginx server. > Roger: Curl give me the following: > * About to connect() to supervisor port 8080 (#0) > * Trying 127.0.0.1... connected > * Connected to supervisor (127.0.0.1) port 8080 (#0) >> GET / HTTP/1.1 >> User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k >> zlib/1.2.3.3 libidn/1.15 >> Host: supervisor:8080 >> Accept: */* >> > < HTTP/1.1 500 Internal Server Error > < Server: nginx/0.8.53 > < Date: Wed, 24 Nov 2010 19:13:07 GMT > < Content-Type: text/html > < Connection: keep-alive > < Content-Length: 146 > < > <head> > <title>Error response</title> > </head> > <body> > <h1>Error response</h1> > <p>Error code 500. > <p>Message: Internal Server Error. > </body> > * Connection #0 to host supervisor left intact > * Closing connection #0 > I've also setup nginx with debug logs which are attached. The debug logs > include the output for one request. > > > On 24 November 2010 18:05, Roger Hoover <roger.hoo...@gmail.com> wrote: >> >> 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
