search for: glusterd_resolve_all_bricks

...*E [glusterd-store.c:1845:glusterd_store_retrieve_volume] 0-: Unknown key: > brick-0* This makes some sense to me since I have 18 replica 2 volumes resulting in a total of 36 bricks. Then there are a few more "I" messages and this is the rest of the file: *E [glusterd-store.c:2472:glusterd_resolve_all_bricks] 0-glusterd: resolve > brick failed in restore > **E [xlator.c:390:xlator_init] 0-management: Initialization of volume > 'management' failed, review your volfile again > **E [graph.c:292:glusterfs_graph_init] 0-management: initializing > translator failed > **E [graph.c:47...

...tore.c:2197:glusterd_restore_op_version] 0-glusterd: retrieved op-version: 31004 [2017-08-17 09:04:00.711413] I [MSGID: 106194] [glusterd-store.c:3776:glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps list. [2017-08-17 09:04:00.756731] E [MSGID: 106187] [glusterd-store.c:4559:glusterd_resolve_all_bricks] 0-glusterd: resolve brick failed in restore [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again [2017-08-17 09:04:00.756802] E [MSGID: 101066] [graph.c:325:glusterfs_graph_init] 0-ma...

...re_op_version] > 0-glusterd: retrieved op-version: 31004 > [2017-08-17 09:04:00.711413] I [MSGID: 106194] [glusterd-store.c:3776: > glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps > list. > [2017-08-17 09:04:00.756731] E [MSGID: 106187] [glusterd-store.c:4559:glusterd_resolve_all_bricks] > 0-glusterd: resolve brick failed in restore > [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] > 0-management: Initialization of volume 'management' failed, review your > volfile again > [2017-08-17 09:04:00.756802] E [MSGID: 101066] > [graph.c:...

...gt;> retrieved op-version: 31004 >> [2017-08-17 09:04:00.711413] I [MSGID: 106194] >> [glusterd-store.c:3776:glusterd_store_retrieve_missed_snaps_list] >> 0-management: No missed snaps list. >> [2017-08-17 09:04:00.756731] E [MSGID: 106187] >> [glusterd-store.c:4559:glusterd_resolve_all_bricks] 0-glusterd: resolve >> brick failed in restore >> [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] >> 0-management: Initialization of volume 'management' failed, review your >> volfile again >> [2017-08-17 09:04:00.756802] E [MSGID: 10...

...0-glusterd: retrieved op-version: 31004 > > [2017-08-17 09:04:00.711413] I [MSGID: 106194] [glusterd-store.c:3776: > > glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps > > list. > > [2017-08-17 09:04:00.756731] E [MSGID: 106187] [glusterd-store.c:4559:glusterd_resolve_all_bricks] > > 0-glusterd: resolve brick failed in restore > > [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] > > 0-management: Initialization of volume 'management' failed, review your > > volfile again > > [2017-08-17 09:04:00.756802] E [MSGI...

...-version: 31004 >>> [2017-08-17 09:04:00.711413] I [MSGID: 106194] >>> [glusterd-store.c:3776:glusterd_store_retrieve_missed_snaps_list] >>> 0-management: No missed snaps list. >>> [2017-08-17 09:04:00.756731] E [MSGID: 106187] >>> [glusterd-store.c:4559:glusterd_resolve_all_bricks] 0-glusterd: resolve >>> brick failed in restore >>> [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] >>> 0-management: Initialization of volume 'management' failed, review your >>> volfile again >>> [2017-08-17 09:04:00....

...> [2017-08-17 09:04:00.711413] I [MSGID: 106194] [glusterd-store.c:3776: >> > > glusterd_store_retrieve_missed_snaps_list] 0-management: No missed >> snaps >> > > list. >> > > [2017-08-17 09:04:00.756731] E [MSGID: 106187] >> [glusterd-store.c:4559:glusterd_resolve_all_bricks] >> > > 0-glusterd: resolve brick failed in restore >> > > [2017-08-17 09:04:00.756787] E [MSGID: 101019] >> [xlator.c:503:xlator_init] >> > > 0-management: Initialization of volume 'management' failed, review >> your >> > > volfil...

...> > > > [2017-08-17 09:04:00.711413] I [MSGID: 106194] [glusterd-store.c:3776: > > > > glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps > > > > list. > > > > [2017-08-17 09:04:00.756731] E [MSGID: 106187] [glusterd-store.c:4559:glusterd_resolve_all_bricks] > > > > 0-glusterd: resolve brick failed in restore > > > > [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] > > > > 0-management: Initialization of volume 'management' failed, review your > > > > volfile again > &...

...d 4 times between [2017-10-04 15:44:20.168321] and [2017-10-04 15:44:20.185536] [2017-10-04 15:44:20.188517] I [MSGID: 106544] [glusterd.c:158:glusterd_uuid_init] 0-management: retrieved UUID: 29f246da-71b1-4c60-a8c6-e6291f3f8cce [2017-10-04 15:44:20.189091] E [MSGID: 106187] [glusterd-store.c:4566:glusterd_resolve_all_bricks] 0-glusterd: resolve brick failed in restore [2017-10-04 15:44:20.189123] E [MSGID: 101019] [xlator.c:503:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again [2017-10-04 15:44:20.189139] E [MSGID: 101066] [graph.c:325:glusterfs_graph_init] 0-ma...

...] 0-management: setting frame-timeout to 600 [2014-03-04 21:20:37.776185] I [socket.c:3485:socket_init] 0-management: SSL support is NOT enabled [2014-03-04 21:20:37.776201] I [socket.c:3500:socket_init] 0-management: using system polling thread [2014-03-04 21:20:37.780363] E [glusterd-store.c:2548:glusterd_resolve_all_bricks] 0-glusterd: resolve brick failed in restore [2014-03-04 21:20:37.780395] E [xlator.c:423:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again [2014-03-04 21:20:37.780410] E [graph.c:292:glusterfs_graph_init] 0-management: initializing translato...

...d op-version: 31004 > > > [2017-08-17 09:04:00.711413] I [MSGID: 106194] [glusterd-store.c:3776: > > > glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps > > > list. > > > [2017-08-17 09:04:00.756731] E [MSGID: 106187] [glusterd-store.c:4559:glusterd_resolve_all_bricks] > > > 0-glusterd: resolve brick failed in restore > > > [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] > > > 0-management: Initialization of volume 'management' failed, review your > > > volfile again > > > [2017-08-17...

...d op-version: 31004 > > > [2017-08-17 09:04:00.711413] I [MSGID: 106194] [glusterd-store.c:3776: > > > glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps > > > list. > > > [2017-08-17 09:04:00.756731] E [MSGID: 106187] [glusterd-store.c:4559:glusterd_resolve_all_bricks] > > > 0-glusterd: resolve brick failed in restore > > > [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] > > > 0-management: Initialization of volume 'management' failed, review your > > > volfile again > > > [2017-08-17...

...0-glusterd: retrieved op-version: 31004 > > [2017-08-17 09:04:00.711413] I [MSGID: 106194] [glusterd-store.c:3776: > > glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps > > list. > > [2017-08-17 09:04:00.756731] E [MSGID: 106187] [glusterd-store.c:4559:glusterd_resolve_all_bricks] > > 0-glusterd: resolve brick failed in restore > > [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] > > 0-management: Initialization of volume 'management' failed, review your > > volfile again > > [2017-08-17 09:04:00.756802] E [MSGI...

...0-04 15:44:20.168321] and > [2017-10-04 15:44:20.185536] > [2017-10-04 15:44:20.188517] I [MSGID: 106544] > [glusterd.c:158:glusterd_uuid_init] 0-management: retrieved UUID: > 29f246da-71b1-4c60-a8c6-e6291f3f8cce > [2017-10-04 15:44:20.189091] E [MSGID: 106187] [glusterd-store.c:4566:glusterd_resolve_all_bricks] > 0-glusterd: resolve brick failed in restore > The fix had been done in a way that while resolving the bricks, we just match them through their peer's UUIDs. If we fail to match through the UUIDs & hostname then we go for local address resolution. In this case it seems like the UUI...

...d 4 times between [2017-10-04 15:44:20.168321] and [2017-10-04 15:44:20.185536] [2017-10-04 15:44:20.188517] I [MSGID: 106544] [glusterd.c:158:glusterd_uuid_init] 0-management: retrieved UUID: 29f246da-71b1-4c60-a8c6-e6291f3f8cce [2017-10-04 15:44:20.189091] E [MSGID: 106187] [glusterd-store.c:4566:glusterd_resolve_all_bricks] 0-glusterd: resolve brick failed in restore The fix had been done in a way that while resolving the bricks, we just match them through their peer's UUIDs. If we fail to match through the UUIDs & hostname then we go for local address resolution. In this case it seems like the UUID matching...

...;> [2017-10-04 15:44:20.185536] >> [2017-10-04 15:44:20.188517] I [MSGID: 106544] >> [glusterd.c:158:glusterd_uuid_init] 0-management: retrieved UUID: >> 29f246da-71b1-4c60-a8c6-e6291f3f8cce >> [2017-10-04 15:44:20.189091] E [MSGID: 106187] >> [glusterd-store.c:4566:glusterd_resolve_all_bricks] 0-glusterd: resolve >> brick failed in restore >> > > The fix had been done in a way that while resolving the bricks, we just > match them through their peer's UUIDs. If we fail to match through the > UUIDs & hostname then we go for local address resolution. In this...

Are you shure about possibility to resolve all node names on all other nodes? You need to use names used previously in Gluster - check their by ?gluster peer status? or ?gluster pool list?. Regards, Bartosz > Wiadomo?? napisana przez Ludwig Gamache <ludwig at elementai.com> w dniu 24.10.2017, o godz. 03:13: > > All, > > I am trying to add a third peer to my gluster

...>> [2017-08-17 09:04:00.711413] I [MSGID: 106194] > >>> [glusterd-store.c:3776:glusterd_store_retrieve_missed_snaps_list] > >>> 0-management: No missed snaps list. > >>> [2017-08-17 09:04:00.756731] E [MSGID: 106187] > >>> [glusterd-store.c:4559:glusterd_resolve_all_bricks] 0-glusterd: resolve > >>> brick failed in restore > >>> [2017-08-17 09:04:00.756787] E [MSGID: 101019] > [xlator.c:503:xlator_init] > >>> 0-management: Initialization of volume 'management' failed, review your > >>> volfile again > >...

All, I am trying to add a third peer to my gluster install. The first 2 nodes are running since many months and have gluster 3.10.3-1. I recently installed the 3rd node and gluster 3.10.6-1. I was able to start the gluster daemon on it. After, I tried to add the peer from one of the 2 previous server (gluster peer probe IPADDRESS). That first peer started the communication with the 3rd peer. At

...sion: 31004 >>>> [2017-08-17 09:04:00.711413] I [MSGID: 106194] [glusterd-store.c:3776: >>>> glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps >>>> list. >>>> [2017-08-17 09:04:00.756731] E [MSGID: 106187] [glusterd-store.c:4559:glusterd_resolve_all_bricks] >>>> 0-glusterd: resolve brick failed in restore >>>> [2017-08-17 09:04:00.756787] E [MSGID: 101019] [xlator.c:503:xlator_init] >>>> 0-management: Initialization of volume 'management' failed, review your >>>> volfile again >>>> [...