Well, here's what I know: I had this issue several months back and 'solved' it by disabling the in memory upload handler. I wrote a little about it at the bottom of this thread: https://forums.mediatemple.net/viewtopic.php?id=2514
But it looks like in Django 1.1beta the TemporaryFileUploadHandler is now using the same locking calls that the MemoryFileUploadHandler is, so that hack is no longer enough. I've reverted back to django 1.0 and file uploads work again. Bummer. MWM On Jun 17, 9:47 am, Sean Brant <brant.s...@gmail.com> wrote: > Nope, there customer support takes to long so I just gave up. Please > post if you have any updates. Last I remember it might be a NFS issue > on there end. Not really sure. > > On Jun 17, 2009, at 9:43 AM, mmarshall <matt...@matthewmarshall.org> > wrote: > > > > > On Jun 9, 9:19 am, Sean Brant <brant.s...@gmail.com> wrote: > >> "Did MediaTemple change something about the file system you have > >> access to? It sounds like they must have changed something so that > >> the file locking code that used to work for your setup is no longer > >> working." > > >> That is what it sounds like to me, however they we're not much help. > >> I'll reach back out to them and see what they say. > > > Any news on this? I'm running up against the same problem. > > > MWM > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
