Repeating tracebacks in journal on fresh containerized deployment

Solution Verified - Updated -

Issue

  • After fresh Red Hat OpenStack Platform 13 deployment, we can see repeating Tracebacks in the docker.service in the controllers:
systemctl status docker.service
..

Oct 14 21:35:33 controller-0 dockerd-current[19433]:     self.RequestHandlerClass(request, client_address, self)
Oct 14 21:35:33 controller-0 dockerd-current[19433]:   File "/usr/lib64/python2.7/SocketServer.py", line 651, in __init__
Oct 14 21:35:33 controller-0 dockerd-current[19433]:     self.finish()
Oct 14 21:35:33 controller-0 dockerd-current[19433]:   File "/usr/lib64/python2.7/SocketServer.py", line 710, in finish
Oct 14 21:35:33 controller-0 dockerd-current[19433]:     self.wfile.close()
Oct 14 21:35:33 controller-0 dockerd-current[19433]:   File "/usr/lib64/python2.7/socket.py", line 279, in close
Oct 14 21:35:33 controller-0 dockerd-current[19433]:     self.flush()
Oct 14 21:35:33 controller-0 dockerd-current[19433]:   File "/usr/lib64/python2.7/socket.py", line 303, in flush
Oct 14 21:35:33 controller-0 dockerd-current[19433]:     self._sock.sendall(view[write_offset:write_offset+buffer_size])
Oct 14 21:35:33 controller-0 dockerd-current[19433]: error: [Errno 32] Broken pipe

Environment

  • Red Hat OpenStack Platform 13

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content