[Gluster-users] Strange side-effect to "option base-port 50152"

[Paul Boven]

Hi Vijay, everyone,

On 01/26/2014 04:22 PM, Vijay Bellur wrote:
> On 01/26/2014 07:57 PM, Paul Boven wrote:

>> The result of this was that migrations completely stopped
>> working. Trying to do a migration would cause the process on the sending
>> machine to hang, and on the receiving machine, libvirt became completely
>> unresponsive, even 'virsh list' would simply hang.
>>
>> Curiously, 'gluster volume status' showed that, despite setting the
>> base-port to 50152, the bricks were still listening on 49152, as before
>> the config change & reboot.
>
> Restart of both glusterd and the volume would be necessary to change the
> ports where the bricks listen.

As I wrote, I did a complete reboot of both machines, to make sure that 
this configuration change was accepted.

> I am still not certain as to what caused the migration to hang. Do you
> notice anything unusual in the log files when the hang happens?

The message I get after setting the base-port is still:
-incoming tcp:0.0.0.0:49152: Failed to bind socket: Address already in use

Regards, Paul Boven.