View Single Post
Old 05-30-2017, 09:48 AM   #393
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by kovidgoyal View Post
Well, it was only a guess. The other thing you could try is adding some print statements to see if the client is actually receiving all the data or aborting in between. You can change line 310 to disable the use of sendfile and then add the prints to the write() method to see what is being written to the socket.
That shows me something. But, I can't see what is wrong with it.

I also added a print in the send() in loop.py to see if there was an exception. I got:

Code:
send - exception - e: [Errno 10053] An established connection was aborted by the software in your host machine
That seems to happen on the last packet of the file sent.

Wireshark tells me roughly the same thing. The device is sending packets back with the reset bit set. I assume that's why the above error happens. I'll have to hunt through it and see what else I can find.
davidfor is offline   Reply With Quote