Hi,
Actually you were right. one of the ip-adresses were wrong in r0.res file I
have corrected this, but still I can't promote any of the nodes to primary.
output from drbdadm dump
[root@tdprodrepo01 ~]# drbdadm dump
# /etc/drbd.conf
common {
disk {
on-io-error dettach;
and corosync-objctl | grep member gives:
[root@tdprodrepo01 /]# corosync-objctl | grep member
totem.interface.member.memberaddr=10.240.195.10
totem.interface.member.memberaddr=10.240.195.11
totem.interface.member.memberaddr=10.240.196.10
totem.interface.member.memberaddr=10.240.196.11
runtime.tote
at least corosync-cfgtool -s gives no errors
[root@tdprodrepo02 log]# corosync-cfgtool -s
Printing ring status.
Local node ID 197390346
RING ID 0
id = 10.240.195.11
status = ring 0 active with no faults
RING ID 1
id = 10.240.196.11
status = ring 1 active
Am 15.08.2013 13:25, schrieb Fredrik Hudner:
So if you have any other suggestions how I can come out of this situation,
it would be much appreciated
Are you sure the machines see each other? "diskless" for the remote side
sounds not too convinving...
JC
___
I still can't promote any of the nodes to primary, the output of cat
/proc/drbd on both machines are
[root@tdprodrepo02 ~]# cat /proc/drbd
version: 8.4.1 (api:1/proto:86-100)
GIT-hash: 91b4c048c1a0e06777b5f65d312b38d47abaea80 build by gardner@,
2012-08-25 00:57:01
0: cs:Connected ro:Secondary/Sec
Am 14.08.2013 22:12, schrieb Fredrik Hudner:
Hi,
I have a problem I don't know how to resolve.
One of my clusters which reside in a VCentre where moved away to another
blade as two blades in the Vcentre went down.
After that I got some problems with my cluster and I guess I messed it up a
bit a
thanks mate,
I will definitetly try this tomorrow morning. Sometimes it's a bit hard to
navigate around in the documentation for a very specific problem.
Will see if I can get my boss to sponsor a LinBiT training when he's back
from partenaty leave..
Guess the only English spoken are in the USA ?
On 08/14/2013 02:12 PM, Fredrik Hudner wrote:
>
> I have tried to make one node primary but only get:
>
> 0: State change failed: (-2) Need access to UpToDate data
> Command 'drbdsetup primary 0' terminated with exit code 17
When you've suffered a sudden disconnect, you can get into a situation
wh
Hi,
I have a problem I don't know how to resolve.
One of my clusters which reside in a VCentre where moved away to another
blade as two blades in the Vcentre went down.
After that I got some problems with my cluster and I guess I messed it up a
bit as the state of drbd now shows secondary/seconda
