search for: glusterd_op_reset_brick

Displaying 6 results from an estimated 6 matches for "glusterd_op_reset_brick".

2017 Jul 05
1
op-version for reset-brick (Was: Re: [ovirt-users] Upgrading HC from 4.0 to 4.1)
..._v3_commit] > 0-management: Commit failed for operation Reset Brick on local node > [2017-07-05 15:04:07.178214] E [MSGID: 106123] > [glusterd-replace-brick.c:649:glusterd_mgmt_v3_initiate_replace_brick_cmd_phases] > 0-management: Commit Op Failed > > While going through the code, glusterd_op_reset_brick () failed resulting > into these logs. Now I don't see any error logs generated from > glusterd_op_reset_brick () which makes me thing that have we failed from a > place where we log the failure in debug mode. Would you be able to restart > glusterd service with debug log mode and r...
2017 Jul 05
1
op-version for reset-brick (Was: Re: [ovirt-users] Upgrading HC from 4.0 to 4.1)
...erd-mgmt.c:1532:glusterd_mgmt_v3_commit] 0-management: Commit failed for operation Reset Brick on local node [2017-07-05 15:04:07.178214] E [MSGID: 106123] [glusterd-replace-brick.c:649:glusterd_mgmt_v3_initiate_replace_brick_cmd_phases] 0-management: Commit Op Failed While going through the code, glusterd_op_reset_brick () failed resulting into these logs. Now I don't see any error logs generated from glusterd_op_reset_brick () which makes me thing that have we failed from a place where we log the failure in debug mode. Would you be able to restart glusterd service with debug log mode and reran this test and s...
2017 Jul 06
1
op-version for reset-brick (Was: Re: [ovirt-users] Upgrading HC from 4.0 to 4.1)
...: Commit >> failed for operation Reset Brick on local node >> [2017-07-05 15:04:07.178214] E [MSGID: 106123] >> [glusterd-replace-brick.c:649:glusterd_mgmt_v3_initiate_replace_brick_cmd_phases] >> 0-management: Commit Op Failed >> >> While going through the code, glusterd_op_reset_brick () failed resulting >> into these logs. Now I don't see any error logs generated from >> glusterd_op_reset_brick () which makes me thing that have we failed from a >> place where we log the failure in debug mode. Would you be able to restart >> glusterd service with debu...
2017 Jul 05
1
op-version for reset-brick (Was: Re: [ovirt-users] Upgrading HC from 4.0 to 4.1)
On Wed, Jul 5, 2017 at 5:22 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > And what does glusterd log indicate for these failures? > See here in gzip format https://drive.google.com/file/d/0BwoPbcrMv8mvYmlRLUgyV0pFN0k/view?usp=sharing It seems that on each host the peer files have been updated with a new entry "hostname2": [root at ovirt01 ~]# cat
2017 Jul 07
0
op-version for reset-brick (Was: Re: [ovirt-users] Upgrading HC from 4.0 to 4.1)
...:1512: > glusterd_volume_brickinfo_get_by_brick] 0-glusterd: Returning -1 > [2017-07-06 13:04:30.222250] D [MSGID: 0] [glusterd-replace-brick.c:416: > glusterd_op_perform_replace_brick] 0-glusterd: Returning -1 > [2017-07-06 13:04:30.222257] C [MSGID: 106074] [glusterd-reset-brick.c:372:glusterd_op_reset_brick] > 0-management: Unable to add dst-brick: ovirt01.localdomain.local:/gluster/brick3/export > to volume: export > > > Does it share up more light? > > Thanks, > Gianluca > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.glus...
2017 Jul 10
0
op-version for reset-brick (Was: Re: [ovirt-users] Upgrading HC from 4.0 to 4.1)
...:gluster > d_volume_brickinfo_get_by_brick] 0-glusterd: Returning -1 > [2017-07-06 13:04:30.222250] D [MSGID: 0] [glusterd-replace-brick.c:416: > glusterd_op_perform_replace_brick] 0-glusterd: Returning -1 > [2017-07-06 13:04:30.222257] C [MSGID: 106074] > [glusterd-reset-brick.c:372:glusterd_op_reset_brick] 0-management: Unable > to add dst-brick: ovirt01.localdomain.local:/gluster/brick3/export to > volume: export > > > Does it share up more light? > > Thanks, > Gianluca > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.glus...