Created attachment 1096715 [details] central.log excerpt Description of problem: Strange traceback in ceilometer/central.log - 2015-11-19 08:08:48.844 25809 ERROR ceilometer.hardware.pollsters.generic ;RuntimeError: Second simultaneous write on fileno 21 detected. Unless you really know what you're doing, make sure that only one greenthread can write any particular socket. Consider using a pools.Pool. If you do know what you're doing and want to disable this error, call eventlet.debug.hub_prevent_multiple_readers(False) - MY THREAD=<built-in method switch of GreenThread object at 0x2da5050>; THAT THREAD=FdListener('write', 21, <built-in method switch of GreenThread object at 0x2da50f0>, <built-in method throw of GreenThread object at 0x2da50f0>) Looks like some race condition bug cuz after restart it wasn't reproduced. Version-Release number of selected component (if applicable): openstack-ceilometer-api-5.0.0-1.el7ost.noarch openstack-ceilometer-notification-5.0.0-1.el7ost.noarch openstack-ceilometer-common-5.0.0-1.el7ost.noarch python-ceilometerclient-1.5.0-1.el7ost.noarch python-ceilometer-5.0.0-1.el7ost.noarch openstack-ceilometer-central-5.0.0-1.el7ost.noarch openstack-ceilometer-polling-5.0.0-1.el7ost.noarch openstack-ceilometer-alarm-5.0.0-1.el7ost.noarch openstack-ceilometer-collector-5.0.0-1.el7ost.noarch How reproducible: N/A Actual results: Traceback in log. Additional info: HA virtual setup (3 controller + 1 compute)
Upstream version 5.0.4 have been released with the fix.
This is included with the 5.0.4 and 5.0.5 rebases.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2714.html