Displaying 3 results from an estimated 3 matches for "1yzfdwgkfdahivbsj7pcoe".
2020 May 06
2
Nodes in CTDB Cluster don't release recovery lock
...ith flock, and I've confirmed the lock is being held with
`lslock`.
Here is the debug information from the "healthy node" (the unhealthy one
just says it can't take the lock as it is under contention, so I thought it
would be of little use):
https://drive.google.com/drive/folders/1yzFdwGKfDAHiVbsj7pcOe-jX4KHpFO2U?usp=sharing
Best regards and thank you all for your time,
Christian
--
<https://opendrives.com/wp-content/uploads/2020/04/OD-Anywhere.pdf>
2020 May 07
0
Nodes in CTDB Cluster don't release recovery lock
...med the lock is being held with
> `lslock`.
>
> Here is the debug information from the "healthy node" (the unhealthy one
> just says it can't take the lock as it is under contention, so I thought it
> would be of little use):
> https://drive.google.com/drive/folders/1yzFdwGKfDAHiVbsj7pcOe-jX4KHpFO2U?usp=sharing
Your main problem seems to be that the nodes are not connecting to each
other:
$ ls ctdb*.log
ctdb-full.log ctdb-locked-out-node.log ctdb.log
$ grep "connected to" ctdb*.log
$
You should see lines something similar to this:
2020/05/07 16:58:06.186548...
2020 May 07
1
Nodes in CTDB Cluster don't release recovery lock
...t; `lslock`.
> >
> > Here is the debug information from the "healthy node" (the unhealthy one
> > just says it can't take the lock as it is under contention, so I thought
> it
> > would be of little use):
> >
> https://drive.google.com/drive/folders/1yzFdwGKfDAHiVbsj7pcOe-jX4KHpFO2U?usp=sharing
>
> Your main problem seems to be that the nodes are not connecting to each
> other:
>
> $ ls ctdb*.log
> ctdb-full.log ctdb-locked-out-node.log ctdb.log
> $ grep "connected to" ctdb*.log
> $
>
> You should see lines something...