[DRBD-user] Docker socket crashing

Roland Kammerer roland.kammerer at linbit.com
Mon Aug 14 09:36:37 CEST 2017

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Thu, Aug 10, 2017 at 10:56:30PM +0000, James Bland wrote:
> Hi,
> 
> I’ve installed DRBD9 via PPA onto a fresh Ubuntu 16.04 Server across 2 nodes with both also being upgraded to the 4.10 HWE kernel.
> 
> This is then setup and nodes look good and tried making a volume as a test in drbdmanage without issues
> 
> +------------------------------------------------------------------------------------------------------------+
> | Name         | Pool Size | Pool Free |                                                             | State |
> |------------------------------------------------------------------------------------------------------------|
> | kt-docker-01 |     40956 |     40948 |                                                             |    ok |
> | kt-docker-02 |     40956 |     40948 |                                                             |    ok |
> +------------------------------------------------------------------------------------------------------------+
> 
> I’ve then tried to use this with docker however the socket crashes in a loop until it gives up which I can see in the syslog
> 
> 
> Aug 10 23:18:34 kt-docker-01 systemd[1]: docker-drbdmanage-plugin.service: Main process exited, code=exited, status=1/FAILURE
> Aug 10 23:18:34 kt-docker-01 systemd[1]: docker-drbdmanage-plugin.service: Unit entered failed state.
> Aug 10 23:18:34 kt-docker-01 systemd[1]: docker-drbdmanage-plugin.service: Failed with result 'exit-code'.
> Aug 10 23:18:34 kt-docker-01 systemd[1]: Started DRBDmanage Docker Volume Plugin.
> Aug 10 23:18:34 kt-docker-01 python2[3798]: Traceback (most recent call last):
> Aug 10 23:18:34 kt-docker-01 python2[3798]:   File "/usr/libexec/docker/drbdmanage-docker-volume", line 81, in <module>
> Aug 10 23:18:34 kt-docker-01 python2[3798]:     class DockerHandler(BaseHTTPRequestHandler):
> Aug 10 23:18:34 kt-docker-01 python2[3798]:   File "/usr/libexec/docker/drbdmanage-docker-volume", line 83, in DockerHandler
> Aug 10 23:18:34 kt-docker-01 python2[3798]:     dm = DrbdManageDriver()
> Aug 10 23:18:34 kt-docker-01 python2[3798]:   File "/usr/libexec/docker/drbdmanage-docker-volume", line 51, in __init__
> Aug 10 23:18:34 kt-docker-01 python2[3798]:     super(DrbdManageDriver, self).__init__()
> Aug 10 23:18:34 kt-docker-01 python2[3798]:   File "/usr/lib/python2.7/dist-packages/drbdmanage/clienthelper.py", line 58, in __init__
> Aug 10 23:18:34 kt-docker-01 python2[3798]:     self.dbus_connect()
> Aug 10 23:18:34 kt-docker-01 python2[3798]:   File "/usr/lib/python2.7/dist-packages/drbdmanage/clienthelper.py", line 85, in dbus_connect
> Aug 10 23:18:34 kt-docker-01 python2[3798]:     if not dm_utils.is_rc_retry(server_rc[0]):
> Aug 10 23:18:34 kt-docker-01 python2[3798]:   File "/usr/lib/python2.7/dist-packages/drbdmanage/utils.py", line 335, in is_rc_retry
> Aug 10 23:18:34 kt-docker-01 python2[3798]:     rc_num, _, _ = rc_entry
> Aug 10 23:18:34 kt-docker-01 python2[3798]: TypeError: 'dbus.Int32' object is not iterable
> Aug 10 23:18:34 kt-docker-01 systemd[1]: docker-drbdmanage-plugin.service: Main process exited, code=exited, status=1/FAILURE
> Aug 10 23:18:34 kt-docker-01 systemd[1]: docker-drbdmanage-plugin.service: Unit entered failed state.
> Aug 10 23:18:34 kt-docker-01 systemd[1]: docker-drbdmanage-plugin.service: Failed with result 'exit-code'.
> Aug 10 23:18:34 kt-docker-01 systemd[1]: docker-drbdmanage-plugin.service: Start request repeated too quickly.
> Aug 10 23:18:34 kt-docker-01 systemd[1]: Failed to start DRBDmanage Docker Volume Plugin.
> Aug 10 23:18:34 kt-docker-01 systemd[1]: docker-drbdmanage-plugin.socket: Unit entered failed state.
> 
> 
> Is there anything I can do my end to make this work or is it maybe an
> incompatibility between the docker plugin and the latest versions of
> drbdmanage? I see that the docker plugin hasn’t been updated for a
> while.

Yeah, good old dbus... You are right, that is most likely due to changes
in drbdmanage not reflected everywhere. I will try to fix that soon.

Thanks for reporting, rck



More information about the drbd-user mailing list