Displaying 18 results from an estimated 18 matches for "106116".
Did you mean:
106,16
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...7-19 15:07:43.130244] E [MSGID: 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...
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...terd-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:
>...
2017 Jul 20
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...-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_...
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...] E [MSGID: 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-...
2017 Jul 20
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...gt; [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
>>...
2017 Jul 26
2
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...usterd_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:...
2017 Jul 26
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...;> 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...
2017 Jul 27
0
glusterd-locks.c:572:glusterd_mgmt_v3_lock
...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...
2017 Dec 15
3
Production Volume will not start
...erd_submit_reply] 0-glusterd: 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.96265...
2017 Dec 18
0
Production Volume will not start
...ate peerinfo entry of
nsgtpcfs02.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 Jun 27
2
Gluster failure due to "0-management: Lock not released for <volumename>"
...:52:02.716782. timeout = 600 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. timeo...
2017 Jun 29
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...:52:02.716782. timeout = 600 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. timeo...
2017 Jun 30
3
Gluster failure due to "0-management: Lock not released for <volumename>"
...ut = 600 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-...
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...:52:02.716782. timeout = 600 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. timeo...
2017 Jul 05
1
Gluster failure due to "0-management: Lock not released for <volumename>"
...ut = 600 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-...
2017 Jul 04
0
Gluster failure due to "0-management: Lock not released for <volumename>"
...:52:02.716782. timeout = 600 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. timeo...
2017 Jun 22
0
Gluster failure due to "0-management: Lock not released for <volumename>"
Could you attach glusterd.log and cmd_history.log files from all the nodes?
On Wed, Jun 21, 2017 at 11:40 PM, Victor Nomura <victor at mezine.com> wrote:
> Hi All,
>
>
>
> I?m fairly new to Gluster (3.10.3) and got it going for a couple of months
> now but suddenly after a power failure in our building it all came crashing
> down. No client is able to connect after
2017 Jun 21
2
Gluster failure due to "0-management: Lock not released for <volumename>"
Hi All,
I'm fairly new to Gluster (3.10.3) and got it going for a couple of months
now but suddenly after a power failure in our building it all came crashing
down. No client is able to connect after powering back the 3 nodes I have
setup.
Looking at the logs, it looks like there's some sort of "Lock" placed on the
volume which prevents all the clients from connecting to