Dear Jim, 

Thank you for your help, now it's working again!!! :) 
Have a nice day! 

Regards, 

Tibor 

----- 2018. máj.. 29., 23:57, Jim Kusznir <[email protected]> írta: 

> I had the same problem when I upgraded to 4.2. I found that if I went to the
> brick in the UI and selected it, there was a "start" button in the upper-right
> of the gui. clicking that resolved this problem a few minutes later.
> I had to repeat for each volume that showed a brick down for which that brick
> was not actually down.

> --Jim

> On Tue, May 29, 2018 at 6:34 AM, Demeter Tibor < [ mailto:[email protected] 
> |
> [email protected] ] > wrote:

>> Hi,

>> I've successfully upgraded my hosts and I could raise the cluster level to 
>> 4.2.
>> Everything seems fine, but the monitoring problem does not resolved. My 
>> bricks
>> on first node are shown down (red) , but the glusterfs working fine (I 
>> verified
>> in terminal).

>> I've attached my engine.log.

>> Thanks in advance,

>> R,
>> Tibor

>> ----- 2018. máj.. 28., 14:59, Demeter Tibor < [ mailto:[email protected] |
>> [email protected] ] > írta:

>>> Hi,
>>> Ok I will try it.

>>> In this case, is it possible to remove and re-add a host that member of HA
>>> gluster ? This is an another task, but I need to separate my gluster network
>>> from my ovirtmgmt network.
>>> What is the recommended way for do this?

>>> It is not important now, but I need to do in future.

>>> I will attach my engine.log after upgrade my host.

>>> Thanks,
>>> Regards.

>>> Tibor

>>> ----- 2018. máj.. 28., 14:44, Sahina Bose < [ mailto:[email protected] |
>>> [email protected] ] > írta:

>>>> On Mon, May 28, 2018 at 4:47 PM, Demeter Tibor < [ 
>>>> mailto:[email protected] |
>>>> [email protected] ] > wrote:

>>>>> Dear Sahina,

>>>>> Yes, exactly. I can check that check box, but I don't know how is safe 
>>>>> that. Is
>>>>> it safe?

>>>> It is safe - if you can ensure that only one host is put into maintenance 
>>>> at a
>>>> time.

>>>>> I want to upgrade all of my host. If it will done, then the monitoring 
>>>>> will work
>>>>> perfectly?

>>>> If it does not please provide engine.log again once you've upgraded all the
>>>> hosts.

>>>>> Thanks.
>>>>> R.

>>>>> Tibor

>>>>> ----- 2018. máj.. 28., 10:09, Sahina Bose < [ mailto:[email protected] |
>>>>> [email protected] ] > írta:

>>>>>> On Mon, May 28, 2018 at 1:06 PM, Demeter Tibor < [ 
>>>>>> mailto:[email protected] |
>>>>>> [email protected] ] > wrote:

>>>>>>> Hi,

>>>>>>> Somebody could answer to my question please?
>>>>>>> It is very important for me, I could no finish my upgrade process (from 
>>>>>>> 4.1 to
>>>>>>> 4.2) since 9th May!

>>>>>> Can you explain how the upgrade process is blocked due to the monitoring?
>>>>>> If it's because you cannot move the host to maintenance, can you try 
>>>>>> with the
>>>>>> option "Ignore quorum checks" enabled?

>>>>>>> Meanwhile - I don't know why - one of my two gluster volume seems UP 
>>>>>>> (green) on
>>>>>>> the GUI. So, now only one is down.

>>>>>>> I need help. What can I do?

>>>>>>> Thanks in advance,

>>>>>>> Regards,

>>>>>>> Tibor

>>>>>>> ----- 2018. máj.. 23., 21:09, Demeter Tibor < [ 
>>>>>>> mailto:[email protected] |
>>>>>>> [email protected] ] > írta:

>>>>>>>> Hi,

>>>>>>>> I've updated again to the latest version, but there are no changes. 
>>>>>>>> All of
>>>>>>>> bricks on my first node are down in the GUI (in console are ok)
>>>>>>>> An Interesting thing, the "Self-Heal info" column show "OK" for all 
>>>>>>>> hosts and
>>>>>>>> all bricks, but "Space used" column is zero for all hosts/bricks.
>>>>>>>> Can I force remove and re-add my host to cluster awhile it is a 
>>>>>>>> gluster member?
>>>>>>>> Is it safe ?
>>>>>>>> What can I do?

