replication from slave to master

Hello! I get replication works with 2.3.7. It works from master SLES9/x86 to slave CentOS/x86-64. Now I want to change server roles. I changed configs and start sync_client on slave. And get error: Jul 17 12:54:30 backup sync_client[12963]: Doing a peer verify Jul 17 12:54:30 backup sync_clie

Re: 2.3.1 replication and deliver problem

- Original Message - From: "Patrick H Radtke" <[EMAIL PROTECTED]> To: "Dmitry Melekhov" <[EMAIL PROTECTED]> Cc: Sent: Friday, February 03, 2006 6:40 PM Subject: Re: 2.3.1 replication and deliver problem On Fri, 3 Feb 2006, Dmitry Melekhov wrote:

Re: 2.3.1 replication and deliver problem

Patrick Radtke wrote: Maybe check the log on your replica. Possibly something is going wrong with sync_server (though it seems unlikely since sync_client -u works) Yes. Something is wrong with sync_server. Feb 3 09:10:28 backup syncserver[1899]: Fatal error: Virtual memory exhausted

Re: 2.3.1 replication and deliver problem

David Carter wrote: On Tue, 31 Jan 2006, Dmitry Melekhov wrote: This is what I see. Promoting: MAILBOX user.dm -> USER dm Error in do_sync(): bailing out! Not too informational message... syslog should tell you why it decided to bail out. Unfortunately I see in log (i.e. -l ) only w

Re: 2.3.1 replication and deliver problem

Patrick H Radtke wrote: But it is not completely clear how sync_client -r replication works. I see that this process juts disappears after some time and I see no replication at all... but sync_client -u replication works OK.. sync_client -r should stay running. Try running it with the -l -r

Re: 2.3.1 replication and deliver problem

Patrick H Radtke wrote: I don't think your replica machine ('backup') is configured correctly Thank you! You were right. Now sync_client connects to server correctly. But it is not completely clear how sync_client -r replication works. I see that this process juts disappears after some

Re: 2.3.1 replication and deliver problem

Patrick H Radtke wrote: So the connection works, but there is probably a problem with the authentication. What authentication mechanism are you useing for sync_client? sync_server should advertise the available SASL mechanisms. If you are using PLAIN then you need to have a certificate,

2.3.1 replication and deliver problem

Hello! It doesn't work for me [EMAIL PROTECTED]:~> sync_client -S backup -r Can not connect to server 'backup' On the other side: Jan 18 16:18:50 backup master[16437]: about to exec /usr/lib/cyrus/bin/sync_server Jan 18 16:18:51 backup syncserver[16437]: executed Jan 18 16:18:51 backup sync

Re: Cyrus 2.0.7 death by 11 again

11 > ...etc. > > lmtpd works without core dump only pop3d and imapd. > > I have the same problem if /etc/sasldb exists :( If it not exists all works OK, but sometimes imapd crash with the same message. Did you solve this problem? -- Dmitry Melekhov http://www.aspec.ru/~dm 2:5050/11.23@fidonet

problem with 2.0.7

Hello! We use cyrus 2.0.7 with cyrus-sasl 1.5.24. Problem is that we get message unable to open Berkeley db /etc/sasldb If we create this file than imapd is coredump. I don't understand why it wants /etc/sasldb, if it configured to use PAM :( -- Dmitry Melekhov http://www.aspec.ru/~dm 2