[Vserver] vserver heartbeat?
Hi all! What is a good haresources-script for vserver? Or can I just use /etc/init.d/vservers? (I have a Gentoo-system) Greetings, Evert ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vserver heartbeat?
Hi Evert, I just linked /usr/sbin/vserver to /etc/ha.d/resource.d and put into my haressources file: vserver::mail Works for me (gentoo, too ;) Oliver -- Diese Nachricht wurde digital unterschrieben oliwel's public key: http://www.oliwel.de/oliwel.crt Basiszertifikat: http://www.ldv.ei.tum.de/page72 smime.p7s Description: S/MIME Cryptographic Signature ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer, heartbeat and drbd
On Mon, Jun 28, 2004 at 11:41:24PM -0600, Lucas Albers wrote: [snip problems using drbd with rebootmgr, as it has a file handle open.] Herbert Poetzl said: there is an alternative to the rebootmgr, it's called vshelper, and it should not have this issue ... Is vshelper a stable utility? vshelper is called from the kernel, and as script it isn't part of stable yet (still devel) Is it supported on debian? sure, all scripts should be supported on debian the kernel support only depends on the actual linux-vserver patch ... I can't seem to find any deb packages for it. it is part of util-vserver (at least for the alpha releases, but I think latest pre for stable contain it too, enrico will know ;) HTH, Herbert best, Herbert -- Luke Computer Science System Administrator Security Administrator,College of Engineering Montana State University-Bozeman,Montana ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer, heartbeat and drbd
[snip problems using drbd with rebootmgr, as it has a file handle open.] Is vshelper a stable utility? Is it supported on debian? I can't seem to find any deb packages for it. Herbert Poetzl said: there is an alternative to the rebootmgr, it's called vshelper, and it should not have this issue ... best, Herbert -- Luke Computer Science System Administrator Security Administrator,College of Engineering Montana State University-Bozeman,Montana ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer, heartbeat and drbd
On Friday 28 May 2004 02:04, Lucas Albers wrote:
Hi,
Could you post more details about this?
1.The startup script you have for a vserver which does the arp takeover.
Assume listed in /etc/vservers/servername.sh
#!/bin/sh
case $1 in
pre-start)
/usr/lib/heartbeat/send_arp eth1 ip-addr mac-addr brdcast-addr
# this is for the router (may be redunant):
/usr/lib/heartbeat/send_arp eth1 ip-addr mac-addr router ip-addr
How do you disable rebootmgr if you are using vserver?
Just disabling the startup-script:
update-rc.d -f rebootmgr remove (debian)
Does this break other items?
You cannot reboot the vserver from inside.
If you need this feature, you should propably use the
new reboot userspace helper.
2.) Your Heartbeat script.
harsources:
node1 datadisk::drbd0 vserver::vservername \
MailTo::mail-addr::vservername
3.) Your Sample drbd config.
(I should probably not use protocol B)
resource drbd0 {
protocol=B
fsckcmd=fsck -p -y
disk {
disk-size=1G
}
net {
sync-max=50M
sync-group=0
}
on node1 {
device=/dev/nb0
# btw, don't do this.
# did you notice that in this example we have two drbd devices
# on the same spindle (hda)? performance will be bad. if you
# use several drbd devices, put them on different spindles;
# different channels/controllers won't be a bad idea for IDE.
disk=/dev/linux_vg/vserver_lv
address=ip-addr
port=7789
}
on node2 {
device=/dev/nb0
# and while we are at it,
# if drbd throughput is low, please check your disk
# throughput first. maybe you need to enable DMA? (- man hdparm)
disk=/dev/linux_vg/vserver_lv
address=ip-addr
port=7789
}
}
Any other changes you had to make to vserver to get this to work.
I'll go ask on the drbd list for more drbd specific information.
Thanks.
The heartbeat vserver resource script is just a copy (or symlink) to the
vserver script.
Hope that helps, Thomas
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer, heartbeat and drbd
Gebhardt Thomas said: We are running this type of setup here but don't yet have any experience with real hardware failures but only with test situations. Yes, you are right: heartbeat doesn't need to manage the ip takeover, vserver does. We emit an unsolitcited arp reply in the vserver pre-start script in order to inform all hosts in the local subnet about the takeover. We don't run the rebootmgr because we noticed that its open socket in the vserver filesystem prevented heartbeat from unmounting the vserver filesystem and the takeover hangs. Our heartbeat resources are datadisk, vserver and MailTo, where the vserver resource script is just a symbolic link to the standard vserver script. Off-topic: If you are using drbd, how are you managing the synchro when the master BA comes online again? Don't know what you want to know here. We have heartbeat configured with auto_failback off, so when BA comes up again, the vserver stay on BB until we interactively force the takeover. So we can have a look at BA and eventually start drbd on BA if that doesn't happen automagically. If you want to force a full sync, you have to delete all files in /var/lib/drbd before reconnecting BA. After drbd has synced the disk(s) you can do a /usr/lib/heartbeat/hb_standby foreign on BB to force the failback of the vservers. Cheers, Thomas Could you post more details about this? 1.The startup script you have for a vserver which does the arp takeover. Assume listed in /etc/vservers/servername.sh How do you disable rebootmgr if you are using vserver? Does this break other items? 2.) Your Heartbeat script. 3.) Your Sample drbd config. Any other changes you had to make to vserver to get this to work. I'll go ask on the drbd list for more drbd specific information. Thanks. I'll write this up if I can get more information on this, thanks. -- Luke Computer Science System Administrator Security Administrator,College of Engineering Montana State University-Bozeman,Montana ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer, heartbeat and drbd
On Wednesday 03 March 2004 16:51, loic d'Anterroches wrote: Hi, Do I am wrong or thanks to the vserver approach I don't need to setup an ip takeover? Or formulated another way: heartbeat is only used to start the vserver on BB if BA goes down, drbd taking care of the synchro of the data. We are running this type of setup here but don't yet have any experience with real hardware failures but only with test situations. Yes, you are right: heartbeat doesn't need to manage the ip takeover, vserver does. We emit an unsolitcited arp reply in the vserver pre-start script in order to inform all hosts in the local subnet about the takeover. We don't run the rebootmgr because we noticed that its open socket in the vserver filesystem prevented heartbeat from unmounting the vserver filesystem and the takeover hangs. Our heartbeat resources are datadisk, vserver and MailTo, where the vserver resource script is just a symbolic link to the standard vserver script. Off-topic: If you are using drbd, how are you managing the synchro when the master BA comes online again? Don't know what you want to know here. We have heartbeat configured with auto_failback off, so when BA comes up again, the vserver stay on BB until we interactively force the takeover. So we can have a look at BA and eventually start drbd on BA if that doesn't happen automagically. If you want to force a full sync, you have to delete all files in /var/lib/drbd before reconnecting BA. After drbd has synced the disk(s) you can do a /usr/lib/heartbeat/hb_standby foreign on BB to force the failback of the vservers. Cheers, Thomas ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer, heartbeat and drbd
Hi, Yes, you are right: heartbeat doesn't need to manage the ip takeover, vserver does. We emit an unsolitcited arp reply in the vserver pre-start script in order to inform all hosts in the local subnet about the takeover. We don't run the rebootmgr because we noticed that its open socket in the vserver filesystem prevented heartbeat from unmounting the vserver filesystem and the takeover hangs. Our heartbeat resources are datadisk, vserver and MailTo, where the vserver resource script is just a symbolic link to the standard vserver script. Thanks for this confirmation. It is more clear for me. I will also this rebootmgr issue. Off-topic: If you are using drbd, how are you managing the synchro when the master BA comes online again? Don't know what you want to know here. We have heartbeat configured with auto_failback off, so when BA comes up again, the vserver stay on BB until we interactively force the takeover. So we can have a look at BA and eventually start drbd on BA if that doesn't happen automagically. If you want to force a full sync, you have to delete all files in /var/lib/drbd before reconnecting BA. After drbd has synced the disk(s) you can do a /usr/lib/heartbeat/hb_standby foreign on BB to force the failback of the vservers. Sorry, my question was not correctly formulated, but you gave me the answer anyway :-) I was not sure about the synchro back from BB to BA when BA comes online again, but definitely it looks like doing that manually is better at least to correctly check BA. Thanks for your complete and fast answer, loic ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer, heartbeat and drbd
On Thu, Mar 04, 2004 at 10:57:40AM +0100, loic d'Anterroches wrote: Hi, Yes, you are right: heartbeat doesn't need to manage the ip takeover, vserver does. We emit an unsolitcited arp reply in the vserver pre-start script in order to inform all hosts in the local subnet about the takeover. We don't run the rebootmgr because we noticed that its open socket in the vserver filesystem prevented heartbeat from unmounting the vserver filesystem and the takeover hangs. Our heartbeat resources are datadisk, vserver and MailTo, where the vserver resource script is just a symbolic link to the standard vserver script. Thanks for this confirmation. It is more clear for me. I will also this rebootmgr issue. there is an alternative to the rebootmgr, it's called vshelper, and it should not have this issue ... best, Herbert Off-topic: If you are using drbd, how are you managing the synchro when the master BA comes online again? Don't know what you want to know here. We have heartbeat configured with auto_failback off, so when BA comes up again, the vserver stay on BB until we interactively force the takeover. So we can have a look at BA and eventually start drbd on BA if that doesn't happen automagically. If you want to force a full sync, you have to delete all files in /var/lib/drbd before reconnecting BA. After drbd has synced the disk(s) you can do a /usr/lib/heartbeat/hb_standby foreign on BB to force the failback of the vservers. Sorry, my question was not correctly formulated, but you gave me the answer anyway :-) I was not sure about the synchro back from BB to BA when BA comes online again, but definitely it looks like doing that manually is better at least to correctly check BA. Thanks for your complete and fast answer, loic ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] VServer, heartbeat and drbd
Dear All, I am new on the list, so please excuse my naive question. I went through the how-tos and the archives of the list, but was enable to find the answer to my question. It is between heartbeat and vserver so I hope not to be completely off-topic. Supposing I run 2 boxes BA and BB each has its very own IP + 1 ip for the vserver. When BA goes down, BB take over. DRBD mount the /vservers partition on BB as primary, then a script from linux-ha start the vserver on BB. Do I am wrong or thanks to the vserver approach I don't need to setup an ip takeover? Or formulated another way: heartbeat is only used to start the vserver on BB if BA goes down, drbd taking care of the synchro of the data. If anybody of you have experience with VServer, heartbeat and drbd I would be happy to have your feedback. Off-topic: If you are using drbd, how are you managing the synchro when the master BA comes online again? You will get a little howto if I succeed setting up all that. Best regards, loic -- loïc d'Anterroches [EMAIL PROTECTED] CAPEC, Department of Chemical Engineering Technical University of Denmark, DK-2800 Lyngby, Denmark tel: (+45)4525 2911 fax: (+45)4593 2906 ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
