ok, wait a second, I'll try with my VM. the previous traceback is due to the changes done to the certificate generation: I took them for granted but there must be an error somewhere.
On Wednesday, December 12, 2012 7:48:54 PM UTC+1, Richard wrote: > > uwsgi doesn't seem to start, I have not log for it in /var/log/uwsgi/ > > Try to start it like that : > > /etc/init$ sudo start uwsgi-emperor > start: Job failed to start > > Richard > > On Wed, Dec 12, 2012 at 1:27 PM, Richard Vézina > <[email protected]<javascript:> > > wrote: > >> Here error log : >> >> cat /var/log/nginx/error.log >> 2012/12/12 13:12:40 [emerg] 17676#0: >> SSL_CTX_use_certificate_chain_file("/etc/nginx/ssl/web2py.crt") failed >> (SSL: error:02001002:system library:fopen:No such file or directory >> error:20074002:BIO routines:FILE_CTRL:system lib error:140DC002:SSL >> routines:SSL_CTX_use_certificate_chain_file:system lib) >> 2012/12/12 13:12:40 [emerg] 17677#0: >> SSL_CTX_use_certificate_chain_file("/etc/nginx/ssl/web2py.crt") failed >> (SSL: error:02001002:system library:fopen:No such file or directory >> error:20074002:BIO routines:FILE_CTRL:system lib error:140DC002:SSL >> routines:SSL_CTX_use_certificate_chain_file:system lib) >> 2012/12/12 13:15:34 [emerg] 17721#0: >> SSL_CTX_use_certificate_chain_file("/etc/nginx/ssl/self_signed.crt") failed >> (SSL: error:02001002:system library:fopen:No such file or directory >> error:20074002:BIO routines:FILE_CTRL:system lib error:140DC002:SSL >> routines:SSL_CTX_use_certificate_chain_file:system lib) >> 2012/12/12 13:15:34 [emerg] 17722#0: >> SSL_CTX_use_certificate_chain_file("/etc/nginx/ssl/self_signed.crt") failed >> (SSL: error:02001002:system library:fopen:No such file or directory >> error:20074002:BIO routines:FILE_CTRL:system lib error:140DC002:SSL >> routines:SSL_CTX_use_certificate_chain_file:system lib) >> 2012/12/12 13:16:45 [emerg] 17756#0: >> SSL_CTX_use_certificate_chain_file("/etc/nginx/ssl/self_signed.crt") failed >> (SSL: error:02001002:system library:fopen:No such file or directory >> error:20074002:BIO routines:FILE_CTRL:system lib error:140DC002:SSL >> routines:SSL_CTX_use_certificate_chain_file:system lib) >> 2012/12/12 13:16:45 [emerg] 17757#0: >> SSL_CTX_use_certificate_chain_file("/etc/nginx/ssl/self_signed.crt") failed >> (SSL: error:02001002:system library:fopen:No such file or directory >> error:20074002:BIO routines:FILE_CTRL:system lib error:140DC002:SSL >> routines:SSL_CTX_use_certificate_chain_file:system lib) >> 2012/12/12 13:17:29 [crit] 17770#0: *5 connect() to >> unix:///tmp/web2py.socket failed (2: No such file or directory) while >> connecting to upstream, client: 192.168.1.102, server: sgddms1, request: >> "GET / HTTP/1.1", upstream: "uwsgi://unix:///tmp/web2py.socket:", host: >> "192.168.1.190" >> 2012/12/12 13:17:29 [crit] 17770#0: *5 connect() to >> unix:///tmp/web2py.socket failed (2: No such file or directory) while >> connecting to upstream, client: 192.168.1.102, server: sgddms1, request: >> "GET /favicon.ico HTTP/1.1", upstream: >> "uwsgi://unix:///tmp/web2py.socket:", host: "192.168.1.190" >> 2012/12/12 13:18:34 [crit] 17770#0: *9 connect() to >> unix:///tmp/web2py.socket failed (2: No such file or directory) while >> connecting to upstream, client: 192.168.1.102, server: sgddms1, request: >> "GET / HTTP/1.1", upstream: "uwsgi://unix:///tmp/web2py.socket:", host: >> "192.168.1.190" >> 2012/12/12 13:18:34 [crit] 17770#0: *9 connect() to >> unix:///tmp/web2py.socket failed (2: No such file or directory) while >> connecting to upstream, client: 192.168.1.102, server: sgddms1, request: >> "GET /favicon.ico HTTP/1.1", upstream: >> "uwsgi://unix:///tmp/web2py.socket:", host: "192.168.1.190" >> 2012/12/12 13:18:38 [crit] 17770#0: *9 connect() to >> unix:///tmp/web2py.socket failed (2: No such file or directory) while >> connecting to upstream, client: 192.168.1.102, server: sgddms1, request: >> "GET / HTTP/1.1", upstream: "uwsgi://unix:///tmp/web2py.socket:", host: >> "192.168.1.190" >> 2012/12/12 13:18:38 [crit] 17770#0: *9 connect() to >> unix:///tmp/web2py.socket failed (2: No such file or directory) while >> connecting to upstream, client: 192.168.1.102, server: sgddms1, request: >> "GET /favicon.ico HTTP/1.1", upstream: >> "uwsgi://unix:///tmp/web2py.socket:", host: "192.168.1.190" >> >> Please ignore the lines about certificat, I didn't have the last version >> of the script. So I change the wrong name of the certificat in order that >> nginx config use the proper files. >> >> Richard >> >> On Wed, Dec 12, 2012 at 1:18 PM, Richard Vézina >> <[email protected]<javascript:> >> > wrote: >> >>> 502 Bad Gateway >>> >>> Under 12.10 >>> >>> Richard >>> >>> >>> On Wed, Dec 12, 2012 at 12:53 PM, Richard Vézina >>> <[email protected]<javascript:> >>> > wrote: >>> >>>> I am testing it right now, waiting the VM finish to install :) >>>> >>>> Richard >>>> >>>> >>>> On Wed, Dec 12, 2012 at 12:48 PM, Niphlod <[email protected]<javascript:> >>>> > wrote: >>>> >>>>> @Richard: fixed. Can you test if this is the behaviour that you want ? >>>>> >>>>> @Paolo: thanks for the pointer, fixed. >>>>> >>>>> @Massimo: I "released" the script here to test it before sending the >>>>> patch to you just because of these small hiccups here and there. This >>>>> could >>>>> definitely become the default installation script on debian derivatives >>>>> of >>>>> web2py (with one of the speediest stacks out there and quite frankly the >>>>> easiest to maintain :-P). Next steps are fabric/cuisine scripts for all >>>>> kinds of Linuxes. >>>>> >>>>> -- >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >> > --
