Hi Graham, Thanks for the reply. I tried to recreate this issue today and my app seems to work fine with both the long and the short name. It must have been some other config issue that I inadvertently fixed. Thanks again for the reply and sorry for wasting your time.
Patrick On Sunday, November 22, 2015 at 8:20:24 AM UTC+11, Graham Dumpleton wrote: > > Also try temporarily turning on DEBUG=True in your Django settings module. > It is normal that if you have an exception in your application code that > nothing gets logged and just a 500 returned. This is because by default > Django doesn’t log anything and needs to be set up to log details of > exceptions or send them as email to you. > > So make sure that Django itself is set up to capture details of Python > exceptions in some way. > > Enabling debug mode of Django will in most cases allow the exception to be > visible in the browser. That said, enabling debug mode of Django can > sometimes see a problem go away as it is returning error responses. If that > occurs then it could be well be a problem in Apache configuration with > ErrorDocument directives referring to URLs that do not exist. > > Anyway, try enabling debug in Django first, or have it log exceptions, and > determine whether the 500 is coming from Django. > > Graham > > On 22 Nov 2015, at 6:39 AM, Graham Dumpleton <[email protected] > <javascript:>> wrote: > > There shouldn't be a limit on the name of the application group. > > Can you set LogLevel directive in Apache for that VirtualHost, or whole > server as necessary, to 'debug'. This will enable a lot more logging. > Capture what mod_wsgi is logging for the request when made and post it. > > Thanks. > > Graham > > On 21 Nov 2015, at 6:38 PM, Patrick Joy <[email protected] > <javascript:>> wrote: > > Hi, > > Just wondering what the maximum length of the application name is when > mod_wsgi in daemon mode? > > I have noticed that when the application name is too long (for example > below), apache will return a 500 server error but nothing will be logged in > any of the logs, even with log level set to debug. > > WSGIDaemonProcess mysuperduperapplication user=django group=django > threads=25 display-name=%{GROUP} inactivity-timeout=3600 > python-home=/usr/local/pythonenv/DJANGO_1.8 > WSGIProcessGroup mysuperduperapplication > > Thanks, > Patrick > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] <javascript:> > . > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
