search for: gd_mgmt_v3_collate_errors

Displaying 20 results from an estimated 22 matches for "gd_mgmt_v3_collate_errors".

glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...D: 106119] [glusterd-op-sm.c:3782:glusterd_op_ac_lock] 0-management: Unable to acquire lock for vm-images-repo [2017-07-19 15:07:43.130320] E [MSGID: 106376] [glusterd-op-sm.c:7775:glusterd_op_sm] 0-management: handler returned: -1 [2017-07-19 15:07:43.130665] E [MSGID: 106116] [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking failed on virtnode-0-1-gluster. Please check log file for details. [2017-07-19 15:07:43.131293] E [MSGID: 106116] [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking failed on virtnode-0-2-gluster. Please check log file for details. [2017-07-19 15:07:43.1313...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...0-management: Unable > to acquire lock for vm-images-repo > [2017-07-19 15:07:43.130320] E [MSGID: 106376] > [glusterd-op-sm.c:7775:glusterd_op_sm] 0-management: handler > returned: -1 > [2017-07-19 15:07:43.130665] E [MSGID: 106116] > [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: > Locking failed on virtnode-0-1-gluster. Please check log file for > details. > [2017-07-19 15:07:43.131293] E [MSGID: 106116] > [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: > Locking failed on virtnode-0-2-gluster. Please check lo...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...e lock for vm-images-repo >> [2017-07-19 15:07:43.130320] E [MSGID: 106376] >> [glusterd-op-sm.c:7775:glusterd_op_sm] 0-management: handler >> returned: -1 >> [2017-07-19 15:07:43.130665] E [MSGID: 106116] >> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: >> Locking failed on virtnode-0-1-gluster. Please check log file >> for details. >> [2017-07-19 15:07:43.131293] E [MSGID: 106116] >> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: >> Locking failed...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...m.c:3782:glusterd_op_ac_lock] > 0-management: Unable to acquire lock for vm-images-repo > [2017-07-19 15:07:43.130320] E [MSGID: 106376] [glusterd-op-sm.c:7775:glusterd_op_sm] > 0-management: handler returned: -1 > [2017-07-19 15:07:43.130665] E [MSGID: 106116] > [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking > failed on virtnode-0-1-gluster. Please check log file for details. > [2017-07-19 15:07:43.131293] E [MSGID: 106116] > [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking > failed on virtnode-0-2-gluster. Please check log file for details. >...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
..._ac_lock] 0-management: Unable to >> acquire lock for vm-images-repo >> [2017-07-19 15:07:43.130320] E [MSGID: 106376] >> [glusterd-op-sm.c:7775:glusterd_op_sm] 0-management: handler returned: -1 >> [2017-07-19 15:07:43.130665] E [MSGID: 106116] >> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking >> failed on virtnode-0-1-gluster. Please check log file for details. >> [2017-07-19 15:07:43.131293] E [MSGID: 106116] >> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking >> failed on virtnode-0-2-gluster. Please check log file fo...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 26
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...>>> acquire lock for vm-images-repo >>> [2017-07-19 15:07:43.130320] E [MSGID: 106376] >>> [glusterd-op-sm.c:7775:glusterd_op_sm] 0-management: handler returned: >>> -1 >>> [2017-07-19 15:07:43.130665] E [MSGID: 106116] >>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking >>> failed on virtnode-0-1-gluster. Please check log file for details. >>> [2017-07-19 15:07:43.131293] E [MSGID: 106116] >>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] 0-management: Locking >>> failed on virtnode-0-2-gluster. Please c...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 26
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...-repo >>> [2017-07-19 15:07:43.130320] E [MSGID: 106376] >>> [glusterd-op-sm.c:7775:glusterd_op_sm] 0-management: handler >>> returned: -1 >>> [2017-07-19 15:07:43.130665] E [MSGID: 106116] >>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] >>> 0-management: Locking failed on virtnode-0-1-gluster. Please >>> check log file for details. >>> [2017-07-19 15:07:43.131293] E [MSGID: 106116] >>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] >>> 0-managem...
orphaned snapshots
2023 Aug 09
1
orphaned snapshots
...tage of one node, after bringing it up again, the node has some orphaned snapshosts, which are already deleted on the other nodes. How can I delete these orphaned snapshots? Trying the normal way produceses these errors: |[2023-08-08 19:34:03.667109 +0000] E [MSGID: 106115] [glusterd-mgmt.c:118:gd_mgmt_v3_collate_errors] 0-management: Pre Validation failed on B742. Please check log file for details.| |[2023-08-08 19:34:03.667184 +0000] E [MSGID: 106115] [glusterd-mgmt.c:118:gd_mgmt_v3_collate_errors] 0-management: Pre Validation failed on B741. Please check log file for details.| |[2023-08-08 19:34:03.667210 +0...
glusterd-locks.c:572:glusterd_mgmt_v3_lock
2017 Jul 27
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...-07-19 15:07:43.130320] E [MSGID: 106376] >>>> [glusterd-op-sm.c:7775:glusterd_op_sm] 0-management: >>>> handler returned: -1 >>>> [2017-07-19 15:07:43.130665] E [MSGID: 106116] >>>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors] >>>> 0-management: Locking failed on virtnode-0-1-gluster. >>>> Please check log file for details. >>>> [2017-07-19 15:07:43.131293] E [MSGID: 106116] >>>> [glusterd-mgmt.c:135:gd_mgmt_v3_collate_errors...
orphaned snapshots
2023 Aug 10
2
orphaned snapshots
...tage of one node, after bringing it up again, the node has some orphaned snapshosts, which are already deleted on the other nodes. How can I delete these orphaned snapshots? Trying the normal way produceses these errors: [2023-08-08 19:34:03.667109 +0000] E [MSGID: 106115] [glusterd-mgmt.c:118:gd_mgmt_v3_collate_errors] 0-management: Pre Validation failed on B742. Please check log file for details. [2023-08-08 19:34:03.667184 +0000] E [MSGID: 106115] [glusterd-mgmt.c:118:gd_mgmt_v3_collate_errors] 0-management: Pre Validation failed on B741. Please check log file for details. [2023-08-08 19:34:03.667210 +0000]...
Production Volume will not start
2017 Dec 15
3
Production Volume will not start
...Reply submission failed [2017-12-15 18:56:17.962251] E [rpc-clnt.c:185:call_bail] 0-management: bailing out frame type(glusterd mgmt v3) op(--(4)) xid = 0x14 sent = 2017-12-15 18:46:09.005976. timeout = 600 for 10.17.100.208:24007 [2017-12-15 18:56:17.962324] E [MSGID: 106116] [glusterd-mgmt.c:124:gd_mgmt_v3_collate_errors] 0-management: Commit failed on nsgtpcfs02.corp.nsgdv.com. Please check log file for details. [2017-12-15 18:56:17.962408] E [MSGID: 106123] [glusterd-mgmt.c:1677:glusterd_mgmt_v3_commit] 0-management: Commit failed on peers [2017-12-15 18:56:17.962656] E [MSGID: 106123] [glusterd-mgmt.c:2209:glust...
Production Volume will not start
2017 Dec 18
0
Production Volume will not start
...s02.corp.nsgdv.com in /var/lib/glusterd/peers folder on the node where the CLI failed. Can you please share the output of gluster peer status along with the content of "cat /var/lib/glusterd/peers/* " from all the nodes? [2017-12-15 18:56:17.962324] E [MSGID: 106116] [glusterd-mgmt.c:124:gd_mgmt_v3_collate_errors] > 0-management: Commit failed on nsgtpcfs02.corp.nsgdv.com. Please check > log file for details. > > [2017-12-15 18:56:17.962408] E [MSGID: 106123] [glusterd-mgmt.c:1677:glusterd_mgmt_v3_commit] > 0-management: Commit failed on peers > > [2017-12-15 18:56:17.962656] E [MSGID:...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 27
2
Gluster failure due to "0-management: Lock not released for <volumename>"
...for 192.168.150.52:24007 [2017-06-21 23:02:53.836936] E [rpc-clnt.c:200:call_bail] 0-management: bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = 2017-06-21 22:52:47.909169. timeout = 600 for 192.168.150.53:24007 [2017-06-21 23:02:53.836991] E [MSGID: 106116] [glusterd-mgmt.c:124:gd_mgmt_v3_collate_errors] 0-management: Locking failed on gfsnode3. Please check log file for details. [2017-06-21 23:02:53.837016] E [rpc-clnt.c:200:call_bail] 0-management: bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = 2017-06-21 22:52:47.909175. timeout = 600 for 192.168.150.52:24007 I'd like...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 29
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...for 192.168.150.52:24007 [2017-06-21 23:02:53.836936] E [rpc-clnt.c:200:call_bail] 0-management: bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = 2017-06-21 22:52:47.909169. timeout = 600 for 192.168.150.53:24007 [2017-06-21 23:02:53.836991] E [MSGID: 106116] [glusterd-mgmt.c:124:gd_mgmt_v3_collate_errors] 0-management: Locking failed on gfsnode3. Please check log file for details. [2017-06-21 23:02:53.837016] E [rpc-clnt.c:200:call_bail] 0-management: bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = 2017-06-21 22:52:47.909175. timeout = 600 for 192.168.150.52:24007 I'd like...
Big problems after update to 9.6
2023 Feb 23
1
Big problems after update to 9.6
...2-23 20:26:57.619318 +0000] E [rpc-clnt.c:181:call_bail] 0-management: bailing out frame type(glusterd mgmt v3), op(--(6)), xid = 0x11, unique = 27, sent = 2023-02-23 20:16:50.596447 +0000, timeout = 600 for 10.20.20.11:24007 [2023-02-23 20:26:57.619425 +0000] E [MSGID: 106115] [glusterd-mgmt.c:122:gd_mgmt_v3_collate_errors] 0-management: Unlocking failed on br. Please check log file for details. [2023-02-23 20:26:57.619545 +0000] E [MSGID: 106151] [glusterd-syncop.c:1655:gd_unlock_op_phase] 0-management: Failed to unlock on some peer(s) [2023-02-23 20:26:57.619693 +0000] W [glusterd-locks.c:817:glusterd_mgmt_v3_unloc...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jun 30
3
Gluster failure due to "0-management: Lock not released for <volumename>"
...> [2017-06-21 23:02:53.836936] E [rpc-clnt.c:200:call_bail] 0-management: > bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = > 2017-06-21 22:52:47.909169. timeout = 600 for 192.168.150.53:24007 > [2017-06-21 23:02:53.836991] E [MSGID: 106116] > [glusterd-mgmt.c:124:gd_mgmt_v3_collate_errors] 0-management: Locking > failed on gfsnode3. Please check log file for details. > [2017-06-21 23:02:53.837016] E [rpc-clnt.c:200:call_bail] 0-management: > bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = > 2017-06-21 22:52:47.909175. timeout = 600 for 192.168.150.52:...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...for 192.168.150.52:24007 [2017-06-21 23:02:53.836936] E [rpc-clnt.c:200:call_bail] 0-management: bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = 2017-06-21 22:52:47.909169. timeout = 600 for 192.168.150.53:24007 [2017-06-21 23:02:53.836991] E [MSGID: 106116] [glusterd-mgmt.c:124:gd_mgmt_v3_collate_errors] 0-management: Locking failed on gfsnode3. Please check log file for details. [2017-06-21 23:02:53.837016] E [rpc-clnt.c:200:call_bail] 0-management: bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = 2017-06-21 22:52:47.909175. timeout = 600 for 192.168.150.52:24007 I'd like...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jul 05
1
Gluster failure due to "0-management: Lock not released for <volumename>"
...> [2017-06-21 23:02:53.836936] E [rpc-clnt.c:200:call_bail] 0-management: > bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = > 2017-06-21 22:52:47.909169. timeout = 600 for 192.168.150.53:24007 > [2017-06-21 23:02:53.836991] E [MSGID: 106116] > [glusterd-mgmt.c:124:gd_mgmt_v3_collate_errors] 0-management: Locking > failed on gfsnode3. Please check log file for details. > [2017-06-21 23:02:53.837016] E [rpc-clnt.c:200:call_bail] 0-management: > bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = > 2017-06-21 22:52:47.909175. timeout = 600 for 192.168.150.52:...
Big problems after update to 9.6
2023 Feb 24
1
Big problems after update to 9.6
...6:50.596447 +0000, timeout = 600 for 10.20.20.11:24007<https://urldefense.com/v3/__http://10.20.20.11:24007__;!!I_DbfM1H!H-ob27qPp9fpvcacuvx-Rq_m9Rdc7w0qO3r5pewwZCO30JJzs4eTic2nPJo3JaeCgJanX84-S_Iv80eiwJIScXmwbFpt--19$> [2023-02-23 20:26:57.619425 +0000] E [MSGID: 106115] [glusterd-mgmt.c:122:gd_mgmt_v3_collate_errors] 0-management: Unlocking failed on br. Please check log file for details. [2023-02-23 20:26:57.619545 +0000] E [MSGID: 106151] [glusterd-syncop.c:1655:gd_unlock_op_phase] 0-management: Failed to unlock on some peer(s) [2023-02-23 20:26:57.619693 +0000] W [glusterd-locks.c:817:glusterd_mgmt_v3_unloc...
Gluster failure due to "0-management: Lock not released for <volumename>"
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...for 192.168.150.52:24007 [2017-06-21 23:02:53.836936] E [rpc-clnt.c:200:call_bail] 0-management: bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = 2017-06-21 22:52:47.909169. timeout = 600 for 192.168.150.53:24007 [2017-06-21 23:02:53.836991] E [MSGID: 106116] [glusterd-mgmt.c:124:gd_mgmt_v3_collate_errors] 0-management: Locking failed on gfsnode3. Please check log file for details. [2017-06-21 23:02:53.837016] E [rpc-clnt.c:200:call_bail] 0-management: bailing out frame type(glusterd mgmt v3) op(--(1)) xid = 0x5 sent = 2017-06-21 22:52:47.909175. timeout = 600 for 192.168.150.52:24007 I'd like...