>>>>>>>> I haven't update other hosts while gluster not working fine, or the 
>>>>>>>> GUI does not
>>>>>>>> detect . So my other hosts is remained 4.1 yet :(

>>>>>>>> Thanks in advance,

>>>>>>>> Regards

>>>>>>>> Tibor

>>>>>>>> ----- 2018. máj.. 23., 14:45, Denis Chapligin < [ 
>>>>>>>> mailto:[email protected] |
>>>>>>>> [email protected] ] > írta:

>>>>>>>>> Hello!

>>>>>>>>> On Tue, May 22, 2018 at 11:10 AM, Demeter Tibor < [ 
>>>>>>>>> mailto:[email protected] |
>>>>>>>>> [email protected] ] > wrote:

>>>>>>>>>> Is there any changes with this bug?

>>>>>>>>>> Still I haven't finish my upgrade process that i've started on 9th 
>>>>>>>>>> may:(

>>>>>>>>>> Please help me if you can.

>>>>>>>>> Looks like all required patches are already merged, so could you 
>>>>>>>>> please to
>>>>>>>>> update your engine again to the latest night build?

>>>>>>>> _______________________________________________
>>>>>>>> Users mailing list -- [ mailto:[email protected] | [email protected] ]
>>>>>>>> To unsubscribe send an email to [ mailto:[email protected] |
>>>>>>>> [email protected] ]

>>>>>>> _______________________________________________
>>>>>>> Users mailing list -- [ mailto:[email protected] | [email protected] ]
>>>>>>> To unsubscribe send an email to [ mailto:[email protected] |
>>>>>>> [email protected] ]
>>>>>>> Privacy Statement: [ https://www.ovirt.org/site/privacy-policy/ |
>>>>>>> https://www.ovirt.org/site/privacy-policy/ ]
>>>>>>> oVirt Code of Conduct: [
>>>>>>> https://www.ovirt.org/community/about/community-guidelines/ |
>>>>>>> https://www.ovirt.org/community/about/community-guidelines/ ]
>>>>>>> List Archives: [
>>>>>>> https://lists.ovirt.org/archives/list/[email protected]/message/MRAAPZSRIXLAJZBV6TRDXXK7R2ISPSDK/
>>>>>>> |
>>>>>>> https://lists.ovirt.org/archives/list/[email protected]/message/MRAAPZSRIXLAJZBV6TRDXXK7R2ISPSDK/
>>>>>>> ]

>>> _______________________________________________
>>> Users mailing list -- [ mailto:[email protected] | [email protected] ]
>>> To unsubscribe send an email to [ mailto:[email protected] |
>>> [email protected] ]
>>> Privacy Statement: [ https://www.ovirt.org/site/privacy-policy/ |
>>> https://www.ovirt.org/site/privacy-policy/ ]
>>> oVirt Code of Conduct: [
>>> https://www.ovirt.org/community/about/community-guidelines/ |
>>> https://www.ovirt.org/community/about/community-guidelines/ ]
>>> List Archives: [
>>> https://lists.ovirt.org/archives/list/[email protected]/message/OWA2I6AFZPO56Z2N6D25HUHLW6CGOUWL/
>>> |
>>> https://lists.ovirt.org/archives/list/[email protected]/message/OWA2I6AFZPO56Z2N6D25HUHLW6CGOUWL/
>>> ]
>> _______________________________________________
>> Users mailing list -- [ mailto:[email protected] | [email protected] ]
>> To unsubscribe send an email to [ mailto:[email protected] |
>> [email protected] ]
>> Privacy Statement: [ https://www.ovirt.org/site/privacy-policy/ |
>> https://www.ovirt.org/site/privacy-policy/ ]
>> oVirt Code of Conduct: [
>> https://www.ovirt.org/community/about/community-guidelines/ |
>> https://www.ovirt.org/community/about/community-guidelines/ ]
>> List Archives: [
>> https://lists.ovirt.org/archives/list/[email protected]/message/DP6DDTNTQUUQZN6BPOTPHUY4XD7A7RQB/
>> |
>> https://lists.ovirt.org/archives/list/[email protected]/message/DP6DDTNTQUUQZN6BPOTPHUY4XD7A7RQB/
>> ]
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/KKMWNPOCQN7ZCEQZIF6W35HHZSYFRZIA/

Reply via email to