Description of problem: during setting up multiplexed volume for openshift setting up gluster volume set all transport.listen-backlog kills gluster Version-Release number of selected component (if applicable): glusterfs-3.8.4-44.el7rhgs.x86_64 Fri Nov 3 07:59:52 2017 glusterfs-api-3.8.4-44.el7rhgs.x86_64 Tue Oct 31 17:15:15 2017 glusterfs-cli-3.8.4-44.el7rhgs.x86_64 Tue Oct 31 17:15:15 2017 glusterfs-client-xlators-3.8.4-44.el7rhgs.x86_64 Tue Oct 31 17:15:14 2017 glusterfs-fuse-3.8.4-44.el7rhgs.x86_64 Tue Oct 31 17:15:15 2017 glusterfs-geo-replication-3.8.4-44.el7rhgs.x86_64 Tue Oct 31 17:15:15 2017 glusterfs-libs-3.8.4-44.el7rhgs.x86_64 Fri Nov 3 07:59:52 2017 glusterfs-server-3.8.4-44.el7rhgs.x86_64 How reproducible: Set up multiplexed pool. Set gluster volume set all transport.listen-backlog 128 glusterd gets killed Steps to Reproduce: 1. 2. 3. Actual results: After setting backlog option the glusterd process gets killed. Expected results: Set up multiplexing and backlog according to documentation: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html/administration_guide/brick_configuration#many-bricks-per-node-multiplex Additional info: In next comment