- 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:
Vincent Deffontaines wrote:
Actually, my permission problem must be different from Dmitry's problem.
I just tried running sync_client by hand and it quits :
$/usr/cyrus/bin/sync_client -v -u username
Error from send_lock(): bailing out!
Syslog says :
sync_client[21692]: starttls: TLSv1 with cip
On Fri, 3 Feb 2006, Dmitry Melekhov wrote:
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[189
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
Vincent Deffontaines wrote:
Greetings,
I am experimenting problems quite similar to those of Dmitry.
I had the same TLS setup problem, now fixed. If interest is raised I can
patch the replication documentation so that other users will get it
straightforward.
Any additions/clarifications to t
Actually, my permission problem must be different from Dmitry's problem.
I just tried running sync_client by hand and it quits :
$/usr/cyrus/bin/sync_client -v -u username
Error from send_lock(): bailing out!
Syslog says :
sync_client[21692]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits
Greetings,
I am experimenting problems quite similar to those of Dmitry.
I had the same TLS setup problem, now fixed. If interest is raised I can
patch the replication documentation so that other users will get it
straightforward.
Now, here is what I get in my syslogs :
o Master server :
Feb
On Jan 31, 2006, at 4:06 AM, Dmitry Melekhov wrote:
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
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 what
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.
--
David Carter Email: [EMAIL PROTECTED]
Uni
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
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 and it
will log what its
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
On Thu, 19 Jan 2006, Dmitry Melekhov wrote:
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 usi
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,
On Thu, 19 Jan 2006, Dmitry Melekhov wrote:
Patrick Radtke wrote:
What happens when you try
telnet backup 2005
[EMAIL PROTECTED] dm]$ telnet backup 2005
Trying 192.168.22.211...
Connected to backup.p98.belkam.com (192.168.22.211).
Escape character is '^]'.
* OK backup Cyrus sync server v2
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
17 matches
Mail list logo
