Upload complete, but with error

[Dave S]

When uploading a file from one of our Windows clients, we sometimes find this in the web2py.log file:

   File "/home/ec2-user/web2py/web2py-2.14.6/gluon/rocket.py", line 1337, in run

    self.run_app(conn)


  File "/home/ec2-user/web2py/web2py-2.14.6/gluon/rocket.py", line 1851, in run_app
    self.write(data, sections)


  File "/home/ec2-user/web2py/web2py-2.14.6/gluon/rocket.py", line 1766, in write
    self.send_headers(data, sections)


  File "/home/ec2-user/web2py/web2py-2.14.6/gluon/rocket.py", line 1750, in send_headers
    self.conn.sendall(b(header_data))


  File "/usr/lib64/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)


error: [Errno 32] Broken pipe

Is this basically a timeout because the end of transfer wasn't detected properly?  Or is something going wrong with preparing and sending the response?

/dps

[Dave S]

On Thursday, December 15, 2016 at 2:11:57 PM UTC-8, Dave S wrote:

When uploading a file from one of our Windows clients, we sometimes find this in the web2py.log file:

[...]

  File "/home/ec2-user/web2py/web2py-2.14.6/gluon/rocket.py", line 1766, in write
    self.send_headers(data, sections)

  File "/home/ec2-user/web2py/web2py-2.14.6/gluon/rocket.py", line 1750, in send_headers
    self.conn.sendall(b(header_data))


  File "/usr/lib64/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)


error: [Errno 32] Broken pipe

Is this basically a timeout because the end of transfer wasn't detected properly?  Or is something going wrong with preparing and sending the response?

With a quick look at line 1750, I see it follows something about closing the connection.  Is that "close" as in book-keeping, or "close" as socket code thinks the connection is closed?

/dps

[Dave S]

Current status in the other thread:
<URL:https://groups.google.com/d/msg/web2py/dTK5lxWBsIA/3sIYnwMsBwAJ>

/dps