From owner-freebsd-cluster@FreeBSD.ORG Wed Sep 29 20:30:19 2004 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E358016A4CE for ; Wed, 29 Sep 2004 20:30:19 +0000 (GMT) Received: from ack.xyberpix.com (xyberpix.demon.co.uk [83.104.33.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4398443D31 for ; Wed, 29 Sep 2004 20:30:19 +0000 (GMT) (envelope-from xyberpix@xyberpix.com) Received: from [192.168.1.16] (unknown [83.104.33.136]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by ack.xyberpix.com (Postfix) with ESMTP id 80BA91EC493 for ; Tue, 28 Sep 2004 21:28:53 +0100 (BST) From: xyberpix To: "FreeBSD-cluster[List]" Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ZhzNbQtHjydm1i03JoUH" Message-Id: <1096488485.2760.29.camel@syn> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6-2mdk Date: Wed, 29 Sep 2004 21:08:05 +0100 Subject: Cluster help X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 20:30:20 -0000 --=-ZhzNbQtHjydm1i03JoUH Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi All, Here's my scenario: I currently have a machine running FreeBSD,Postfix, with SSL and TLS and now I want to set up another machine, and then cluster the two machines. Ideally what I would like is to have the cluster working as a HA cluster, so that if one node fails, the other will take over. Problem: I have no idea where to start with this, and Google really hasn't been too kind to me, so I am looking for any assistance that anyone is willing to give. TIA xyberpix --=20 For Security and Open Source news: http://xyberpix.demon.co.uk --=-ZhzNbQtHjydm1i03JoUH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBWxYkim9OFinkmJQRArTtAKC9y8thhITJ/9dSVEOcteg3UOFP+QCZATcE FeSfvMzIDYf/PH/Xt4S8qnA= =PCqT -----END PGP SIGNATURE----- --=-ZhzNbQtHjydm1i03JoUH-- From owner-freebsd-cluster@FreeBSD.ORG Wed Sep 29 22:00:58 2004 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE27116A4CF for ; Wed, 29 Sep 2004 22:00:58 +0000 (GMT) Received: from watcher.puryear-it.com (ip-66-186-248-99.static.eatel.net [66.186.248.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BDBB43D5C for ; Wed, 29 Sep 2004 22:00:58 +0000 (GMT) (envelope-from dustin@puryear-it.com) Received: from localhost (unknown [127.0.0.1]) by watcher.puryear-it.com (Postfix) with ESMTP id BBF4034D2F; Wed, 29 Sep 2004 16:57:52 -0500 (CDT) Received: from watcher.puryear-it.com ([127.0.0.1]) by localhost (watcher.puryear-it.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50145-10; Wed, 29 Sep 2004 16:57:51 -0500 (CDT) Received: from THEBOX (localhost [127.0.0.1]) by watcher.puryear-it.com (Postfix) with SMTP id B24EC34D1E; Wed, 29 Sep 2004 16:57:50 -0500 (CDT) Message-ID: <009d01c4a66f$c6de3ad0$0200a8c0@THEBOX> From: "Dustin Puryear" To: "xyberpix" References: <1096488485.2760.29.camel@syn> Date: Wed, 29 Sep 2004 17:00:00 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new cc: freebsd-cluster@freebsd.org Subject: Re: Cluster help X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 22:00:59 -0000 Hi. This is definitely doable. Some options: 1. Use a front-end load-balancer. This makes your life very easy. 2. Use MX records. 3. Use various tools available for FreeBSD for IP fail-over. One of your biggest concerns is going to be storage. If a server fails-over do you need to worry about the secondary server having access to the primary's files? You didn't provide quite enough detail for me to tell. --- Puryear Information Technology, LLC Baton Rouge, LA * 225-706-8414 http://www.puryear-it.com Author of "Best Practices for Managing Linux and UNIX Servers" Download your free copy: http://www.puryear-it.com/bestpractices_ebook.htm From owner-freebsd-cluster@FreeBSD.ORG Wed Sep 29 22:09:43 2004 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DA3716A4CE for ; Wed, 29 Sep 2004 22:09:43 +0000 (GMT) Received: from ack.xyberpix.com (xyberpix.demon.co.uk [83.104.33.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AD6C43D41 for ; Wed, 29 Sep 2004 22:09:43 +0000 (GMT) (envelope-from xyberpix@xyberpix.com) Received: from [192.168.1.16] (unknown [83.104.33.136]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by ack.xyberpix.com (Postfix) with ESMTP id 2AC781EC493; Tue, 28 Sep 2004 23:08:18 +0100 (BST) From: xyberpix To: Dustin Puryear In-Reply-To: <009d01c4a66f$c6de3ad0$0200a8c0@THEBOX> References: <1096488485.2760.29.camel@syn> <009d01c4a66f$c6de3ad0$0200a8c0@THEBOX> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-pdHCHjBUjxp18tIHsWmE" Message-Id: <1096494446.2760.37.camel@syn> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6-2mdk Date: Wed, 29 Sep 2004 22:47:27 +0100 cc: "FreeBSD-cluster\[List\]" Subject: Re: Cluster help X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 22:09:43 -0000 --=-pdHCHjBUjxp18tIHsWmE Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Dustin, Ok, so things are sounding positive already, this is great news! As for using a load balancer, not an option, this is for home use, not work, so the finances are a bit low. :( As for the using MX records, I could do that, but the only problem is that I only have 1 external IP addy, so unless someone is willing to donate a spare one, and set up routing for me for nothing, which I can't really see happening, this isn't really an option right now. I have looked into getting more IP addy's from my ISP, but all the effort is not really worth it at this point, and neither is the price. You mentioned various tools available for FreeBSD for IP failover, can you maybe please let me have some names, as this may be a good option for me. As for if a server fails over, it would be nice to have access to the primary servers files, but this isn't really a necessity, as I am sure I can accomplish this with nightly backups, and then a script to copy things over to the secondary server, what do you think? Thanks again xyberpix On Wed, 2004-09-29 at 23:00, Dustin Puryear wrote: > Hi. This is definitely doable. Some options: >=20 > 1. Use a front-end load-balancer. This makes your life very easy. > 2. Use MX records. > 3. Use various tools available for FreeBSD for IP fail-over. >=20 > One of your biggest concerns is going to be storage. If a server fails-ov= er > do you need to worry about the secondary server having access to the > primary's files? You didn't provide quite enough detail for me to tell. >=20 > --- > Puryear Information Technology, LLC > Baton Rouge, LA * 225-706-8414 > http://www.puryear-it.com >=20 > Author of "Best Practices for Managing Linux and UNIX Servers" > Download your free copy: > http://www.puryear-it.com/bestpractices_ebook.htm --=20 For Security and Open Source news: http://xyberpix.demon.co.uk --=-pdHCHjBUjxp18tIHsWmE Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBWy1tim9OFinkmJQRAp0sAKCdFdtijGvpQwcGGCt2u+i2Enzr1gCghQIv ZbqoCyH8ZOcBmdq9kkEc63g= =riEu -----END PGP SIGNATURE----- --=-pdHCHjBUjxp18tIHsWmE-- From owner-freebsd-cluster@FreeBSD.ORG Wed Sep 29 22:19:07 2004 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB1FE16A4CE for ; Wed, 29 Sep 2004 22:19:07 +0000 (GMT) Received: from freebsdcluster.org (freebsdcluster.dk [195.184.98.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B4FA43D4C for ; Wed, 29 Sep 2004 22:19:07 +0000 (GMT) (envelope-from lasse@freebsdcluster.org) Received: from localhost (localhost.dk [127.0.0.1]) by freebsdcluster.org (Postfix) with ESMTP id CDD74622A; Thu, 30 Sep 2004 00:20:48 +0200 (CEST) Received: from freebsdcluster.org ([127.0.0.1]) by localhost (freebsdcluster.dk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36151-03; Thu, 30 Sep 2004 00:20:41 +0200 (CEST) Received: by freebsdcluster.org (Postfix, from userid 65534) id 4DDE56234; Thu, 30 Sep 2004 00:20:41 +0200 (CEST) Received: from host-84-9-26-23.bulldogdsl.com (host-84-9-26-23.bulldogdsl.com [84.9.26.23]) by www.freebsdcluster.org (IMP) with HTTP for ; Thu, 30 Sep 2004 00:20:40 +0200 Message-ID: <1096496440.415b353902146@www.freebsdcluster.org> Date: Thu, 30 Sep 2004 00:20:41 +0200 From: "Lasse L. Johnsen" To: xyberpix References: <1096488485.2760.29.camel@syn> <009d01c4a66f$c6de3ad0$0200a8c0@THEBOX> <1096494446.2760.37.camel@syn> In-Reply-To: <1096494446.2760.37.camel@syn> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.6 X-Originating-IP: 84.9.26.23 X-Virus-Scanned: by amavisd-new at example.com cc: "FreeBSD-cluster\[List\]" cc: Dustin Puryear Subject: Re: Cluster help X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 22:19:07 -0000 Hello, Have a look at freevrrpd (http://www.freebsd.org/cgi/url.cgi?ports/net/freevrrpd/pkg-descr) it a nice tool for sharing one IP address between two machines. So for instance machine A has IP 10.0.0.2 and machine B has IP 10.0.0.3. If you run vrrpd on them both, you can give machine A the additional IP address 10.0.0.1, machine B will then constantly check that machine A is running. In case it's not, machine B will assume the IP address 10.0.0.1. vrrpd also provide hooks for launching various scripts when a switch happen so you can start up say a postfix instance on machine B to take over the job of machine A. (I'm sure the documentation explains it better than me). Hope you make it work. Br, Lasse Quoting xyberpix : > Hi Dustin, > > Ok, so things are sounding positive already, this is great news! > > As for using a load balancer, not an option, this is for home use, not > work, so the finances are a bit low. :( > As for the using MX records, I could do that, but the only problem is > that I only have 1 external IP addy, so unless someone is willing to > donate a spare one, and set up routing for me for nothing, which I can't > really see happening, this isn't really an option right now. I have > looked into getting more IP addy's from my ISP, but all the effort is > not really worth it at this point, and neither is the price. > You mentioned various tools available for FreeBSD for IP failover, can > you maybe please let me have some names, as this may be a good option > for me. > As for if a server fails over, it would be nice to have access to the > primary servers files, but this isn't really a necessity, as I am sure I > can accomplish this with nightly backups, and then a script to copy > things over to the secondary server, what do you think? > > Thanks again > xyberpix > > > On Wed, 2004-09-29 at 23:00, Dustin Puryear wrote: > > Hi. This is definitely doable. Some options: > > > > 1. Use a front-end load-balancer. This makes your life very easy. > > 2. Use MX records. > > 3. Use various tools available for FreeBSD for IP fail-over. > > > > One of your biggest concerns is going to be storage. If a server fails-over > > do you need to worry about the secondary server having access to the > > primary's files? You didn't provide quite enough detail for me to tell. > > > > --- > > Puryear Information Technology, LLC > > Baton Rouge, LA * 225-706-8414 > > http://www.puryear-it.com > > > > Author of "Best Practices for Managing Linux and UNIX Servers" > > Download your free copy: > > http://www.puryear-it.com/bestpractices_ebook.htm > -- > For Security and Open Source news: > http://xyberpix.demon.co.uk > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From owner-freebsd-cluster@FreeBSD.ORG Wed Sep 29 23:34:54 2004 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9734B16A4CE for ; Wed, 29 Sep 2004 23:34:54 +0000 (GMT) Received: from out010.verizon.net (out010pub.verizon.net [206.46.170.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C38343D55 for ; Wed, 29 Sep 2004 23:34:54 +0000 (GMT) (envelope-from steve@n2sw.com) Received: from STACY ([24.90.108.92]) by out010.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040929233453.QPGE23744.out010.verizon.net@STACY>; Wed, 29 Sep 2004 18:34:53 -0500 From: "Steve" To: "'Lasse L. Johnsen'" , "'xyberpix'" Date: Wed, 29 Sep 2004 19:34:50 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <1096496440.415b353902146@www.freebsdcluster.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcSmclxnUkQCfcRqTLKWI+Wj5DpMHwAClPBg X-Authentication-Info: Submitted using SMTP AUTH at out010.verizon.net from [24.90.108.92] at Wed, 29 Sep 2004 18:34:53 -0500 Message-Id: <20040929233453.QPGE23744.out010.verizon.net@STACY> cc: "'FreeBSD-cluster\[List\]'" cc: 'Dustin Puryear' Subject: RE: Cluster help X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 23:34:54 -0000 I would use rsync to mirror By the way are you using imap style dirs with postfix, As for the failover that tool mentioned below works great Assign diff ips to the two servers, and on the router (there is one I assume) forward port 25 and 110 to the failover ip -- Steve Rieger -----Original Message----- From: owner-freebsd-cluster@freebsd.org [mailto:owner-freebsd-cluster@freebsd.org] On Behalf Of Lasse L. Johnsen Sent: Wednesday, September 29, 2004 6:21 PM To: xyberpix Cc: FreeBSD-cluster[List]; Dustin Puryear Subject: Re: Cluster help Hello, Have a look at freevrrpd (http://www.freebsd.org/cgi/url.cgi?ports/net/freevrrpd/pkg-descr) it a nice tool for sharing one IP address between two machines. So for instance machine A has IP 10.0.0.2 and machine B has IP 10.0.0.3. If you run vrrpd on them both, you can give machine A the additional IP address 10.0.0.1, machine B will then constantly check that machine A is running. In case it's not, machine B will assume the IP address 10.0.0.1. vrrpd also provide hooks for launching various scripts when a switch happen so you can start up say a postfix instance on machine B to take over the job of machine A. (I'm sure the documentation explains it better than me). Hope you make it work. Br, Lasse Quoting xyberpix : > Hi Dustin, > > Ok, so things are sounding positive already, this is great news! > > As for using a load balancer, not an option, this is for home use, not > work, so the finances are a bit low. :( As for the using MX records, I > could do that, but the only problem is that I only have 1 external IP > addy, so unless someone is willing to donate a spare one, and set up > routing for me for nothing, which I can't really see happening, this > isn't really an option right now. I have looked into getting more IP > addy's from my ISP, but all the effort is not really worth it at this > point, and neither is the price. > You mentioned various tools available for FreeBSD for IP failover, can > you maybe please let me have some names, as this may be a good option > for me. > As for if a server fails over, it would be nice to have access to the > primary servers files, but this isn't really a necessity, as I am sure > I can accomplish this with nightly backups, and then a script to copy > things over to the secondary server, what do you think? > > Thanks again > xyberpix > > > On Wed, 2004-09-29 at 23:00, Dustin Puryear wrote: > > Hi. This is definitely doable. Some options: > > > > 1. Use a front-end load-balancer. This makes your life very easy. > > 2. Use MX records. > > 3. Use various tools available for FreeBSD for IP fail-over. > > > > One of your biggest concerns is going to be storage. If a server > > fails-over do you need to worry about the secondary server having > > access to the primary's files? You didn't provide quite enough detail for me to tell. > > > > --- > > Puryear Information Technology, LLC > > Baton Rouge, LA * 225-706-8414 > > http://www.puryear-it.com > > > > Author of "Best Practices for Managing Linux and UNIX Servers" > > Download your free copy: > > http://www.puryear-it.com/bestpractices_ebook.htm > -- > For Security and Open Source news: > http://xyberpix.demon.co.uk > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ freebsd-cluster@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-cluster To unsubscribe, send any mail to "freebsd-cluster-unsubscribe@freebsd.org"