ble :/
>>
>>
>>
>> Regards
>>
>> Jo
>>
>>
>>
>>
>>
>> -Original message-
>> *From:* Atin Mukherjee <amukh...@redhat.com>
>> *Sent:* Tue 23-01-2018 05:15
>> *Subject:* Re: [Gluster-users] BUG: After stop an
t 3.10 and hope to stay stable :/
>
>
>
> Regards
>
> Jo
>
>
>
>
>
> -Original message-
> *From:* Atin Mukherjee <amukh...@redhat.com>
> *Sent:* Tue 23-01-2018 05:15
> *Subject:* Re: [Gluster-users] BUG: After stop and start wrong port is
> adverti
Can remember the days I wrote
kernel drivers myself in c :)
Regards
Jo Goossens
-----Original message-
From:Atin Mukherjee <amukh...@redhat.com <mailto:amukh...@redhat.com> >
Sent:Fri 27-10-2017 21:01
Subject:Re: [Gluster-users] BUG: After stop and start wrong port is advertised
T
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Could you confirm this should have been fixed in 3.10.8? If so we'll
>>>>> test it for sure!
>>>>>
>>>>
>>>> Fix should be part of 3.10.8 which is awaiti
10.7 - no I guess as the patch is still in review and 3.10.7 is
>>> getting tagged today. You’ll get this fix in 3.10.8.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> PS: Wow nice all that c code and those "goto out&qu
t;>
>>
>>
>>
>>
>>
>> -----Original message-----
>> *From:* Atin Mukherjee <amukh...@redhat.com>
>>
>> *Sent:* Mon 30-10-2017 17:40
>> *Subject:* Re: [Gluster-users] BUG: After stop and start wrong port is
>> advertised
>&
nnouncement.
>
> Regards
>
> Jo
>
>
>
>
>
>
> -Original message-
> *From:* Atin Mukherjee <amukh...@redhat.com>
>
> *Sent:* Mon 30-10-2017 17:40
> *Subject:* Re: [Gluster-users] BUG: After stop and start wrong port is
> advertised
> *To:* Jo
t the best way often I think). Can remember the days I wrote
kernel drivers myself in c :)
Regards
Jo Goossens
-Original message-
From:Atin Mukherjee <amukh...@redhat.com <mailto:amukh...@redhat.com> >
Sent:Fri 27-10-2017 21:01
Subject:Re: [Gluster-users] BUG: After
com>
> To: "Mike Hulsman" <mike.huls...@proxy.nl>
> Cc: "Jo Goossens" <jo.gooss...@hosted-power.com>, "gluster-users"
> <gluster-users@gluster.org>
> Sent: Wednesday, November 8, 2017 2:12:02 PM
> Subject: Re: [Gluster-users] BUG: After stop
otterdam+The+Netherlands=gmail=g>
> | +31 10 307 0965
>
> ------
>
> *From: *"Jo Goossens" <jo.gooss...@hosted-power.com>
> *To: *"Atin Mukherjee" <amukh...@redhat.com>
> *Cc: *gluster-users@gluster.org
> *Sent: *F
el drivers myself in c :)
>
>
>
>
>
> Regards
>
> Jo Goossens
>
>
>
>
>
>
>
>
> -Original message-----
> *From:* Atin Mukherjee <amukh...@redhat.com>
> *Sent:* Fri 27-10-2017 21:01
> *Subject:* Re: [Gluster-users] BUG: After stop and start wrong port
We (finally) figured out the root cause, Jo!
Patch https://review.gluster.org/#/c/18579 posted upstream for review.
On Thu, Sep 21, 2017 at 2:08 PM, Jo Goossens
wrote:
> Hi,
>
>
>
>
>
> We use glusterfs 3.10.5 on Debian 9.
>
>
>
> When we stop or restart the
Regards
>
> Jo
>
>
>
>
>
>
>
>
> -Original message-
> From: Darrell Budic <bu...@onholyground.com>
> Sent: Fri 22-09-2017 17:24
> Subject: Re: [Gluster-users] BUG: After stop and start wrong port is
> advertised
> To: Atin Mukherjee <amu
I encountered this once in the past, an additional symptom was peers were in
disconnected state on the peers that were NOT using the wrong ports.
Disconnected peers is how it detected it in the first place.
It happened to me after rebooting, and I fixed it but wasn’t able to stop and
gather
017 17:24
Subject:Re: [Gluster-users] BUG: After stop and start wrong port is advertised
To:Atin Mukherjee <amukh...@redhat.com>;
CC:Jo Goossens <jo.gooss...@hosted-power.com>; gluster-users@gluster.org;
I encountered this once in the past, an additional symptom was peers were in
I've already replied to your earlier email. In case you've not seen it in
your mailbox here it goes:
This looks like a bug to me. For some reason glusterd's portmap is
referring to a stale port (IMO) where as brick is still listening to the
correct port. But ideally when glusterd service is
Hi,
We use glusterfs 3.10.5 on Debian 9.
When we stop or restart the service, e.g.: service glusterfs-server restart
We see that the wrong port get's advertised afterwards. For example:
Before restart:
Status of volume: public
Gluster process TCP Port
17 matches
Mail list logo