Opened 9 years ago

Closed 9 years ago

#25607 closed Bug (needsinfo)

IIS deployment - WSGI handler

Reported by: Ola Owned by: nobody
Component: HTTP handling Version: 1.8
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Ola)

The following script https://github.com/aleksandra-tarkowska/openmicroscopy/blob/iss_deploy_improvement/components/tools/OmeroPy/src/omero_web_iis.py allowed our Django application being smoothly deployed on Windows IIS 6 or 7 With Django<=1.6. Since we upgraded Django to use 1.8 this no longer works. There is not much in the logfile.

HTTP Error 500.0 - Internal Server Error

Detailed Error Information:
Module	   IsapiModule
Notification	   ExecuteRequestHandler
Handler	   AboMapperCustom-8263
Error Code	   0x80004005
Requested URL	   http://localhost:80/omero/
Physical Path	   C:\inetpub\wwwroot\
Logon Method	   Anonymous
Logon User	   Anonymous

Microsoft Knowledge Base Articles:

    294807

Change History (9)

comment:1 by Ola, 9 years ago

Description: modified (diff)
Summary: IIS deploymentIIS deployment - WSGI handler

comment:2 by Ola, 9 years ago

Description: modified (diff)

comment:3 by Ola, 9 years ago

Description: modified (diff)

comment:4 by Claude Paroz, 9 years ago

Resolution: needsinfo
Status: newclosed

I'm not very happy to keep such bugs open until someone can demonstrate that Django is at fault.

comment:5 by Josh Smeaton, 9 years ago

Agree with Claude, this doesn't (yet) look like a problem with Django. The reporter will need to provide additional information. Here's some ideas for collecting more information.

Set DEBUG=True in your settings (make sure it's not in production though!) and try to make the request. You should get the django error page which will give you information about the error and a stacktrace if the error was within the django process.

Additionally, set up logging in your settings to write to a file. Until you can see what is happening within django to cause the error, we can't help you.

comment:6 by Ola, 9 years ago

This is the error:

> c:\omero.server\lib\python\omero_web_iis.py(133)<module>()->None
-> HandleCommandLine(params)
(Pdb)
Exception AttributeError: "'NoneType' object has no attribute 'path'" in <bound
method Signal._remove_receiver of <django.dispatch.dispatcher.Signal object at 0
x00000000055A4048>> ignored

am not even getting to the Django page

Version 3, edited 9 years ago by Ola (previous) (next) (diff)

comment:7 by Ola, 9 years ago

Resolution: needsinfo
Status: closednew

comment:8 by Ola, 9 years ago

Please note that I have no issue with deploying application on Unix using apache and mod_wsgi or nginx and gunicorn. This is just IIS and 1.8 problem

comment:9 by Tim Graham, 9 years ago

Resolution: needsinfo
Status: newclosed

Sorry, but the provided information still doesn't demonstrate to me that Django is at fault (although I never used IIS before and don't have a setup to reproduce there error).

Maybe you get can help from other IIS users using TicketClosingReasons/UseSupportChannels and then reopen this with a better description of why Django is at fault and what change we need to make? It would also be helpful if you could bisect to the Django commit where things stopped working. Thanks!

Note: See TracTickets for help on using tickets.
Back to Top