search for: 101066

Displaying 20 results from an estimated 26 matches for "101066".

Did you mean: 10106
2018 May 15
2
glusterfs 3.13 repo unavailable and downgrade to 3.12.9 fails
...to 3.12 breaks the server node i believe the issue is with: *[2018-05-15 08:54:39.981101] E [MSGID: 101019] [xlator.c:503:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again [2018-05-15 08:54:39.981113] E [MSGID: 101066] [graph.c:327:glusterfs_graph_init] 0-management: initializing translator failed [2018-05-15 08:54:39.981121] E [MSGID: 101176] [graph.c:698:glusterfs_graph_activate] 0-graph: init failed * Any help appreciated, thanks Details: *Installed Packages* glusterfs.x86_64 3.12.9-1.el7 @gluster-3.12 glus...
2018 May 15
0
glusterfs 3.13 repo unavailable and downgrade to 3.12.9 fails
...e server node i believe the issue is with: > *[2018-05-15 08:54:39.981101] E [MSGID: 101019] > [xlator.c:503:xlator_init] 0-management: Initialization of volume > 'management' failed, review your volfile again????????????????????????????? > [2018-05-15 08:54:39.981113] E [MSGID: 101066] > [graph.c:327:glusterfs_graph_init] 0-management: initializing translator > failed?????????????????????????????????????????????????????????????? > [2018-05-15 08:54:39.981121] E [MSGID: 101176] > [graph.c:698:glusterfs_graph_activate] 0-graph: init > failed?????????????????????????...
2018 May 15
1
[External] Re: glusterfs 3.13 repo unavailable and downgrade to 3.12.9 fails
...s the server node i believe the issue is with: > > *[2018-05-15 08:54:39.981101] E [MSGID: 101019] > > [xlator.c:503:xlator_init] 0-management: Initialization of volume > > 'management' failed, review your volfile again > > > [2018-05-15 08:54:39.981113] E [MSGID: 101066] > > [graph.c:327:glusterfs_graph_init] 0-management: initializing translator > > failed > > [2018-05-15 08:54:39.981121] E [MSGID: 101176] > > [graph.c:698:glusterfs_graph_activate] 0-graph: init > > failed > > > * > > > > Any help appreciated, th...
2018 May 15
1
[External] Re: glusterfs 3.13 repo unavailable and downgrade to 3.12.9 fails
...with: > > *[2018-05-15 08:54:39.981101] E [MSGID: 101019] > > [xlator.c:503:xlator_init] 0-management: Initialization of volume > > 'management' failed, review your volfile again????????????????????????????? > > [2018-05-15 08:54:39.981113] E [MSGID: 101066] > > [graph.c:327:glusterfs_graph_init] 0-management: initializing translator > > failed?????????????????????????????????????????????????????????????? > > [2018-05-15 08:54:39.981121] E [MSGID: 101176] > > [graph.c:698:glusterfs_graph_activate] 0-graph: init...
2017 Aug 17
3
Glusterd not working with systemd in redhat 7
...usterd-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-management: initializing translator failed [2017-08-17 09:04:00.756816] E [MSGID: 101176] [graph.c:681:glusterfs_graph_activate] 0-graph: init failed [2017-08-17 09:04:00.766584] W [glusterfsd.c:1332:cleanup_and_exit] (-->/usr/sbin/glusterd(glusterfs_volumes...
2017 Aug 18
0
Glusterd not working with systemd in redhat 7
...erd_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-management: initializing translator > failed > [2017-08-17 09:04:00.756816] E [MSGID: 101176] > [graph.c:681:glusterfs_graph_activate] 0-graph: init failed > [2017-08-17 09:04:00.766584] W [glusterfsd.c:1332:cleanup_and_exit] > (-->/usr/s...
2017 Aug 18
2
Glusterd not working with systemd in redhat 7
...ks] 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-management: initializing translator >> failed >> [2017-08-17 09:04:00.756816] E [MSGID: 101176] >> [graph.c:681:glusterfs_graph_activate] 0-graph: init failed >> [2017-08-17 09:04:00.766584] W [glusterfsd.c:1332:cleanup_and_exit...
2017 Aug 18
1
Glusterd not working with systemd in redhat 7
...gt; > 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-management: initializing translator > > failed > > [2017-08-17 09:04:00.756816] E [MSGID: 101176] > > [graph.c:681:glusterfs_graph_activate] 0-graph: init failed > > [2017-08-17 09:04:00.766584] W [glusterfsd.c:1332:cleanup_and...
2017 Aug 18
0
Glusterd not working with systemd in redhat 7
...lve >>> 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-management: initializing translator >>> failed >>> [2017-08-17 09:04:00.756816] E [MSGID: 101176] >>> [graph.c:681:glusterfs_graph_activate] 0-graph: init failed >>> [2017-08-17 09:04:00.766584] W [glusterfsd.c:1...
2017 Sep 17
2
Glusterd not working with systemd in redhat 7
...gt;> > > [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-management: initializing >> translator >> > > failed >> > > [2017-08-17 09:04:00.756816] E [MSGID: 101176] >> > > [graph.c:681:glusterfs_graph_activate] 0-graph: init failed >> > > [2017-0...
2017 Oct 04
0
Glusterd not working with systemd in redhat 7
...d 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-management: initializing translator > > > > failed > > > > [2017-08-17 09:04:00.756816] E [MSGID: 101176] > > > > [graph.c:681:glusterfs_graph_activate] 0-graph: init failed > > > > [2017-08-17...
2017 Oct 04
2
Glusterd not working with systemd in redhat 7
...usterd-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-management: initializing translator failed [2017-10-04 15:44:20.189153] E [MSGID: 101176] [graph.c:681:glusterfs_graph_activate] 0-graph: init failed [2017-10-04 15:44:20.190877] W [glusterfsd.c:1360:cleanup_and_exit] (-->/usr/sbin/glusterd(glusterfs_volumes...
2017 Oct 04
2
Glusterd not working with systemd in redhat 7
...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-management: initializing translator > > > failed > > > [2017-08-17 09:04:00.756816] E [MSGID: 101176] > > > [graph.c:681:glusterfs_graph_activate] 0-graph: init failed > > > [2017-08-17 09:04:00.766584] W [glus...
2017 Oct 04
0
Glusterd not working with systemd in redhat 7
...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-management: initializing translator > > > failed > > > [2017-08-17 09:04:00.756816] E [MSGID: 101176] > > > [graph.c:681:glusterfs_graph_activate] 0-graph: init failed > > > [2017-08-17 09:04:00.766584] W [glus...
2017 Oct 04
2
Glusterd not working with systemd in redhat 7
...gt; > 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-management: initializing translator > > failed > > [2017-08-17 09:04:00.756816] E [MSGID: 101176] > > [graph.c:681:glusterfs_graph_activate] 0-graph: init failed > > [2017-08-17 09:04:00.766584] W [glusterfsd.c:1332:cleanup_and...
2017 Oct 05
0
Glusterd not working with systemd in redhat 7
...lname>/bricks/* Please also provide the gluster volume info output. > [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-management: initializing translator > failed > [2017-10-04 15:44:20.189153] E [MSGID: 101176] > [graph.c:681:glusterfs_graph_activate] 0-graph: init failed > [2017-10-04 15:44:20.190877] W [glusterfsd.c:1360:cleanup_and_exit] > (-->/usr/s...
2017 Oct 05
2
Glusterd not working with systemd in redhat 7
...glusterd/vols/<volname>/bricks/* Please also provide the gluster volume info output. [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-management: initializing translator failed [2017-10-04 15:44:20.189153] E [MSGID: 101176] [graph.c:681:glusterfs_graph_activate] 0-graph: init failed [2017-10-04 15:44:20.190877] W [glusterfsd.c:1360:cleanup_and_exit] (-->/usr/sbin/glusterd(glusterfs_volumes...
2017 Oct 05
0
Glusterd not working with systemd in redhat 7
...Please also provide the gluster volume info output. > >> [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-management: initializing translator >> failed >> [2017-10-04 15:44:20.189153] E [MSGID: 101176] >> [graph.c:681:glusterfs_graph_activate] 0-graph: init failed >> [2017-10-04 15:44:20.190877] W [glusterfsd.c:1360:cleanup_and_exit...
2017 Oct 24
0
trying to add a 3rd peer
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 Aug 18
2
Glusterd not working with systemd in redhat 7
...iled 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-management: initializing > translator > >>> failed > >>> [2017-08-17 09:04:00.756816] E [MSGID: 101176] > >>> [graph.c:681:glusterfs_graph_activate] 0-graph: init failed > >>> [2017-08-17 09:0...