Re: IMAP automagic replication?
El sáb, 28-02-2004 a las 18:51, Adam ENDRODI escribió: On Sun, Feb 29, 2004 at 01:00:09AM +0100, Kilian Krause wrote: I came accross the idea of using CODA for replication of the filesys even though the slow network connection, but somewhat i doubt it'll be performant over internet. Especially more performant than plain IMAP replication. Anybody having numbers on these ones? I guess you don't want to sync at the file system level. Coda won't be an easy battle and is generally agreed not to be suitable for real-time applications (read: bloody slow). Moreover, apart from the rumours, wou'd definitely need to complicate the architect with another layer--some kind of encrypting tunnel. DRBD ... this is what i use, and it works fine. It is very bandwith sensitive though. just my gut feelings, adam -- Am I a cleric? | 1024D/37B8D989 Or maybe a sinner? | 954B 998A E5F5 BA2A 3622 Unbeliever?| 82DD 54C2 843D 37B8 D989 Renegade? | http://sks.dnsalias.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IMAP automagic replication?
El sáb, 28-02-2004 a las 18:51, Adam ENDRODI escribió: On Sun, Feb 29, 2004 at 01:00:09AM +0100, Kilian Krause wrote: I came accross the idea of using CODA for replication of the filesys even though the slow network connection, but somewhat i doubt it'll be performant over internet. Especially more performant than plain IMAP replication. Anybody having numbers on these ones? I guess you don't want to sync at the file system level. Coda won't be an easy battle and is generally agreed not to be suitable for real-time applications (read: bloody slow). Moreover, apart from the rumours, wou'd definitely need to complicate the architect with another layer--some kind of encrypting tunnel. DRBD ... this is what i use, and it works fine. It is very bandwith sensitive though. just my gut feelings, adam -- Am I a cleric? | 1024D/37B8D989 Or maybe a sinner? | 954B 998A E5F5 BA2A 3622 Unbeliever?| 82DD 54C2 843D 37B8 D989 Renegade? | http://sks.dnsalias.net
IMAP automagic replication?
Hi guys, i have 2 systems up with Exim+Procmail+Courier-IMAPd serving my Maildirs.. So far, so easy and working fine. ;) Synchronization with mailsync does work ok, but takes kinda long (too long to make it run every few minutes) However, now i want to add some magic that when i read Mail on one system it's automagically synced to the other. A friend of mine proposed Cyrus and murder to setup a load balancer which would sync all imap requests altering one mailspool to the other. (and mail could be relayed to the other system thru a procmail recipe with setting an X-Loop header, so that'd be easy enough) Has anyone already gotten Courier to replicate or shall i give Cyrus a try? Thanks for your oppinion ;) -- Best regards, Kilian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: IMAP automagic replication?
Hi again ;) maybe to clearify why not simply going NFS or whatever local filesys replication: the servers are not in one network, but the one is on 768/128 kBit DSL and shall serve for the local net it's in. I came accross the idea of using CODA for replication of the filesys even though the slow network connection, but somewhat i doubt it'll be performant over internet. Especially more performant than plain IMAP replication. Anybody having numbers on these ones? -- Best regards, Kilian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: IMAP automagic replication?
On Sun, Feb 29, 2004 at 01:00:09AM +0100, Kilian Krause wrote: I came accross the idea of using CODA for replication of the filesys even though the slow network connection, but somewhat i doubt it'll be performant over internet. Especially more performant than plain IMAP replication. Anybody having numbers on these ones? I guess you don't want to sync at the file system level. Coda won't be an easy battle and is generally agreed not to be suitable for real-time applications (read: bloody slow). Moreover, apart from the rumours, wou'd definitely need to complicate the architect with another layer--some kind of encrypting tunnel. just my gut feelings, adam -- Am I a cleric? | 1024D/37B8D989 Or maybe a sinner? | 954B 998A E5F5 BA2A 3622 Unbeliever?| 82DD 54C2 843D 37B8 D989 Renegade? | http://sks.dnsalias.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: replication
Thanks for your suggestions and the two people who replied off list. This will probably work well without too much time invested :-) On Wednesday 19 March 2003 12:32 am, Marcin Sochacki wrote: On Tue, Mar 18, 2003 at 11:13:50AM -0700, [EMAIL PROTECTED] wrote: As a favor to a friend, I'm trying to setup a mirror of his server, where I can basically be a 'hotswap' for him. So far, the main problem that I'm running into is that everything is ip-based. For instance, it's dead-simple to be a secondary dns server for him, but if his box (which hosts dns, web, and mail) goes down, then I'm simply pointing people into dead-space, right? Well, email is the one standout, where the MX records would get them to my machine, but I'm having a hard time figuring out how to make web and dns do the same thing. If you're hosting secondary DNS, it shouldn't be too difficult. First, change the default TTL of your zone to a very low value, like one minute. This way you'll almost prevent caching of DNS records on other hosts. When your (secondary) machine detects, that the primary one is dead, you should swap the configuration files for your bind, and make yourself a primary, and the only one nameserver for the particular domain, with the addresses pointing to your machine. Reload bind, and from that moment all HTTP requests should start hitting your server. You should constantly monitor if the primary machine comes back online, and if it does -- swap the bind configuration back to original state. It also means, that you should parse the mirrored httpd.conf and change the IP in VirtualHost to your address. I don't think you need any special software -- everything can be done with a couple of scripts in your favourite scripting language. Marcin -- MuMlutlitithtrhreeaadededd s siigngnatatuurere D.A.Bishop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: replication
On Tue, Mar 18, 2003 at 11:13:50AM -0700, [EMAIL PROTECTED] wrote: As a favor to a friend, I'm trying to setup a mirror of his server, where I can basically be a 'hotswap' for him. So far, the main problem that I'm running into is that everything is ip-based. For instance, it's dead-simple to be a secondary dns server for him, but if his box (which hosts dns, web, and mail) goes down, then I'm simply pointing people into dead-space, right? Well, email is the one standout, where the MX records would get them to my machine, but I'm having a hard time figuring out how to make web and dns do the same thing. If you're hosting secondary DNS, it shouldn't be too difficult. First, change the default TTL of your zone to a very low value, like one minute. This way you'll almost prevent caching of DNS records on other hosts. When your (secondary) machine detects, that the primary one is dead, you should swap the configuration files for your bind, and make yourself a primary, and the only one nameserver for the particular domain, with the addresses pointing to your machine. Reload bind, and from that moment all HTTP requests should start hitting your server. You should constantly monitor if the primary machine comes back online, and if it does -- swap the bind configuration back to original state. It also means, that you should parse the mirrored httpd.conf and change the IP in VirtualHost to your address. I don't think you need any special software -- everything can be done with a couple of scripts in your favourite scripting language. Marcin
Re: replication
Thanks for your suggestions and the two people who replied off list. This will probably work well without too much time invested :-) On Wednesday 19 March 2003 12:32 am, Marcin Sochacki wrote: On Tue, Mar 18, 2003 at 11:13:50AM -0700, [EMAIL PROTECTED] wrote: As a favor to a friend, I'm trying to setup a mirror of his server, where I can basically be a 'hotswap' for him. So far, the main problem that I'm running into is that everything is ip-based. For instance, it's dead-simple to be a secondary dns server for him, but if his box (which hosts dns, web, and mail) goes down, then I'm simply pointing people into dead-space, right? Well, email is the one standout, where the MX records would get them to my machine, but I'm having a hard time figuring out how to make web and dns do the same thing. If you're hosting secondary DNS, it shouldn't be too difficult. First, change the default TTL of your zone to a very low value, like one minute. This way you'll almost prevent caching of DNS records on other hosts. When your (secondary) machine detects, that the primary one is dead, you should swap the configuration files for your bind, and make yourself a primary, and the only one nameserver for the particular domain, with the addresses pointing to your machine. Reload bind, and from that moment all HTTP requests should start hitting your server. You should constantly monitor if the primary machine comes back online, and if it does -- swap the bind configuration back to original state. It also means, that you should parse the mirrored httpd.conf and change the IP in VirtualHost to your address. I don't think you need any special software -- everything can be done with a couple of scripts in your favourite scripting language. Marcin -- MuMlutlitithtrhreeaadededd s siigngnatatuurere D.A.Bishop
replication
As a favor to a friend, I'm trying to setup a mirror of his server, where I can basically be a 'hotswap' for him. So far, the main problem that I'm running into is that everything is ip-based. For instance, it's dead-simple to be a secondary dns server for him, but if his box (which hosts dns, web, and mail) goes down, then I'm simply pointing people into dead-space, right? Well, email is the one standout, where the MX records would get them to my machine, but I'm having a hard time figuring out how to make web and dns do the same thing. To explain what I mean, say he's box a, ip 10.0.0.1, i'm b, ip 192.168.0.1. We are on completely different networks, with different providers. So his machine/connection goes down, and I, using mon or bb, detect it. Now what? bind happily tells people to go to 10.0.0.1 for foo.org. My carefully mirrored httpd.conf contains a bunch of lines talking about VirtualHost 10.0.0.1:80. Without manually editing all those, what's the solution? And, just to make things doubly difficult, it would be really, really nice if it worked as both a 'normal' secondary, and a mirror, at the same time. :-P But if I had to choose, it'd definetly be to be a mirror. Pointers to the FM to R would be appreciated, google just got me a bunch of links about mirroring with hot-swappable computers on the same network, or setting up secondary dns servers, neither of which as particularly helpful :-) Thanks! D.A.Bishop P.S. The most helpful thing is that we are running matching version of debian, so software installing/version matching is no problem at all... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: replication
On Tue, Mar 18, 2003 at 11:13:50AM -0700, [EMAIL PROTECTED] wrote: As a favor to a friend, I'm trying to setup a mirror of his server, where I can basically be a 'hotswap' for him. So far, the main problem that I'm running into is that everything is ip-based. For instance, it's dead-simple to be a secondary dns server for him, but if his box (which hosts dns, web, and mail) goes down, then I'm simply pointing people into dead-space, right? Well, email is the one standout, where the MX records would get them to my machine, but I'm having a hard time figuring out how to make web and dns do the same thing. If you're hosting secondary DNS, it shouldn't be too difficult. First, change the default TTL of your zone to a very low value, like one minute. This way you'll almost prevent caching of DNS records on other hosts. When your (secondary) machine detects, that the primary one is dead, you should swap the configuration files for your bind, and make yourself a primary, and the only one nameserver for the particular domain, with the addresses pointing to your machine. Reload bind, and from that moment all HTTP requests should start hitting your server. You should constantly monitor if the primary machine comes back online, and if it does -- swap the bind configuration back to original state. It also means, that you should parse the mirrored httpd.conf and change the IP in VirtualHost to your address. I don't think you need any special software -- everything can be done with a couple of scripts in your favourite scripting language. Marcin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
replication
As a favor to a friend, I'm trying to setup a mirror of his server, where I can basically be a 'hotswap' for him. So far, the main problem that I'm running into is that everything is ip-based. For instance, it's dead-simple to be a secondary dns server for him, but if his box (which hosts dns, web, and mail) goes down, then I'm simply pointing people into dead-space, right? Well, email is the one standout, where the MX records would get them to my machine, but I'm having a hard time figuring out how to make web and dns do the same thing. To explain what I mean, say he's box a, ip 10.0.0.1, i'm b, ip 192.168.0.1. We are on completely different networks, with different providers. So his machine/connection goes down, and I, using mon or bb, detect it. Now what? bind happily tells people to go to 10.0.0.1 for foo.org. My carefully mirrored httpd.conf contains a bunch of lines talking about VirtualHost 10.0.0.1:80. Without manually editing all those, what's the solution? And, just to make things doubly difficult, it would be really, really nice if it worked as both a 'normal' secondary, and a mirror, at the same time. :-P But if I had to choose, it'd definetly be to be a mirror. Pointers to the FM to R would be appreciated, google just got me a bunch of links about mirroring with hot-swappable computers on the same network, or setting up secondary dns servers, neither of which as particularly helpful :-) Thanks! D.A.Bishop P.S. The most helpful thing is that we are running matching version of debian, so software installing/version matching is no problem at all...
LDAP replication problem
= get_ctrls: oid="2.16.840.1.113730.3.4.2" (critical)
= get_ctrls: 1 0
conn=0 op=1 ADD
dn="[EMAIL PROTECTED],OU=EMAIL,DC=COKER,DC=COM,DC=AU"
is_entry_objectclass("[EMAIL PROTECTED],ou=EMail,dc=coker,dc=com,dc=au",
"2.16.840.1.113730.3.2.6") no objectClass attribute
The above is the final output of "slapd -d-1" on the LDAP slave when slurpd
is trying to write data.
At this time the slurpd will stop and no further replication will occur.
This only occurs when adding new objects into the directory, if I use slapcat
to get the LDIF for the master, scp it to the slave and then create a new
slave database with slapadd then after that replication can be used for
changes to the same object.
I don't know what "2.16.840.1.113730.3.2.6" is. It's not in any of the
schema files that come with openLDAP.
Also what's the OID 2.16.840.1.113730.3.2.TBD in misc.schema in the latest
slapd package? Isn't the "TBD" part a violation of the syntax?
Ben, I am CCing you because I think that some part or parts of this message
may refer to bugs in your OpenLDAP packages. But at the moment I'm not sure
in which way (so I'm not reporting bugs until after some discussion).
--
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
LDAP replication problem
= get_ctrls: oid=2.16.840.1.113730.3.4.2 (critical) = get_ctrls: 1 0 conn=0 op=1 ADD dn=[EMAIL PROTECTED],OU=EMAIL,DC=COKER,DC=COM,DC=AU is_entry_objectclass([EMAIL PROTECTED],ou=EMail,dc=coker,dc=com,dc=au, 2.16.840.1.113730.3.2.6) no objectClass attribute The above is the final output of slapd -d-1 on the LDAP slave when slurpd is trying to write data. At this time the slurpd will stop and no further replication will occur. This only occurs when adding new objects into the directory, if I use slapcat to get the LDIF for the master, scp it to the slave and then create a new slave database with slapadd then after that replication can be used for changes to the same object. I don't know what 2.16.840.1.113730.3.2.6 is. It's not in any of the schema files that come with openLDAP. Also what's the OID 2.16.840.1.113730.3.2.TBD in misc.schema in the latest slapd package? Isn't the TBD part a violation of the syntax? Ben, I am CCing you because I think that some part or parts of this message may refer to bugs in your OpenLDAP packages. But at the moment I'm not sure in which way (so I'm not reporting bugs until after some discussion). -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
