search for: jx4khpfo2u

...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>

...eld 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 node.2 ctd...

...> > 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...