El martes, 16 de febrero de 2016, 21:12:32 (UTC+1), James Schneider escribió: > > How long does the file upload work before receiving the error? >>>>> >>>> >>>> There is no response from the server (fiddler returns -1, whatever this >>>> means) >>>> >>> >>> Well, no response from the server doesn't necessarily mean that there >>> were no logs. Can you check the error and access logs of the server? >>> >> >> > > Have you checked the server logs? >
Yes....there are no logs!! I know....just joined the project and we are using the email handler....sad! > > > >> >> >>> >>> Does Fiddler return an immediate response of -1, or does it seem like >>> there is a timeout period? >>> >> >> immediate response, no time out period. >> > > > Without looking at the server logs, I can only guess that Gnuicorn is > unhappy with the headers that are being sent, and might be closing the > connection. A long timeout would probably indicate that Gnuicorn is waiting > for more data but something in the upload process is not triggering that it > has reached the end of the data stream. > I've done some more test and seems that the -1 is normal while data it's been uploaded. Nothing wrong with that. So I guess we need to config the logging and start looking at it. > > > >> >>> After a quick glance at Fiddler itself, are you using any customizations >>> on the rules >>> >> >> no customization. Default "Simulate Modem speeds". I must say I use >> fiddle to be able to reproduce the error locally. If I hit the server >> (production) using wifi (slower than ethernet) I got the same thing, no >> fiddler in the middle. >> > > But it works using a wired Ethernet connection? Honestly, the speed > difference between Wi-Fi and Ethernet for this purpose is probably not > relevant to the problem. The server logs would tell you more about what is > happening. > > logs, logs, logs....I'm on it. :-( > > >>> >>>>> Nice advice...I'll look into this. Do you know any nice example for >>>> that JS library chunk upload. >>>> >>>>> >>>>> >>> >>> Probably best to stick with your existing JS framework of choice if you >>> are using one. All of the major ones have some version of a chunked >>> uploader (JQuery and Angular), and I come across resumable.js fairly >>> frequently. I've never personally had a need for one, so I can't really >>> comment on them in any sort of detail or make a recommendation. >>> >> >> Testing resumable.js....let's see how it goes. >> >> So, far there is some response, but after a while got 404 response >> (testing locally against DAJNGO)....will it make a difference against >> gunicorn? >> >> >> <https://lh3.googleusercontent.com/-Np89QZHcABY/VsLzaKBNNsI/AAAAAAAAX9c/842IZ7Qj9ho/s1600/resumableOption.png> >> > > This smells like either a memory exhaustion/ceiling issue or some kind of > internal connection/process timeout, neither of which are likely easy to > adjust using the Django dev server. Gunicorn probably has 10,000 knobs to > adjust those timers and limits, though. > > Look at the server error/access logs. > again....logs, logs, logs....I'll setup gunicorn locally and enable logging. For someone wanting to move to a file chunk upload, I've tried resumable.js and a django component for it. it was failing. Now I'm happier with this other: https://github.com/juliomalegria/django-chunked-upload-demo (test over wifi ave worked fine). But again.....maybe the problem is in our setup and not in those tools. Thanks, James, you've been vary helpful. > > -James > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/ba2e9f2d-2c6d-4a4a-9259-14a8e95d9135%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
