Displaying 8 results from an estimated 8 matches for "glusterd_store_retrieve_volum".
Did you mean:
glusterd_store_retrieve_volume
2011 Dec 14
1
glusterfs crash when the one of replicate node restart
...0.483828] E [rpc-transport.c:742:rpc_transport_load]
0-rpc-transport: 'rdma' initialization failed
[2011-12-14 13:24:10.483841] W [rpcsvc.c:1288:rpcsvc_transport_create]
0-rpc-service: cannot create listener, initing the transport failed
[2011-12-14 13:24:11.967621] E
[glusterd-store.c:1820:glusterd_store_retrieve_volume] 0-: Unknown key:
brick-0
[2011-12-14 13:24:11.967665] E
[glusterd-store.c:1820:glusterd_store_retrieve_volume] 0-: Unknown key:
brick-1
[2011-12-14 13:24:11.967681] E
[glusterd-store.c:1820:glusterd_store_retrieve_volume] 0-: Unknown key:
brick-2
[2011-12-14 13:24:11.967695] E
[glusterd-store.c:1...
2014 Mar 04
1
glusterd service fails to start from AWS AMI
...21:20:30.543471] W [rpcsvc.c:1387:rpcsvc_transport_create] 0-rpc-service: cannot create listener, initing the transport failed
[2014-03-04 21:20:37.116571] I [glusterd-store.c:1388:glusterd_restore_op_version] 0-glusterd: retrieved op-version: 2
[2014-03-04 21:20:37.120082] E [glusterd-store.c:1905:glusterd_store_retrieve_volume] 0-: Unknown key: brick-0
[2014-03-04 21:20:37.120118] E [glusterd-store.c:1905:glusterd_store_retrieve_volume] 0-: Unknown key: brick-1
[2014-03-04 21:20:37.120137] E [glusterd-store.c:1905:glusterd_store_retrieve_volume] 0-: Unknown key: brick-2
[2014-03-04 21:20:37.120154] E [glusterd-store.c:1...
2017 May 09
1
Empty info file preventing glusterd from starting
...rd-store.c:2047:glusterd_restore_op_version] 0-glusterd: retrieved
op-version: 30706
[2017-05-06 03:33:39.827515] E [MSGID: 106206]
[glusterd-store.c:2562:glusterd_store_update_volinfo] 0-management: Failed
to get next store iter
[2017-05-06 03:33:39.827563] E [MSGID: 106207]
[glusterd-store.c:2844:glusterd_store_retrieve_volume] 0-management: Failed
to update volinfo for c_glusterfs volume
[2017-05-06 03:33:39.827625] E [MSGID: 106201]
[glusterd-store.c:3042:glusterd_store_retrieve_volumes] 0-management:
Unable to restore volume: c_glusterfs
[2017-05-06 03:33:39.827722] E [MSGID: 101019] [xlator.c:428:xlator_init]
0-mana...
2011 Jul 08
1
Possible to bind to multiple addresses?
...s:
[2011-07-08 08:44:03.778665] I [glusterd.c:564:init] 0-management: Using
/etc/glusterd as working directory
[2011-07-08 08:44:03.779276] I [glusterd.c:88:glusterd_uuid_init]
0-glusterd: retrieved UUID: 6bf087ca-e5a2-4dcc-964c-7f17d21bb17f
[2011-07-08 08:44:03.780841] E
[glusterd-store.c:1567:glusterd_store_retrieve_volume] 0-: Unknown key:
brick-0
[2011-07-08 08:44:03.780861] E
[glusterd-store.c:1567:glusterd_store_retrieve_volume] 0-: Unknown key:
brick-1
[2011-07-08 08:44:03.917480] I
[glusterd-handler.c:3399:glusterd_friend_add] 0-glusterd: connect returned 0
[2011-07-08 08:44:03.917709] I
[glusterd-utils.c...
2017 Jun 01
2
[Gluster-devel] Empty info file preventing glusterd from starting
...t; [glusterd-store.c:2562:glusterd_store_update_volinfo]
> > >>>>>>>> 0-management: Failed to get next store iter
> > >>>>>>>> [2017-05-06 03:33:39.827563] E [MSGID: 106207]
> > >>>>>>>> [glusterd-store.c:2844:glusterd_store_retrieve_volume]
> > >>>>>>>> 0-management: Failed to update volinfo for c_glusterfs volume
> > >>>>>>>> [2017-05-06 03:33:39.827625] E [MSGID: 106201]
> > >>>>>>>> [glusterd-store.c:3042:glusterd_store_retrieve_volumes]
>...
2017 Jun 01
0
[Gluster-devel] Empty info file preventing glusterd from starting
...ore.c:2562:glusterd_store_update_volinfo]
> > > >>>>>>>> 0-management: Failed to get next store iter
> > > >>>>>>>> [2017-05-06 03:33:39.827563] E [MSGID: 106207]
> > > >>>>>>>> [glusterd-store.c:2844:glusterd_store_retrieve_volume]
> > > >>>>>>>> 0-management: Failed to update volinfo for c_glusterfs volume
> > > >>>>>>>> [2017-05-06 03:33:39.827625] E [MSGID: 106201]
> > > >>>>>>>> [glusterd-store.c:3042:glusterd_store_retrie...
2013 Oct 07
1
glusterd service fails to start on one peer
...for some reason glusterd sill not start on one
of them. All are running glusterfs version 3.4.0-8.el6 on Centos 6.4
(2.6.32-358.el6.x86_64).
In /var/log/glusterfs/etc-glusterfs-glusterd.vol.log I see this error
repeated 36 times (alternating between brick-0 and brick-1):
*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
> br...
2011 Jul 11
0
Instability when using RDMA transport
...=====
[2011-07-11 10:16:48.352084] I [glusterd.c:564:init] 0-management: Using /etc/glusterd as working directory
[2011-07-11 10:16:48.694351] I [glusterd.c:88:glusterd_uuid_init] 0-glusterd: retrieved UUID: d3f2a368-9640-40b8-a949-d4a61ac861c1
[2011-07-11 10:16:48.700503] E [glusterd-store.c:1567:glusterd_store_retrieve_volume] 0-: Unknown key: brick-0
[2011-07-11 10:16:48.700533] E [glusterd-store.c:1567:glusterd_store_retrieve_volume] 0-: Unknown key: brick-1
[2011-07-11 10:16:48.700548] E [glusterd-store.c:1567:glusterd_store_retrieve_volume] 0-: Unknown key: brick-2
[2011-07-11 10:16:48.873912] I [glusterd-handler.c...