Displaying 20 results from an estimated 30 matches for "glusterd_brick_start".
2018 Mar 21
2
Brick process not starting after reinstall
...c49-82da-4112d22dfd2c, host:
borg-sphere-three, port: 0
[2018-03-20 13:34:12.198929] C [MSGID: 106003]
[glusterd-server-quorum.c:354:glusterd_do_volume_quorum_action]
0-management: Server quorum regained for volume engine. Starting
local bricks.
[2018-03-20 13:34:12.199166] I
[glusterd-utils.c:5941:glusterd_brick_start] 0-management: starting
a fresh brick process for brick /srv/gluster_engine/brick
[2018-03-20 13:34:12.202498] I
[rpc-clnt.c:1044:rpc_clnt_connection_init] 0-management: setting
frame-timeout to 600
[2018-03-20 13:34:12.208389] C [MSGID: 106003]
[glusterd-server-quorum.c:354:glusterd_do_volume_quor...
2018 Mar 21
0
Brick process not starting after reinstall
...org-sphere-three, port: 0
> [2018-03-20 13:34:12.198929] C [MSGID: 106003]
> [glusterd-server-quorum.c:354:glusterd_do_volume_quorum_action]
> 0-management: Server quorum regained for volume engine. Starting
> local bricks.
> [2018-03-20 13:34:12.199166] I
> [glusterd-utils.c:5941:glusterd_brick_start] 0-management: starting
> a fresh brick process for brick /srv/gluster_engine/brick
> [2018-03-20 13:34:12.202498] I
> [rpc-clnt.c:1044:rpc_clnt_connection_init] 0-management: setting
> frame-timeout to 600
> [2018-03-20 13:34:12.208389] C [MSGID: 106003]
> [glusterd-server-quorum...
2017 Dec 15
3
Production Volume will not start
...node. When attempting to start the volume it will eventually return:
Error: Request timed out
For some time after that, the volume is locked and we either have to wait or restart Gluster services. In the gluserd.log, it shows the following:
[2017-12-15 18:00:12.423478] I [glusterd-utils.c:5926:glusterd_brick_start] 0-management: starting a fresh brick process for brick /exp/b1/gv0
[2017-12-15 18:03:12.673885] I [glusterd-locks.c:729:gd_mgmt_v3_unlock_timer_cbk] 0-management: In gd_mgmt_v3_unlock_timer_cbk
[2017-12-15 18:06:34.304868] I [MSGID: 106499] [glusterd-handler.c:4303:__glusterd_handle_status_volume]...
2018 Mar 20
0
brick processes not starting
...c49-82da-4112d22dfd2c, host:
borg-sphere-three, port: 0
[2018-03-20 13:34:12.198929] C [MSGID: 106003]
[glusterd-server-quorum.c:354:glusterd_do_volume_quorum_action]
0-management: Server quorum regained for volume engine. Starting
local bricks.
[2018-03-20 13:34:12.199166] I
[glusterd-utils.c:5941:glusterd_brick_start] 0-management: starting
a fresh brick process for brick /srv/gluster_engine/brick
[2018-03-20 13:34:12.202498] I
[rpc-clnt.c:1044:rpc_clnt_connection_init] 0-management: setting
frame-timeout to 600
[2018-03-20 13:34:12.208389] C [MSGID: 106003]
[glusterd-server-quorum.c:354:glusterd_do_volume_quor...
2017 Dec 18
0
Production Volume will not start
...ventually return:
>
> Error: Request timed out
>
>
>
> For some time after that, the volume is locked and we either have to wait
> or restart Gluster services. In the gluserd.log, it shows the following:
>
>
>
> [2017-12-15 18:00:12.423478] I [glusterd-utils.c:5926:glusterd_brick_start]
> 0-management: starting a fresh brick process for brick /exp/b1/gv0
>
> [2017-12-15 18:03:12.673885] I [glusterd-locks.c:729:gd_mgmt_v3_unlock_timer_cbk]
> 0-management: In gd_mgmt_v3_unlock_timer_cbk
>
> [2017-12-15 18:06:34.304868] I [MSGID: 106499] [glusterd-handler.c:4303:__...
2013 Aug 08
2
not able to restart the brick for distributed volume
...d: Commit failed on localhost. Please check the
log file for more details.
Logs says that it was unable to start the brick
[2013-08-08 14:19:42.280852] I [glusterd-pmap.c:271:pmap_registry_remove]
0-pmap: removing brick (null) on port 49160
[2013-08-08 14:19:42.283583] E
[glusterd-utils.c:4023:glusterd_brick_start] 0-management: Unable to start
brick 192.168.24.80:/.krfs/_home
[2013-08-08 14:19:42.283637] E [glusterd-syncop.c:830:gd_sync_task_begin]
0-management: Commit of operation 'Volume Start' failed on localhost
and the gluster volume remains as stopped
root at ksc-base-unit0:/.krfs> glus...
2018 Jan 29
2
Replacing a third data node with an arbiter one
...glusterd_op_perform_add_bricks]
0-management: arbiter-count is set 1
[2018-01-29 15:15:52.999862] I [MSGID: 106578]
[glusterd-brick-ops.c:1364:glusterd_op_perform_add_bricks]
0-management: type is set 0, need to change it
[2018-01-29 15:15:55.140751] I
[glusterd-utils.c:5941:glusterd_brick_start] 0-management: starting
a fresh brick process for brick /gluster/thedude
[2018-01-29 15:15:55.194678] E [MSGID: 106005]
[glusterd-utils.c:5947:glusterd_brick_start] 0-management: Unable to
start brick arbiter-1.network.hoggins.fr:/gluster/thedude
[2018-01-29 15:15:55.194823] E [...
2018 Jan 29
0
Replacing a third data node with an arbiter one
...0-management: arbiter-count is set 1
> [2018-01-29 15:15:52.999862] I [MSGID: 106578]
> [glusterd-brick-ops.c:1364:glusterd_op_perform_add_bricks]
> 0-management: type is set 0, need to change it
> [2018-01-29 15:15:55.140751] I
> [glusterd-utils.c:5941:glusterd_brick_start] 0-management: starting
> a fresh brick process for brick /gluster/thedude
> [2018-01-29 15:15:55.194678] E [MSGID: 106005]
> [glusterd-utils.c:5947:glusterd_brick_start] 0-management: Unable to
> start brick arbiter-1.network.hoggins.fr:/gluster/thedude
You need to...
2017 Jun 04
2
Adding a new replica to the cluster
Apologies for the delay!
>From the logs:
[2017-05-31 13:06:35.839780] E [MSGID: 106005]
[glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start
brick 156.125.102.103:/data/br0/vm0
[2017-05-31 13:06:35.839869] E [MSGID: 106074]
[glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to
add bricks
This looks like in serv3 the newly added brick failed to come up. You'd
have to look at the sa...
2018 Jan 26
0
Replacing a third data node with an arbiter one
On 01/24/2018 07:20 PM, Hoggins! wrote:
> Hello,
>
> The subject says it all. I have a replica 3 cluster :
>
> gluster> volume info thedude
>
> Volume Name: thedude
> Type: Replicate
> Volume ID: bc68dfd3-94e2-4126-b04d-77b51ec6f27e
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 3 = 3
>
2018 Jan 24
4
Replacing a third data node with an arbiter one
Hello,
The subject says it all. I have a replica 3 cluster :
gluster> volume info thedude
?
Volume Name: thedude
Type: Replicate
Volume ID: bc68dfd3-94e2-4126-b04d-77b51ec6f27e
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: ngluster-1.network.hoggins.fr:/export/brick/thedude
Brick2:
2017 Jun 06
0
Adding a new replica to the cluster
...* dimanche 4 juin 2017 15:31:34
> *? :* Merwan Ouddane
> *Cc :* gluster-users
>
> *Objet :* Re: [Gluster-users] Adding a new replica to the cluster
>
> Apologies for the delay!
>
> From the logs:
>
> [2017-05-31 13:06:35.839780] E [MSGID: 106005] [glusterd-utils.c:4877:glusterd_brick_start]
> 0-management: Unable to start brick 156.125.102.103:/data/br0/vm0
>
>
> [2017-05-31 13:06:35.839869] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick]
> 0-glusterd: Unable to add bricks
>
> This looks like in serv3 the newly added brick failed to come up....
2017 Jun 06
1
Adding a new replica to the cluster
...Mukherjee <amukherj at redhat.com>
Envoy? : dimanche 4 juin 2017 15:31:34
? : Merwan Ouddane
Cc : gluster-users
Objet : Re: [Gluster-users] Adding a new replica to the cluster
Apologies for the delay!
>From the logs:
[2017-05-31 13:06:35.839780] E [MSGID: 106005] [glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start brick 156.125.102.103:/data/br0/vm0
[2017-05-31 13:06:35.839869] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks
This looks like in serv3 the newly added brick failed to come up. You'd have to look at the sam...
2017 Sep 13
1
[3.11.2] Bricks disconnect from gluster with 0-transport: EPOLLERR
...gt; glusterd starts fine and all bricks come up. Hence I suspect a race
> condition
> somewhere. The glusterd.log file (attached) shows that the brick connects,
> and
> then suddenly disconnects from the cluster:
> ----------
> [2017-08-06 03:12:38.536409] I [glusterd-utils.c:5468:glusterd_brick_start]
> 0-management: discovered already-running brick /srv/gluster/gv2/brick1/gvol
> [2017-08-06 03:12:38.536414] I [MSGID: 106143] [glusterd-pmap.c:279:pmap_registry_bind]
> 0-pmap: adding brick /srv/gluster/gv2/brick1/gvol on port 49153
> [2017-08-06 03:12:38.536427] I [rpc-clnt.c:1059:rp...
2018 Apr 25
2
Turn off replication
...50:pmap_registry_bind] 0-pmap: adding brick /gdata/brick1/scratch on port 49152
[2018-04-25 22:08:55.309659] I [MSGID: 106143] [glusterd-pmap.c:250:pmap_registry_bind] 0-pmap: adding brick /gdata/brick1/scratch.rdma on port 49153
[2018-04-25 22:08:55.310231] E [MSGID: 106005] [glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start brick gluster02ib:/gdata/brick1/scratch
[2018-04-25 22:08:55.310275] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks
[2018-04-25 22:08:55.310304] E [MSGID: 106123] [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-manage...
2014 Apr 28
2
volume start causes glusterd to core dump in 3.5.0
...et_filepath+0x72)[0x7eff45e02b72]
/usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(glusterd_set_brick_socket_filepath+0x158)[0x7eff45e02df8]
/usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(glusterd_volume_start_glusterfs+0x4c9)[0x7eff45e094a9]
/usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(glusterd_brick_start+0x119)[0x7eff45e0af29]
/usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(glusterd_op_start_volume+0xfd)[0x7eff45e45a8d]
/usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(glusterd_op_commit_perform+0x53b)[0x7eff45df471b]
/usr/lib64/glusterfs/3.5.0/xlator/mgmt/glusterd.so(gd_commit_op_phase+0xbe)[0...
2018 Apr 27
0
Turn off replication
...adding brick
> /gdata/brick1/scratch on port 49152
> [2018-04-25 22:08:55.309659] I [MSGID: 106143]
> [glusterd-pmap.c:250:pmap_registry_bind] 0-pmap: adding brick
> /gdata/brick1/scratch.rdma on port 49153
> [2018-04-25 22:08:55.310231] E [MSGID: 106005]
> [glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start
> brick gluster02ib:/gdata/brick1/scratch
> [2018-04-25 22:08:55.310275] E [MSGID: 106074]
> [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add
> bricks
> [2018-04-25 22:08:55.310304] E [MSGID: 106123]
> [glusterd-mgmt.c:294:...
2018 Apr 30
2
Turn off replication
...gdata/brick1/scratch on port 49152
>> [2018-04-25 22:08:55.309659] I [MSGID: 106143]
>> [glusterd-pmap.c:250:pmap_registry_bind] 0-pmap: adding brick
>> /gdata/brick1/scratch.rdma on port 49153
>> [2018-04-25 22:08:55.310231] E [MSGID: 106005]
>> [glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start
>> brick gluster02ib:/gdata/brick1/scratch
>> [2018-04-25 22:08:55.310275] E [MSGID: 106074]
>> [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add
>> bricks
>> [2018-04-25 22:08:55.310304] E [MSGID: 106123]
>&g...
2018 May 02
0
Turn off replication
...adding brick
> /gdata/brick1/scratch on port 49152
> [2018-04-25 22:08:55.309659] I [MSGID: 106143]
> [glusterd-pmap.c:250:pmap_registry_bind] 0-pmap: adding brick
> /gdata/brick1/scratch.rdma on port 49153
> [2018-04-25 22:08:55.310231] E [MSGID: 106005]
> [glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start
> brick gluster02ib:/gdata/brick1/scratch
> [2018-04-25 22:08:55.310275] E [MSGID: 106074]
> [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add
> bricks
> [2018-04-25 22:08:55.310304] E [MSGID: 106123]
> [glusterd-mgmt.c:294:...
2018 Apr 25
0
Turn off replication
...50:pmap_registry_bind] 0-pmap: adding brick /gdata/brick1/scratch on port 49152
[2018-04-25 20:56:54.390798] I [MSGID: 106143] [glusterd-pmap.c:250:pmap_registry_bind] 0-pmap: adding brick /gdata/brick1/scratch.rdma on port 49153
[2018-04-25 20:56:54.391401] E [MSGID: 106005] [glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start brick gluster02ib:/gdata/brick1/scratch
[2018-04-25 20:56:54.391457] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks
[2018-04-25 20:56:54.391476] E [MSGID: 106123] [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-manage...