2010/1/6 Don Spaulding <[email protected]>: > Hello, > > I'm using modwsgi 2.5 and apache 2.2.12 on Ubuntu Server (Karmic). > I've got it serving up Django in a pretty standard config, which is > pasted below. > > The problem I'm having is with a Django admin page that has a file > input element. Uploading a file to this page works fine from my Mac, > but doesn't work from a Windows XP client (via Firefox, IE, Chrome, or > Opera). Firefox's progress bar shows up for a split-second, and then > disappears without any errors or warnings, it just redisplays the > current admin page. The file itself resides on an samba file share, > mapped locally to a drive on the client. If I change either the > client OS or the file's location (e.g. local instead of over SMB) the > problem goes away. > > Using Wireshark I'm able to see the response from Apache is a wsgi- > generated 500 error (if it makes it into the django stack, I almost > always get a python traceback, this is just a plain vanilla HTTP > 500). My vhost error log shows the following 3 lines every time the > upload fails. > > [Tue Jan 05 16:33:34 2010] [error] [client 193.230.129.57] (70014)End > of file found: mod_wsgi (pid=23936): Unable to get bucket brigade for > request., referer: http://beta.mydomain.com/admin/livemedia/package/8116/ > [Tue Jan 05 16:33:34 2010] [error] [client 193.230.129.57] mod_wsgi > (pid=21406): Exception occurred processing WSGI script '/home/webdev/ > apps/vhosts/mydomain.wsgi'. > [Tue Jan 05 16:33:34 2010] [error] [client 193.230.129.57] IOError: > failed to write data
This error says that the connection back to the HTTP client has been closed at the time data was attempted to be written back to HTTP client. I can't see why using Samba share would cause this. Thus inclined to think you have an underlying error and the way that error response for that is generating is causing the above. The issue then is what is the underlying error. My guess here would be that the webdev user doesn't have write permission to the Samba share. Graham > I realize this is almost certainly not modwsgi's fault, and I don't > pretend to be much of a hacker at this level of the stack. I wondered > if someone could shed some light onto the possible causes of this > error for me. > > Thanks, > Don > > ### mydomain.conf ### > > <VirtualHost XX.XX.XX.XX:80> > ServerName beta.mydomain.com > ServerAlias beta.mydomain.com > ServerAdmin [email protected] > > Alias /media/ /home/webdev/apps/vhosts/media/mydomain/ > Alias /admin_media/ /home/webdev/apps/mydomain/lib/python2.6/site- > packages/django/contrib/admin/media/ > > DocumentRoot /home/webdev/apps/vhosts/media/mydomain > > <Directory /home/webdev/apps/vhosts/media/mydomain> > Order allow,deny > Allow from all > </Directory> > > <Directory /home/webdev/apps/mydomain/lib/python2.6/site-packages/ > django/contrib/admin/media/ > > Order allow,deny > Allow from all > </Directory> > > LogLevel warn > ErrorLog /home/webdev/apps/vhosts/logs/mydomain.err > CustomLog /home/webdev/apps/vhosts/logs/mydomain.log combined > > WSGIDaemonProcess mydomain processes=20 threads=1 maximum- > requests=50 display-name=%{GROUP} user=webdev group=webdev > WSGIProcessGroup mydomain > > WSGIScriptAlias / /home/webdev/apps/vhosts/mydomain.wsgi > > <Files /home/webdev/apps/vhosts/mydomain.wsgi> > Order allow,deny > Allow from all > </Files> > > </VirtualHost> > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > > >
-- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
