Hi Kaleb,
Thanks, this refers to 3.11.x
On Mon, Jul 3, 2017 at 4:16 PM, Kaleb S. KEITHLEY
wrote:
> On 07/03/2017 06:29 AM, Kaleb S. KEITHLEY wrote:
>
>> On 07/03/2017 04:34 AM, Atin Mukherjee wrote:
>>
>>>
>>> On Mon, 3 Jul 2017 at 12:28, Pawan Al
2017 at 5:26 PM, Atin Mukherjee wrote:
>
>
> On Wed, May 31, 2017 at 3:53 PM, Pawan Alwandi wrote:
>
>> Hello Atin,
>>
>> Sure. A note though, we are running gluster on Debain Jessie/Wheezy
>> hosts, but if you let me know what info you would nee
report from all the nodes to debug and figure out what's
> going wrong. You'd have to give me some time as I have some critical
> backlog items to work on.
>
> On Wed, 31 May 2017 at 11:30, Pawan Alwandi wrote:
>
>> Hello Atin,
>>
>> I've tried res
does look like that there is
> an issue w.r.t peer connections. Does restarting all the glusterd one by
> one solve this?
>
> On Mon, May 29, 2017 at 4:50 PM, Pawan Alwandi wrote:
>
>> Sorry for big attachment in previous mail...last 1000 lines of those logs
>> attached no
PM, Atin Mukherjee wrote:
> Are the other glusterd instances are up? output of gluster peer status &
> gluster volume status please?
>
> On Wed, May 24, 2017 at 4:20 PM, Pawan Alwandi wrote:
>
>> Thanks Atin,
>>
>> So I got gluster downgraded to 3.7.9 on hos
whats up here?
Pawan
On Mon, May 22, 2017 at 9:42 PM, Atin Mukherjee wrote:
>
>
> On Mon, May 22, 2017 at 9:05 PM, Pawan Alwandi wrote:
>
>>
>> On Mon, May 22, 2017 at 8:36 PM, Atin Mukherjee
>> wrote:
>>
>>>
>>>
>>> On Mon, May 22,
bove workaround should
>> suffice. I'll be sending a patch pretty soon.
>>
>
> Posted a patch https://review.gluster.org/#/c/17358 .
>
>
>>
>>
>>
>> On Mon, May 22, 2017 at 11:35 AM, Pawan Alwandi
>> wrote:
>>
>>> Hello Atin,
>>>
>&
you can provide me the content of /var/lib/glusterd from
> all the nodes to get to the root cause of this issue.
>
> On Fri, May 19, 2017 at 12:09 PM, Pawan Alwandi wrote:
>
>> Hello Atin,
>>
>> Thanks for continued support. I've attached requested files from all
May 2017 at 23:40, Atin Mukherjee wrote:
>
>> On Wed, 17 May 2017 at 12:47, Pawan Alwandi wrote:
>>
>>> Hello Atin,
>>>
>>> I realized that these http://gluster.readthedocs.io/
>>> en/latest/Upgrade-Guide/upgrade_to_3.10/ instructions only work for
Mon, May 15, 2017 at 10:31 PM, Atin Mukherjee
wrote:
>
> On Mon, 15 May 2017 at 11:58, Pawan Alwandi wrote:
>
>> Hi Atin,
>>
>> I see below error. Do I require gluster to be upgraded on all 3 hosts
>> for this to work? Right now I have host 1 running 3.10.1 and h
sterd on
>> all the nodes and check the brick status?
>>
>
> s/30101/31001
>
>
>>
>> On Sun, May 14, 2017 at 8:55 PM, Pawan Alwandi wrote:
>>
>>> Hello Atin,
>>>
>>> Thanks for looking at this. Below is the output you requested for.
On Sat, May 13, 2017 at 6:28 PM, Atin Mukherjee wrote:
> I have already asked for the following earlier:
>
> Can you please provide output of following from all the nodes:
>
> cat /var/lib/glusterd/glusterd.info
> cat /var/lib/glusterd/peers/*
>
> On Sat, 13 May 2017 a
Hello folks,
Does anyone have any idea whats going on here?
Thanks,
Pawan
On Wed, May 10, 2017 at 5:02 PM, Pawan Alwandi wrote:
> Hello,
>
> I'm trying to upgrade gluster from 3.6.2 to 3.10.1 but don't see the
> glusterfsd and glusterfs processes coming up.
> http://
Hello,
I'm trying to upgrade gluster from 3.6.2 to 3.10.1 but don't see the
glusterfsd and glusterfs processes coming up.
http://gluster.readthedocs.io/en/latest/Upgrade-Guide/upgrade_to_3.10/ is
the process that I'm trying to follow.
This is a 3 node server setup with a replicated volume having
14 matches
Mail list logo
