Hi,
Thanks a lot for your answer, I tried the following:
configvm1 IPaddr::192.168.1.100 drbddisk::disk0
Filesystem::/dev/drbd0::/replicated::ext3
but still have the same problem, no VIP attached to configvm1 eth0.
I finally decided to reinstall the whole thing (as I had already lost too
much time on that issue) and to move to corosync/pacemaker which I tried a
few months ago successfully.
With that configuration (dnsvm1 : 192.168.1.101 / dnsvm2 : 192.168.1.102 and
a VIP 192.168.1.100)
I succeeded in having a cluster working, my floating IP is changing from one
node to the other without problem and also the resource I declared (for the
moment dhcp3 and apache2).
I follow this how to (https://wiki.ubuntu.com/ClusterStack/LucidTesting) to
make pacemaker works with drbd but now new problems appear:
When my both nodes are active, everything seems to be working. see output of
crm_mon:
============
Last updated: Wed Jul 21 09:20:06 2010
Stack: openais
Current DC: dnsvm1 - partition with quorum
Version: 1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd
2 Nodes configured, 2 expected votes
3 Resources configured.
============
Online: [ dnsvm1 dnsvm2 ]
fs_drbd (ocf::heartbeat:Filesystem): Started dnsvm2
Resource Group: group1
dnsclusterip (ocf::heartbeat:IPaddr2): Started dnsvm1
apache2 (ocf::heartbeat:apache): Started dnsvm1
dhcp3-server (lsb:dhcp3-server): Started dnsvm1
Master/Slave Set: ms_drbd
Masters: [ dnsvm2 ]
Slaves: [ dnsvm1 ]
but if I put node dnsvm2 in standby or shut it down, the filesystem is not
transfeering to dnsvm1 as displayed here:
============
Last updated: Wed Jul 21 09:11:53 2010
Stack: openais
Current DC: dnsvm1 - partition with quorum
Version: 1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd
2 Nodes configured, 2 expected votes
3 Resources configured.
============
Node dnsvm2: standby
Online: [ dnsvm1 ]
Resource Group: group1
dnsclusterip (ocf::heartbeat:IPaddr2): Started dnsvm1
apache2 (ocf::heartbeat:apache): Started dnsvm1
dhcp3-server (lsb:dhcp3-server): Started dnsvm1
Master/Slave Set: ms_drbd
Masters: [ dnsvm1 ]
Stopped: [ drbd_disk:1 ]
Moreover the resource which seems to be attached to dnsvm2 when working is
drbd_disk:0. It is changing to drbd_disk:1 when switching to node 1.
Drbd seems ok anyway ; here is drbdadm status reply:
<resource minor="0" name="disk0" cs="Connected" ro1="Secondary"
ro2="Primary" ds1="UpToDate" ds2="UpToDate" />
Is there sometehing in my conf which can explained that or am I missing
anything else ?
crm configure show:
node dnsvm1
node dnsvm2
primitive apache2 ocf:heartbeat:apache \
params configfile="/etc/apache2/apache2.conf"
httpd="/usr/sbin/apache2" \
op monitor interval="5s"
primitive dhcp3-server lsb:dhcp3-server \
op monitor interval="5s"
primitive dnsclusterip ocf:heartbeat:IPaddr2 \
params ip="192.168.1.100" nic="eth0"
primitive drbd_disk ocf:linbit:drbd \
params drbd_resource="disk0" \
op monitor interval="15s"
primitive fs_drbd ocf:heartbeat:Filesystem \
params device="/dev/drbd/by-res/disk0" directory="/replicated"
fstype="ext3"
group group1 dnsclusterip apache2 dhcp3-server
ms ms_drbd drbd_disk \
meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true"
location loc-1 fs_drbd -inf: dnsvm1
location loc-2 drbd_disk -inf: dnsvm1
colocation mnt_on_master inf: fs_drbd ms_drbd:Master
order apache_after_ip inf: dnsclusterip:start apache2:start
order mount_after_drbd inf: ms_drbd:promote fs_drbd:start
property $id="cib-bootstrap-options" \
dc-version="1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
stonith-enabled="false" \
no-quorum-policy="ignore"
I got this warning when verirying the conf but I can't understand it even
with a lot of time reading the pacemaker web site.
crm_verify[18082]: 2010/07/21_09:30:06 WARN: unpack_rsc_location: No
resource (con=loc-2, rsc=drbd_disk)
Warnings found during check: config may not be valid
WARNING: fs_drbd: default timeout 20s for start is smaller than the advised
60
WARNING: fs_drbd: default timeout 20s for stop is smaller than the advised
60
WARNING: apache2: default timeout 20s for start is smaller than the advised
40s
WARNING: apache2: default timeout 20s for stop is smaller than the advised
60s
WARNING: drbd_disk: default timeout 20s for start is smaller than the
advised 240
WARNING: drbd_disk: default timeout 20s for stop is smaller than the advised
100
Why is it syaing No resource as there is a primitive directive to declare
drbd_disk (and it seems to work when both nodes are active).
Can this be the source of error I get ?
What does unpack_rsc_location mean ?
Finally here is my drbd conf if it can help
/etc/drbd.d/disk0.res
resource disk0 {
protocol C;
net {
cram-hmac-alg sha1;
shared-secret "lucid";
}
syncer { # Vitesse de synchro
rate 640M; # le max
al-extents 257;
}
on dnsvm1 {
device /dev/drbd0;
disk /dev/sda3;
address 192.168.1.101:7788;
meta-disk internal;
}
on dnsvm2 {
device /dev/drbd0;
disk /dev/sda3;
address 192.168.1.102:7788;
meta-disk internal;
}
}
Many thanx in advance ....
Snarf
----- Original Message -----
From: "jayesh shinde" <[email protected]>
To: "General Linux-HA mailing list" <[email protected]>
Sent: Tuesday, July 20, 2010 4:07 PM
Subject: Re: [Linux-HA] heartbeat IPaddr problem
Hi ,
Try like this below in haresources file.
configvm1 IPaddr::192.168.1.100 drbddisk::r0
Filesystem::/dev/drbd0::/usr/local::xfs
where
"configvm1" your primary host name
"192.168.1.100" is the floating IP.
"r0" is resource in /etc/drbd.conf ( check out what u have mention in ur
file)
"/dev/drbd0" is device /etc/drbd.conf
"/usr/local" is the lable over which /dev/drbd0 is suppose to mount ( change
it as per your need )
"xfs" is the file system ( change it as per your need)
Do the same config on both server and then restart the heartbeat service.
you will get aliase ip to your eth0 interface on primary server.
Regards
Jayesh Shinde
--- On Tue, 7/20/10, Francois LE FOLL <[email protected]> wrote:
From: Francois LE FOLL <[email protected]>
Subject: [Linux-HA] heartbeat IPaddr problem
To: [email protected]
Date: Tuesday, July 20, 2010, 4:17 PM
Hello everybody,
this is my first post to this list, and I really need your help.
It's two days since I'm looking over different forum for an answer but I
can't succeed in and google seems not to be my friend on that issue.
Here is my problem description.
I'm running two virtual machine (kvm) hosting ubuntu server 10.04 and I want
them to be configured as a cluster (drbd + heartbeat). First machine is
named configvm1 (192.168.1.101) and the second one is configvm2
(192.168.1.102)
drbd seems to work based on the logs but I'm not an expert at all and I
can't succeed in looking at the shared directory in the secondary node
(which seem to normal in a primary/.Secondary configuration).
Anyway I will have this answered as soon as I will be able to make heartbeat
working and manage drbd daemon.
Currently I'm stuck at the beginning because I can't attach a virtual IP
address on my NIC at the start of hearbeat.
Anyway if I launch the command manually (here after) there is no problem and
I can ping it from both nodes.
"sudo sh /etc/heartbeat/resource.d/IPaddr2 192.168.1.100 start"
but if I simply start heartbeat, I always receive:
Starting High-Availability services: IPaddr2[6687]: INFO: Resource is
stopped
Done.
here are my conf files:
haresources file:
configvm1 IPaddr2::192.168.1.100 drbddisk::disk0 dhcp3-server
ha.cf file:
debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility local0
autojoin none
auto_failback on
bcast eth0
warntime 5
keepalive 1 #ping each other every second (60 heartbeats / minute)
deadtime 10 #declaring a node dead after this timedelay without any
heartbeat
initdead 10
node configvm1
node configvm2
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
