Migration from one server to 2 new servers
Hi
I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
My Current Production Server details:
Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6
New Servers:
Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1
What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not.
Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
copy/migrate the data from old server to new servers. Please suggest what is the best way?
I see that dovecot version(2.0.9) in old production server, I do not know the which is the best option? see the options in the current version.
================================= [root@prodcution ~]# doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
=================================
Please suggest me.
Thanks, Kishore Potnuru
On 27/07/2020 11:59 Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi
I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
My Current Production Server details:
Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6
New Servers:
Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1
What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not.
Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
copy/migrate the data from old server to new servers. Please suggest what is the best way?
I see that dovecot version(2.0.9) in old production server, I do not know the which is the best option? see the options in the current version.
================================= [root@prodcution ~]# doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] =================================
Please suggest me.
Thanks, Kishore Potnuru
doveadm backup -R -u someone imapc:
comes to mind, with master password/master user authentication.
Aki
Hi,
But there is no "doveadm backup" option in dovecot 2.0.9 version.
[root@production ~]# doveadm -backup doveadm: invalid option -- 'b' [root@production ~]# dovecot --version 2.0.9
Copy the contents by using "scp", will that work?
Thanks, Kishore Potnuru
On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi aki.tuomi@open-xchange.com wrote:
On 27/07/2020 11:59 Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi
I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
My Current Production Server details:
Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6
New Servers:
Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1
What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not.
Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
copy/migrate the data from old server to new servers. Please suggest what is the best way?
I see that dovecot version(2.0.9) in old production server, I do not know the which is the best option? see the options in the current version.
================================= [root@prodcution ~]# doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] =================================
Please suggest me.
Thanks, Kishore Potnuru
doveadm backup -R -u someone imapc:
comes to mind, with master password/master user authentication.Aki
On Jul 27, 2020, at 9:20 AM, Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi,
But there is no "doveadm backup" option in dovecot 2.0.9 version.
[root@production ~]# doveadm -backup doveadm: invalid option -- 'b' [root@production ~]# dovecot --version 2.0.9
The command is "doveadm backup”.
Copy the contents by using "scp", will that work?
I would recommend against that approach unless you know what you are doing.
Thanks, Kishore Potnuru
On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi
mailto:aki.tuomi@open-xchange.com> wrote: On 27/07/2020 11:59 Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Hi
I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
My Current Production Server details:
Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6
New Servers:
Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1
What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not.
Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
copy/migrate the data from old server to new servers. Please suggest what is the best way?
I see that dovecot version(2.0.9) in old production server, I do not know the which is the best option? see the options in the current version.
================================= [root@prodcution ~]# doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] =================================
Please suggest me.
Thanks, Kishore Potnuru
doveadm backup -R -u someone imapc:
comes to mind, with master password/master user authentication.Aki
No, but there is backup option on the new server. That's why the -R, which means "backup to here".
Aki
On 27/07/2020 16:20 Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi,
But there is no "doveadm backup" option in dovecot 2.0.9 version.
[root@production ~]# doveadm -backup doveadm: invalid option -- 'b' [root@production ~]# dovecot --version 2.0.9
Copy the contents by using "scp", will that work?
Thanks, Kishore Potnuru
On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi aki.tuomi@open-xchange.com wrote:
On 27/07/2020 11:59 Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi
I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
My Current Production Server details:
Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6
New Servers:
Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1
What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not.
Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
copy/migrate the data from old server to new servers. Please suggest what is the best way?
I see that dovecot version(2.0.9) in old production server, I do not know the which is the best option? see the options in the current version.
================================= [root@prodcution ~]# doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] =================================
Please suggest me.
Thanks, Kishore Potnuru
doveadm backup -R -u someone imapc:
comes to mind, with master password/master user authentication.Aki
Hi ,
I have tried the below command from the new server. But I am getting an error. Anything is missing here?
======== [root@production1 test.org.com]# doveadm backup -R -u kishore@test.org.com remote:vmail@production2.baplc.com vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
========
On Mon, Jul 27, 2020 at 3:08 PM Aki Tuomi aki.tuomi@open-xchange.com wrote:
No, but there is backup option on the new server. That's why the -R, which means "backup to here".
Aki
On 27/07/2020 16:20 Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi,
But there is no "doveadm backup" option in dovecot 2.0.9 version.
[root@production ~]# doveadm -backup doveadm: invalid option -- 'b' [root@production ~]# dovecot --version 2.0.9
Copy the contents by using "scp", will that work?
Thanks, Kishore Potnuru
On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi aki.tuomi@open-xchange.com wrote:
On 27/07/2020 11:59 Kishore Potnuru kishore.reachme@gmail.com
Hi
I am in the process/planning of moving from my existing dovecot
imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
My Current Production Server details:
Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6
New Servers:
Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1
What is the best way to stop/copy/migrate the current production
data to the new servers? I am planning the following steps. Not sure if it is correct or not.
- Stop the Postfix services on the old server and wait for few
mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
- copy/migrate the data from old server to new servers. Please
suggest what is the best way?
- I see that dovecot version(2.0.9) in old production server, I do
not know the which is the best option? see the options in the current version.
================================= [root@prodcution ~]# doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query>
kick [-a <anvil socket path>] [-f] <user mask>[|]
log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] =================================
Please suggest me.
Thanks, Kishore Potnuru
doveadm backup -R -u someone imapc:
comes to mind, with masterwrote: password/master user authentication.
Aki
On 27. Jul 2020, at 23.11, Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi ,
I have tried the below command from the new server. But I am getting an error. Anything is missing here?
Are you sure that is dovecot 2.2.36?
Sami
Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
My Current Production Server details:
Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6
New Servers:
Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1
Thanks & Regards, Kishore
On Mon, 27 Jul, 2020, 9:43 pm Sami Ketola, sami.ketola@dovecot.fi wrote:
On 27. Jul 2020, at 23.11, Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi ,
I have tried the below command from the new server. But I am getting an error. Anything is missing here?
Are you sure that is dovecot 2.2.36?
Sami
On 28. Jul 2020, at 0.10, Kishore Potnuru kishore.reachme@gmail.com wrote:
Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version
2.2.36.8 (0c9d56b41)
[root@ketola ~]# doveadm backup
doveadm backup [-u <user>|-A] [-S
Sami
Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server…
[root at production1 https://dovecot.org/mailman/listinfo/dovecot test.org.com]# doveadm backup -R -u kishore at test.org.com https://dovecot.org/mailman/listinfo/dovecot remote:vmail at production2.baplc.com https://dovecot.org/mailman/listinfo/dovecot
...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
Maybe nothing but thought I would mention it…
On Jul 27, 2020, at 2:50 PM, Sami Ketola sami.ketola@dovecot.fi wrote:
On 28. Jul 2020, at 0.10, Kishore Potnuru kishore.reachme@gmail.com wrote:
Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version 2.2.36.8 (0c9d56b41) [root@ketola ~]# doveadm backup doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Sami
I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing.
The old version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The New version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com]# doveadm backup -R -u kishore@test.org.com remote:vmail@production1.baplc.com vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
[root@production2 test.org.com]#
=================================
On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding tech@leding.net wrote:
Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server…
[root at production1 https://dovecot.org/mailman/listinfo/dovecot test.org.com]# doveadm backup -R -u kishore at test.org.com https://dovecot.org/mailman/listinfo/dovecot remote:vmail at production2.baplc.com https://dovecot.org/mailman/listinfo/dovecot
...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
Maybe nothing but thought I would mention it…
On Jul 27, 2020, at 2:50 PM, Sami Ketola sami.ketola@dovecot.fi wrote:
On 28. Jul 2020, at 0.10, Kishore Potnuru kishore.reachme@gmail.com wrote:
Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version 2.2.36.8 (0c9d56b41) [root@ketola ~]# doveadm backup doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Sami
Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say “production1”…I just double-checked as well...
FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above…
Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2…
On Jul 27, 2020, at 3:10 PM, Kishore Potnuru kishore.reachme@gmail.com wrote:
I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing.
The old version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The New version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com http://test.org.com/]# doveadm backup -R -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production1.baplc.com mailto:remote%3Avmail@production1.baplc.com vmail@production1.baplc.com mailto:vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: read(vmail@production1.baplc.com mailto:vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com http://production1.baplc.com/ doveadm dsync-server -ukishore@test.org.com mailto:ukishore@test.org.com [root@production2 test.org.com http://test.org.com/]#
=================================
On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding
mailto:tech@leding.net> wrote: Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server… [root at production1 https://dovecot.org/mailman/listinfo/dovecot test.org.com http://test.org.com/]# doveadm backup -R -u kishore at test.org.com https://dovecot.org/mailman/listinfo/dovecot remote:vmail at production2.baplc.com https://dovecot.org/mailman/listinfo/dovecot
...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
Maybe nothing but thought I would mention it…
On Jul 27, 2020, at 2:50 PM, Sami Ketola
mailto:sami.ketola@dovecot.fi> wrote: On 28. Jul 2020, at 0.10, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version 2.2.36.8 (0c9d56b41) [root@ketola ~]# doveadm backup doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Sami
Also, FWIW...your doveadm command is missing quite a few options…here is mine…
[Jul-27 @ 15:11:57] > dovecot —version 2.3.10.1 (a3d0e1171)
[Jul-27 @ 15:22:39] > ls -l /usr/bin/doveadm -rwxr-xr-x. 1 root root 2949584 May 19 02:09 /usr/bin/doveadm
[Jul-27 @ 15:21:31] > doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
On Jul 27, 2020, at 3:18 PM, Antonio Leding tech@leding.net wrote:
Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say “production1”…I just double-checked as well...
FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above…
Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2…
On Jul 27, 2020, at 3:10 PM, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing.
The old version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The New version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com http://test.org.com/]# doveadm backup -R -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production1.baplc.com mailto:remote%3Avmail@production1.baplc.com vmail@production1.baplc.com mailto:vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: read(vmail@production1.baplc.com mailto:vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com http://production1.baplc.com/ doveadm dsync-server -ukishore@test.org.com mailto:ukishore@test.org.com [root@production2 test.org.com http://test.org.com/]#
=================================
On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding
mailto:tech@leding.net> wrote: Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server… [root at production1 https://dovecot.org/mailman/listinfo/dovecot test.org.com http://test.org.com/]# doveadm backup -R -u kishore at test.org.com https://dovecot.org/mailman/listinfo/dovecot remote:vmail at production2.baplc.com https://dovecot.org/mailman/listinfo/dovecot
...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
Maybe nothing but thought I would mention it…
On Jul 27, 2020, at 2:50 PM, Sami Ketola
mailto:sami.ketola@dovecot.fi> wrote: On 28. Jul 2020, at 0.10, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version 2.2.36.8 (0c9d56b41) [root@ketola ~]# doveadm backup doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Sami
Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com]# doveadm backup -R -u kishore@test.org.com remote:vmail@production1.baplc.com vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
[root@production2 test.org.com]#
=================================
On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding, tech@leding.net wrote:
Fair enough but the command snippet I posted was taken directly from your earlier post dated *Mon Jul 27 23:11:06 EEST 2020* and it does say “production1”…I just double-checked as well...
FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above…
Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2…
On Jul 27, 2020, at 3:10 PM, Kishore Potnuru kishore.reachme@gmail.com wrote:
I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com]# doveadm backup -R -u kishore@test.org.com remote:vmail@production1.baplc.com vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com): Error: read(vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com doveadm dsync-server - ukishore@test.org.com [root@production2 test.org.com]#
=================================
On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding tech@leding.net wrote:
Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server…
[root at production1 https://dovecot.org/mailman/listinfo/dovecot test.org.com]# doveadm backup -R -u kishore at test.org.com https://dovecot.org/mailman/listinfo/dovecot remote:vmail at production2.baplc.com https://dovecot.org/mailman/listinfo/dovecot
...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
Maybe nothing but thought I would mention it…
On Jul 27, 2020, at 2:50 PM, Sami Ketola sami.ketola@dovecot.fi wrote:
On 28. Jul 2020, at 0.10, Kishore Potnuru kishore.reachme@gmail.com wrote:
Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version 2.2.36.8 (0c9d56b41) [root@ketola ~]# doveadm backup doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Sami
Well that option set still doesn’t look correct…
Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36…
[Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2
[Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
[Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
On Jul 27, 2020, at 3:28 PM, Kishore Potnuru kishore.reachme@gmail.com wrote:
Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com http://test.org.com/]# doveadm backup -R -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production1.baplc.com mailto:remote%3Avmail@production1.baplc.com vmail@production1.baplc.com mailto:vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: read(vmail@production1.baplc.com mailto:vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com http://production1.baplc.com/ doveadm dsync-server -ukishore@test.org.com mailto:ukishore@test.org.com [root@production2 test.org.com http://test.org.com/]#
=================================
On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding,
mailto:tech@leding.net> wrote: Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say “production1”…I just double-checked as well... FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above…
Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2…
On Jul 27, 2020, at 3:10 PM, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com http://test.org.com/]# doveadm backup -R -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production1.baplc.com mailto:remote%3Avmail@production1.baplc.com vmail@production1.baplc.com mailto:vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: read(vmail@production1.baplc.com mailto:vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com http://production1.baplc.com/ doveadm dsync-server -ukishore@test.org.com mailto:ukishore@test.org.com [root@production2 test.org.com http://test.org.com/]#
=================================
On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding
mailto:tech@leding.net> wrote: Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server… [root at production1 https://dovecot.org/mailman/listinfo/dovecot test.org.com http://test.org.com/]# doveadm backup -R -u kishore at test.org.com https://dovecot.org/mailman/listinfo/dovecot remote:vmail at production2.baplc.com https://dovecot.org/mailman/listinfo/dovecot
...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
Maybe nothing but thought I would mention it…
On Jul 27, 2020, at 2:50 PM, Sami Ketola
mailto:sami.ketola@dovecot.fi> wrote: On 28. Jul 2020, at 0.10, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version 2.2.36.8 (0c9d56b41) [root@ketola ~]# doveadm backup doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Sami
This is what my understanding. May be I am also wrong here.
Backup option is there in my new server, production2.
When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same.
Sorry just incase if I am wrong.
Kishore
On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, tech@leding.net wrote:
Well that option set still doesn’t look correct…
Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36…
[Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2
[Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
[Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] [-r] <search query> auth cache|test backup [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> batch [-u <user>|-A] [-S ] <sep> <cmd1> [<sep> <cmd2> [..]] config [doveconf parameters] copy [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> director add|dump|flush|map|move|remove|ring|ring|ring|status dump [-t <type>] <path> exec <binary> [binary parameters] expunge [-u <user>|-A] [-S <socket_path>] [-d] <search query> fetch [-u <user>|-A] [-S <socket_path>] <fields> <search query> force-resync [-u <user>|-A] [-S <socket_path>] <mailbox mask> fs copy|delete|get|iter|iter-dirs|put|stat help <cmd> import [-u <user>|-A] [-S <socket_path>] [-s] <source mail location> <dest parent mailbox> <search query> index [-u <user>|-A] [-S <socket_path>] [-q] [-n <max recent>] <mailbox mask> instance list|remove kick [-a <anvil socket path>] [-f] <user mask>[|]<ip/bits> log errors|find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe mount add|list|remove move [-u <user>|-A] [-S <socket_path>] <destination> [user <source user>] <search query> penalty [-a <anvil socket path>] [<ip/bits>] proxy kick|list purge [-u <user>|-A] [-S <socket_path>] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] [-V] reload replicator remove|replicate|status search [-u <user>|-A] [-S <socket_path>] <search query> sis deduplicate|find stats dump|top stop sync [-u <user>|-A] [-S <socket_path>] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> user [-a <userdb socket path>] [-x <auth info>] [-f field] [-u] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [<ip/bits>] zlibconnect <host> [<port>]
On Jul 27, 2020, at 3:28 PM, Kishore Potnuru kishore.reachme@gmail.com wrote:
Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com]# doveadm backup -R -u kishore@test.org.com remote:vmail@production1.baplc.com vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com): Error: read(vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com doveadm dsync-server - ukishore@test.org.com [root@production2 test.org.com]#
=================================
On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding, tech@leding.net wrote:
Fair enough but the command snippet I posted was taken directly from your earlier post dated *Mon Jul 27 23:11:06 EEST 2020* and it does say “production1”…I just double-checked as well...
FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above…
Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2…
On Jul 27, 2020, at 3:10 PM, Kishore Potnuru kishore.reachme@gmail.com wrote:
I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com]# doveadm backup -R -u kishore@test.org.com remote:vmail@production1.baplc.com vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com): Error: read( vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com doveadm dsync-server - ukishore@test.org.com [root@production2 test.org.com]#
=================================
On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding tech@leding.net wrote:
Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server…
[root at production1 https://dovecot.org/mailman/listinfo/dovecot test.org.com]# doveadm backup -R -u kishore at test.org.com https://dovecot.org/mailman/listinfo/dovecot remote:vmail at production2.baplc.com https://dovecot.org/mailman/listinfo/dovecot
...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
Maybe nothing but thought I would mention it…
On Jul 27, 2020, at 2:50 PM, Sami Ketola sami.ketola@dovecot.fi wrote:
On 28. Jul 2020, at 0.10, Kishore Potnuru kishore.reachme@gmail.com wrote:
Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version 2.2.36.8 (0c9d56b41) [root@ketola ~]# doveadm backup doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Sami
I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side.
Do you have dsync on the 2.0.9 machine?
On Jul 27, 2020, at 4:16 PM, Kishore Potnuru kishore.reachme@gmail.com wrote:
This is what my understanding. May be I am also wrong here.
Backup option is there in my new server, production2.
When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same.
Sorry just incase if I am wrong.
Kishore
On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding,
mailto:tech@leding.net> wrote: Well that option set still doesn’t look correct… Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36…
[Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2
[Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
[Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] [-r] <search query> auth cache|test backup [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> batch [-u <user>|-A] [-S ] <sep> <cmd1> [<sep> <cmd2> [..]] config [doveconf parameters] copy [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> director add|dump|flush|map|move|remove|ring|ring|ring|status dump [-t <type>] <path> exec <binary> [binary parameters] expunge [-u <user>|-A] [-S ] [-d] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox mask> fs copy|delete|get|iter|iter-dirs|put|stat help <cmd> import [-u <user>|-A] [-S ] [-s] <source mail location> <dest parent mailbox> <search query> index [-u <user>|-A] [-S ] [-q] [-n <max recent>] <mailbox mask> instance list|remove kick [-a <anvil socket path>] [-f] <user mask>[|] log errors|find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe mount add|list|remove move [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> penalty [-a <anvil socket path>] [ ] proxy kick|list purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] [-V] reload replicator remove|replicate|status search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stats dump|top stop sync [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> user [-a <userdb socket path>] [-x <auth info>] [-f field] [-u] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] zlibconnect <host> [<port>] On Jul 27, 2020, at 3:28 PM, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com http://test.org.com/]# doveadm backup -R -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production1.baplc.com mailto:remote%3Avmail@production1.baplc.com vmail@production1.baplc.com mailto:vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: read(vmail@production1.baplc.com mailto:vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com http://production1.baplc.com/ doveadm dsync-server -ukishore@test.org.com mailto:ukishore@test.org.com [root@production2 test.org.com http://test.org.com/]#
=================================
On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding,
mailto:tech@leding.net> wrote: Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say “production1”…I just double-checked as well... FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above…
Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2…
On Jul 27, 2020, at 3:10 PM, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com http://test.org.com/]# doveadm backup -R -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production1.baplc.com mailto:remote%3Avmail@production1.baplc.com vmail@production1.baplc.com mailto:vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: read(vmail@production1.baplc.com mailto:vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com http://production1.baplc.com/ doveadm dsync-server -ukishore@test.org.com mailto:ukishore@test.org.com [root@production2 test.org.com http://test.org.com/]#
=================================
On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding
mailto:tech@leding.net> wrote: Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server… [root at production1 https://dovecot.org/mailman/listinfo/dovecot test.org.com http://test.org.com/]# doveadm backup -R -u kishore at test.org.com https://dovecot.org/mailman/listinfo/dovecot remote:vmail at production2.baplc.com https://dovecot.org/mailman/listinfo/dovecot
...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
Maybe nothing but thought I would mention it…
On Jul 27, 2020, at 2:50 PM, Sami Ketola
mailto:sami.ketola@dovecot.fi> wrote: On 28. Jul 2020, at 0.10, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version 2.2.36.8 (0c9d56b41) [root@ketola ~]# doveadm backup doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Sami
Hey Kishore…
I believe this is the thread I mentioned earlier. It is quite long and spans a monthly barrier (Feb\Mar 2012) so if you use the “Next\Previous message” links, you need to be sure to pick up the thread in each monthly archive. I have provided links to the first post of the thread in each archive here:
https://dovecot.org/list/dovecot/2012-February/133718.html https://dovecot.org/list/dovecot/2012-February/133718.html https://dovecot.org/list/dovecot/2012-March/134110.html https://dovecot.org/list/dovecot/2012-March/134110.html
Also, mention of a working syntax for the remote side command can be found in this post:
https://dovecot.org/list/dovecot/2012-February/081425.html https://dovecot.org/list/dovecot/2012-February/081425.html
I’m sure one of the Dovecot devs will chime in at some point but in the meantime, hopefully the above will offer some relief…
On Jul 27, 2020, at 4:38 PM, Antonio Leding tech@leding.net wrote:
I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side.
Do you have dsync on the 2.0.9 machine?
On Jul 27, 2020, at 4:16 PM, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: This is what my understanding. May be I am also wrong here.
Backup option is there in my new server, production2.
When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same.
Sorry just incase if I am wrong.
Kishore
On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding,
mailto:tech@leding.net> wrote: Well that option set still doesn’t look correct… Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36…
[Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2
[Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
[Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] [-r] <search query> auth cache|test backup [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> batch [-u <user>|-A] [-S ] <sep> <cmd1> [<sep> <cmd2> [..]] config [doveconf parameters] copy [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> director add|dump|flush|map|move|remove|ring|ring|ring|status dump [-t <type>] <path> exec <binary> [binary parameters] expunge [-u <user>|-A] [-S ] [-d] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox mask> fs copy|delete|get|iter|iter-dirs|put|stat help <cmd> import [-u <user>|-A] [-S ] [-s] <source mail location> <dest parent mailbox> <search query> index [-u <user>|-A] [-S ] [-q] [-n <max recent>] <mailbox mask> instance list|remove kick [-a <anvil socket path>] [-f] <user mask>[|] log errors|find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe mount add|list|remove move [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> penalty [-a <anvil socket path>] [ ] proxy kick|list purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] [-V] reload replicator remove|replicate|status search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stats dump|top stop sync [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> user [-a <userdb socket path>] [-x <auth info>] [-f field] [-u] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] zlibconnect <host> [<port>] On Jul 27, 2020, at 3:28 PM, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com http://test.org.com/]# doveadm backup -R -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production1.baplc.com mailto:remote%3Avmail@production1.baplc.com vmail@production1.baplc.com mailto:vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: read(vmail@production1.baplc.com mailto:vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com http://production1.baplc.com/ doveadm dsync-server -ukishore@test.org.com mailto:ukishore@test.org.com [root@production2 test.org.com http://test.org.com/]#
=================================
On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding,
mailto:tech@leding.net> wrote: Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say “production1”…I just double-checked as well... FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above…
Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2…
On Jul 27, 2020, at 3:10 PM, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com http://test.org.com/]# doveadm backup -R -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production1.baplc.com mailto:remote%3Avmail@production1.baplc.com vmail@production1.baplc.com mailto:vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: read(vmail@production1.baplc.com mailto:vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com mailto:kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com http://production1.baplc.com/ doveadm dsync-server -ukishore@test.org.com mailto:ukishore@test.org.com [root@production2 test.org.com http://test.org.com/]#
=================================
On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding
mailto:tech@leding.net> wrote: Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server… [root at production1 https://dovecot.org/mailman/listinfo/dovecot test.org.com http://test.org.com/]# doveadm backup -R -u kishore at test.org.com https://dovecot.org/mailman/listinfo/dovecot remote:vmail at production2.baplc.com https://dovecot.org/mailman/listinfo/dovecot
...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
Maybe nothing but thought I would mention it…
On Jul 27, 2020, at 2:50 PM, Sami Ketola
mailto:sami.ketola@dovecot.fi> wrote: On 28. Jul 2020, at 0.10, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Yes. Please find the details of the servers below. I am executing the command from one of the new servers.
I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm?
2.2.36 has it:
[root@ketola ~]# dovecot --version 2.2.36.8 (0c9d56b41) [root@ketola ~]# doveadm backup doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Sami
Hi!
Kishore, you got the command wrong..
doveadm backup -R -u username-goes-here imapc:
for this to work, you need to configure following things:
imapc_host = old-host-name imapc_password = master-password imapc_master_user = master-user-name
and on the old host you need
passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes }
This should let you pull the mails from the old host to your new host over IMAP.
You should probably also look at
https://wiki.dovecot.org/Migration/Dsync
Aki
On 28/07/2020 03:02 Antonio Leding tech@leding.net wrote:
Hey Kishore…
I believe this is the thread I mentioned earlier. It is quite long and spans a monthly barrier (Feb\Mar 2012) so if you use the “Next\Previous message” links, you need to be sure to pick up the thread in each monthly archive. I have provided links to the first post of the thread in each archive here:
https://dovecot.org/list/dovecot/2012-February/133718.html https://dovecot.org/list/dovecot/2012-March/134110.html
Also, mention of a working syntax for the remote side command can be found in this post:
https://dovecot.org/list/dovecot/2012-February/081425.html
I’m sure one of the Dovecot devs will chime in at some point but in the meantime, hopefully the above will offer some relief…
On Jul 27, 2020, at 4:38 PM, Antonio Leding tech@leding.net wrote:
I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side.
Do you have dsync on the 2.0.9 machine?
On Jul 27, 2020, at 4:16 PM, Kishore Potnuru kishore.reachme@gmail.com wrote:
This is what my understanding. May be I am also wrong here.
Backup option is there in my new server, production2.
When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same.
Sorry just incase if I am wrong.
Kishore
On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, tech@leding.net wrote:
Well that option set still doesn’t look correct…
Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36…
[Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2
[Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
[Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] [-r] <search query> auth cache|test backup [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> batch [-u <user>|-A] [-S ] <sep> <cmd1> [<sep> <cmd2> [..]] config [doveconf parameters] copy [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> director add|dump|flush|map|move|remove|ring|ring|ring|status dump [-t <type>] <path> exec <binary> [binary parameters] expunge [-u <user>|-A] [-S ] [-d] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox mask> fs copy|delete|get|iter|iter-dirs|put|stat help <cmd> import [-u <user>|-A] [-S ] [-s] <source mail location> <dest parent mailbox> <search query> index [-u <user>|-A] [-S ] [-q] [-n <max recent>] <mailbox mask> instance list|remove kick [-a <anvil socket path>] [-f] <user mask>[|] log errors|find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe mount add|list|remove move [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> penalty [-a <anvil socket path>] [ ] proxy kick|list purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] [-V] reload replicator remove|replicate|status search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stats dump|top stop sync [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> user [-a <userdb socket path>] [-x <auth info>] [-f field] [-u] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] zlibconnect <host> [<port>] On Jul 27, 2020, at 3:28 PM, Kishore Potnuru kishore.reachme@gmail.com wrote:
Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's.
The new version is:
[root@production2 ~]# dovecot --version 2.2.36 (1f10bfa63)
The old version is :
[root@production1 ~]# dovecot --version 2.0.9
I have executed the command from the new server:
================================= [root@production2 test.org.com (http://test.org.com/)]# doveadm backup -R -u kishore@test.org.com remote:vmail@production1.baplc.com vmail@production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] dsync-local(kishore@test.org.com): Error: read(vmail@production1.baplc.com) failed: EOF (version not received) dsync-local(kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com (http://production1.baplc.com/) doveadm dsync-server -ukishore@test.org.com [root@production2 test.org.com (http://test.org.com/)]#
=================================
On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding, tech@leding.net wrote:
Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say “production1”…I just double-checked as well...
FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above…
Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2…
> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru kishore.reachme@gmail.com wrote: > > > I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing. > > > The new version is: > ==================== > [root@production2 ~]# dovecot --version > 2.2.36 (1f10bfa63) > > > The old version is : > ====================== > [root@production1 ~]# dovecot --version > 2.0.9 > > > I have executed the command from the new server: > > > > ================================= > [root@production2test.org.com (http://test.org.com/)]# doveadm backup -R -ukishore@test.org.comremote:vmail@production1.baplc.com > vmail@production1.baplc.com's password: > usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] > > altmove [-u <user>|-A] [-S
] <search query> > auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] > config [doveconf parameters] > director add|flush|map|remove|status > dump [-t <type>] <path> > expunge [-u <user>|-A] [-S ] <search query> > fetch [-u <user>|-A] [-S ] <fields> <search query> > force-resync [-u <user>|-A] [-S ] <mailbox> > help <cmd> > import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> > kick [-a <anvil socket path>] [-f] <user mask>[|] > log find|reopen|test > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe > penalty [-a <anvil socket path>] [ ] > purge [-u <user>|-A] [-S ] > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] > reload > search [-u <user>|-A] [-S ] <search query> > sis deduplicate|find > stop > user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] > who [-a <anvil socket path>] [-1] [<user mask>] [ ] > dsync-local(kishore@test.org.com): Error: read(vmail@production1.baplc.com) failed: EOF (version not received) > dsync-local(kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmailproduction1.baplc.com (http://production1.baplc.com/)doveadm dsync-server -ukishore@test.org.com > > [root@production2test.org.com (http://test.org.com/)]# > > ================================= > > > On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding tech@leding.net wrote: > > Not sure if this matters but the prompt when attempting the “doveadm backup” command shows it to be a “production" server… > > > > [root at production1 (https://dovecot.org/mailman/listinfo/dovecot) test.org.com (http://test.org.com/)]# doveadm backup -R -u kishore at test.org.com (https://dovecot.org/mailman/listinfo/dovecot) > > remote:vmail at production2.baplc.com (https://dovecot.org/mailman/listinfo/dovecot) > > > > ...that would seem to me to indicate the old box. If so, then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36 > > > > Maybe nothing but thought I would mention it… > > > > > > > > > > > > > > > On Jul 27, 2020, at 2:50 PM, Sami Ketola sami.ketola@dovecot.fi wrote: > > > > > > > > > > > > > > > > > > > On 28. Jul 2020, at 0.10, Kishore Potnuru kishore.reachme@gmail.com wrote: > > > > > > > > Yes. Please find the details of the servers below. I am executing the command from one of the new servers. > > > > > > I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm? > > > > > > 2.2.36 has it: > > > > > > [root@ketola ~]# dovecot --version > > > 2.2.36.8 (0c9d56b41) > > > [root@ketola ~]# doveadm backup > > > doveadm backup [-u <user>|-A] [-S ] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> > > > > > > > > > Sami
Hi,
I have tried the same way as per your suggestion. But it's throwing the below error.
[root@production2 log]# doveadm backup -a All -R -u kishore@test.ba.com imapc: dsync(kishore@test.ba.com): Info: imapc(production1.baplc.com:143): Connected to 161.2.11.119:143 (local 161.2.12.152:45992) dsync(kishore@test.ba.com): Warning: imapc(production1.baplc.com:143): connect(161.2.11.119, 143) timed out after 30 seconds - reconnecting (delay 0 ms) dsync(kishore@test.ba.com): Info: imapc(production1.baplc.com:143): Connected to 161.2.11.119:143 (local 161.2.12.152:46014) dsync(kishore@test.ba.com): Error: imapc(production1.baplc.com:143): connect(161.2.11.119, 143) timed out after 30 seconds - disconnecting dsync(kishore@test.ba.com): Error: User initialization failed: imapc: Login to production1.baplc.com failed: Disconnected from server [root@production2 log]#
I looked into the production1 (old server) logs. I see the below error.
=============== Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there are no passdbs Jul 28 11:14:23 master: Error: service(auth): command startup failed, throttling
After the above error, I have commented "pass=yes" in production1 (old server) server, then I see the below error.
================ Jul 28 11:17:10 auth: Fatal: No passdbs specified in configuration file. PLAIN mechanism needs one Jul 28 11:17:10 master: Error: service(auth): command startup failed, throttling
Please suggest me on fixing the issue. I have also copied the dovecot.conf from both the servers below.
========================================= My old server dovecot.conf (production1):
disable_plaintext_auth = no
listen = * log_path = /var/log/dovecot.log mail_location = maildir:/z1dev/mail/virtual/%d/%n/Maildir/ passdb { args = /etc/dovecot/passwd driver = passwd-file master = yes pass = yes } pop3_uidl_format = %g protocols = pop3 imap ssl = yes ssl_cert =
userdb { args = uid=vmail gid=vmail home=/z1dev/mail/virtual/%d/%n driver = static } mail_debug = no verbose_ssl = no
========================================= My New server dovecot.conf(production2):
disable_plaintext_auth = no
listen = * log_path = /var/log/dovecot.log
mail_location = maildir:/z1devenv/mail/virtual/%d/%n/Maildir/
passdb { args = /etc/dovecot/passwd driver = passwd-file }
pop3_uidl_format = %g protocols = pop3 imap
ssl = yes ssl_cert =
userdb { args = uid=vmail gid=vmail home=/z1devenv/mail/virtual/%d/%n driver = static }
mail_debug = yes verbose_ssl = no
# Enable the replication plugin globally mail_plugins = $mail_plugins notify replication
service replicator { process_min_avail = 1 }
dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u plugin { mail_replica = remote:vmail@production3.baplc.com }
service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } }
service replicator { unix_listener replicator-doveadm { mode = 0600 user = vmail } }
replication_max_conns = 10
imapc_host = production1.baplc.com imapc_password = vmail imapc_master_user = vmail imapc_user = %u
===================================
Please suggest me.
Thanks & Regards, Kishore
On Tue, Jul 28, 2020 at 6:57 AM Aki Tuomi aki.tuomi@open-xchange.com wrote:
Hi!
Kishore, you got the command wrong..
doveadm backup -R -u username-goes-here imapc:
for this to work, you need to configure following things:
imapc_host = old-host-name imapc_password = master-password imapc_master_user = master-user-name
and on the old host you need
passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes }
This should let you pull the mails from the old host to your new host over IMAP.
You should probably also look at
https://wiki.dovecot.org/Migration/Dsync
Aki
On 28/07/2020 03:02 Antonio Leding tech@leding.net wrote:
Hey Kishore…
I believe this is the thread I mentioned earlier. It is quite long and spans a monthly barrier (Feb\Mar 2012) so if you use the “Next\Previous message” links, you need to be sure to pick up the thread in each monthly archive. I have provided links to the first post of the thread in each archive here:
https://dovecot.org/list/dovecot/2012-February/133718.html https://dovecot.org/list/dovecot/2012-March/134110.html
Also, mention of a working syntax for the remote side command can be found in this post:
https://dovecot.org/list/dovecot/2012-February/081425.html
I’m sure one of the Dovecot devs will chime in at some point but in the meantime, hopefully the above will offer some relief…
On Jul 27, 2020, at 4:38 PM, Antonio Leding tech@leding.net wrote:
I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side.
Do you have dsync on the 2.0.9 machine?
On Jul 27, 2020, at 4:16 PM, Kishore Potnuru < kishore.reachme@gmail.com> wrote:
This is what my understanding. May be I am also wrong here.
Backup option is there in my new server, production2.
When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same.
Sorry just incase if I am wrong.
Kishore
Well that option set still doesn’t look correct…
Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36…
[Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2
[Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
[Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] [-r] <search query> auth cache|test backup [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> batch [-u <user>|-A] [-S ] <sep> <cmd1> [<sep> <cmd2> [..]] config [doveconf parameters] copy [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> director add|dump|flush|map|move|remove|ring|ring|ring|status dump [-t <type>] <path> exec <binary> [binary parameters] expunge [-u <user>|-A] [-S ] [-d] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox mask> fs copy|delete|get|iter|iter-dirs|put|stat help <cmd> import [-u <user>|-A] [-S ] [-s] <source mail location> <dest parent mailbox> <search query> index [-u <user>|-A] [-S ] [-q] [-n <max recent>] <mailbox mask> instance list|remove kick [-a <anvil socket path>] [-f] <user mask>[|] log errors|find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe mount add|list|remove move [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> penalty [-a <anvil socket path>] [ ] proxy kick|list purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] [-V] reload replicator remove|replicate|status search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stats dump|top stop sync [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> user [-a <userdb socket path>] [-x <auth info>] [-f field] [-u] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] zlibconnect <host> [<port>] On Jul 27, 2020, at 3:28 PM, Kishore Potnuru < kishore.reachme@gmail.com> wrote:
Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's.
> The new version is: > ==================== > [root@production2 ~]# dovecot --version > 2.2.36 (1f10bfa63) > > > The old version is : > ====================== > [root@production1 ~]# dovecot --version > 2.0.9 > > > I have executed the command from the new server: > > > > ================================= > [root@production2 test.org.com (http://test.org.com/)]# doveadm backup -R -u kishore@test.org.com remote:vmail@production1.baplc.com > vmail@production1.baplc.com's password: > usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] > > altmove [-u <user>|-A] [-S
] <search query> > auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] > config [doveconf parameters] > director add|flush|map|remove|status > dump [-t <type>] <path> > expunge [-u <user>|-A] [-S ] <search query> > fetch [-u <user>|-A] [-S ] <fields> <search query> > force-resync [-u <user>|-A] [-S ] <mailbox> > help <cmd> > import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> > kick [-a <anvil socket path>] [-f] <user mask>[|] > log find|reopen|test > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe > penalty [-a <anvil socket path>] [ ] > purge [-u <user>|-A] [-S ] > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] > reload > search [-u <user>|-A] [-S ] <search query> > sis deduplicate|find > stop > user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] > who [-a <anvil socket path>] [-1] [<user mask>] [ ] > dsync-local(kishore@test.org.com): Error: read( vmail@production1.baplc.com) failed: EOF (version not received) > dsync-local(kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com ( http://production1.baplc.com/) doveadm dsync-server -ukishore@test.org.com > > [root@production2 test.org.com (http://test.org.com/)]# > > ================================= On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding, tech@leding.net wrote: > Fair enough but the command snippet I posted was taken
> > FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above… > > Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2… > > > > > > > > > > > On Jul 27, 2020, at 3:10 PM, Kishore Potnuru < kishore.reachme@gmail.com> wrote: > > > > > > I am executing the command from the new server. I was executing the command from production2 server only. It has the backup
> > > > > > The new version is: > > ==================== > > [root@production2 ~]# dovecot --version > > 2.2.36 (1f10bfa63) > > > > > > The old version is : > > ====================== > > [root@production1 ~]# dovecot --version > > 2.0.9 > > > > > > I have executed the command from the new server: > > > > > > > > ================================= > > [root@production2test.org.com (http://test.org.com/)]# doveadm backup -R -ukishore@test.org.comremote:vmail@production1.baplc.com > > vmail@production1.baplc.com's password: > > usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] > > > > altmove [-u <user>|-A] [-S
] <search query> > > auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] > > config [doveconf parameters] > > director add|flush|map|remove|status > > dump [-t <type>] <path> > > expunge [-u <user>|-A] [-S ] <search query> > > fetch [-u <user>|-A] [-S ] <fields> <search query> > > force-resync [-u <user>|-A] [-S ] <mailbox> > > help <cmd> > > import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> > > kick [-a <anvil socket path>] [-f] <user mask>[|] > > log find|reopen|test > > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe > > penalty [-a <anvil socket path>] [ ] > > purge [-u <user>|-A] [-S ] > > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] > > reload > > search [-u <user>|-A] [-S ] <search query> > > sis deduplicate|find > > stop > > user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] > > who [-a <anvil socket path>] [-1] [<user mask>] [ ] > > dsync-local(kishore@test.org.com): Error: read( vmail@production1.baplc.com) failed: EOF (version not received) > > dsync-local(kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmailproduction1.baplc.com ( http://production1.baplc.com/)doveadm dsync-server -ukishore@test.org.com > > > > [root@production2test.org.com (http://test.org.com/)]# > > > > ================================= > > > > > > On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding < tech@leding.net> wrote: > > > Not sure if this matters but the prompt when attempting > > > > > > [root at production1 ( https://dovecot.org/mailman/listinfo/dovecot) test.org.com ( http://test.org.com/)]# doveadm backup -R -u kishore at test.org.com ( https://dovecot.org/mailman/listinfo/dovecot) > > > remote:vmail at production2.baplc.com ( https://dovecot.org/mailman/listinfo/dovecot) > > > > > > ...that would seem to me to indicate the old box. If so,
On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, tech@leding.net wrote: directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say “production1”…I just double-checked as well... option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing. the “doveadm backup” command shows it to be a “production" server… then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
> > > > > > Maybe nothing but thought I would mention it… > > > > > > > > > > > > > > > > > > > > > > On Jul 27, 2020, at 2:50 PM, Sami Ketola < sami.ketola@dovecot.fi> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > On 28. Jul 2020, at 0.10, Kishore Potnuru < kishore.reachme@gmail.com> wrote: > > > > > > > > > > Yes. Please find the details of the servers below. I am executing the command from one of the new servers. > > > > > > > > I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm? > > > > > > > > 2.2.36 has it: > > > > > > > > [root@ketola ~]# dovecot --version > > > > 2.2.36.8 (0c9d56b41) > > > > [root@ketola ~]# doveadm backup > > > > doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> > > > > > > > > > > > > Sami
Hi,
I have tried the same way as per your suggestion. But it's throwing an error.
[root@production2 log]# doveadm backup -a All -R -u kishore@test.ba.com imapc: dsync(kishore@test.ba.com): Info: imapc(production1.baplc.com:143): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992) dsync(kishore@test.ba.com): Warning: imapc(production1.baplc.com:143): connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - reconnecting (delay 0 ms) dsync(kishore@test.ba.com): Info: imapc(production1.baplc.com:143): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:46014) dsync(kishore@test.ba.com): Error: imapc(production1.baplc.com:143): connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - disconnecting dsync(kishore@test.ba.com): Error: User initialization failed: imapc: Login to production1.baplc.com failed: Disconnected from server [root@production2 log]#
I looked into the production1 (old server) logs. I see the below error.
=============== Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there are no passdbs Jul 28 11:14:23 master: Error: service(auth): command startup failed, throttling
after the above error, I have commented "pass=yes" in production1 (old server) server, then I see the below error.
================ Jul 28 11:17:10 auth: Fatal: No passdbs specified in configuration file. PLAIN mechanism needs one Jul 28 11:17:10 master: Error: service(auth): command startup failed, throttling
Please suggest me on fixing the issue.
On Tue, Jul 28, 2020 at 6:57 AM Aki Tuomi aki.tuomi@open-xchange.com wrote:
Hi!
Kishore, you got the command wrong..
doveadm backup -R -u username-goes-here imapc:
for this to work, you need to configure following things:
imapc_host = old-host-name imapc_password = master-password imapc_master_user = master-user-name
and on the old host you need
passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes }
This should let you pull the mails from the old host to your new host over IMAP.
You should probably also look at
https://wiki.dovecot.org/Migration/Dsync
Aki
On 28/07/2020 03:02 Antonio Leding tech@leding.net wrote:
Hey Kishore…
I believe this is the thread I mentioned earlier. It is quite long and spans a monthly barrier (Feb\Mar 2012) so if you use the “Next\Previous message” links, you need to be sure to pick up the thread in each monthly archive. I have provided links to the first post of the thread in each archive here:
https://dovecot.org/list/dovecot/2012-February/133718.html https://dovecot.org/list/dovecot/2012-March/134110.html
Also, mention of a working syntax for the remote side command can be found in this post:
https://dovecot.org/list/dovecot/2012-February/081425.html
I’m sure one of the Dovecot devs will chime in at some point but in the meantime, hopefully the above will offer some relief…
On Jul 27, 2020, at 4:38 PM, Antonio Leding tech@leding.net wrote:
I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side.
Do you have dsync on the 2.0.9 machine?
On Jul 27, 2020, at 4:16 PM, Kishore Potnuru < kishore.reachme@gmail.com> wrote:
This is what my understanding. May be I am also wrong here.
Backup option is there in my new server, production2.
When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same.
Sorry just incase if I am wrong.
Kishore
Well that option set still doesn’t look correct…
Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36…
[Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2
[Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
[Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] [-r] <search query> auth cache|test backup [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> batch [-u <user>|-A] [-S ] <sep> <cmd1> [<sep> <cmd2> [..]] config [doveconf parameters] copy [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> director add|dump|flush|map|move|remove|ring|ring|ring|status dump [-t <type>] <path> exec <binary> [binary parameters] expunge [-u <user>|-A] [-S ] [-d] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox mask> fs copy|delete|get|iter|iter-dirs|put|stat help <cmd> import [-u <user>|-A] [-S ] [-s] <source mail location> <dest parent mailbox> <search query> index [-u <user>|-A] [-S ] [-q] [-n <max recent>] <mailbox mask> instance list|remove kick [-a <anvil socket path>] [-f] <user mask>[|] log errors|find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe mount add|list|remove move [-u <user>|-A] [-S ] <destination> [user <source user>] <search query> penalty [-a <anvil socket path>] [ ] proxy kick|list purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] [-V] reload replicator remove|replicate|status search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stats dump|top stop sync [-u <user>|-A] [-S ] [-dfR] [-l <secs>] [-m <mailbox>] [-n <namespace>] [-s <state>] <dest> user [-a <userdb socket path>] [-x <auth info>] [-f field] [-u] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] zlibconnect <host> [<port>] On Jul 27, 2020, at 3:28 PM, Kishore Potnuru < kishore.reachme@gmail.com> wrote:
Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's.
> The new version is: > ==================== > [root@production2 ~]# dovecot --version > 2.2.36 (1f10bfa63) > > > The old version is : > ====================== > [root@production1 ~]# dovecot --version > 2.0.9 > > > I have executed the command from the new server: > > > > ================================= > [root@production2 test.org.com (http://test.org.com/)]# doveadm backup -R -u kishore@test.org.com remote:vmail@production1.baplc.com > vmail@production1.baplc.com's password: > usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] > > altmove [-u <user>|-A] [-S
] <search query> > auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] > config [doveconf parameters] > director add|flush|map|remove|status > dump [-t <type>] <path> > expunge [-u <user>|-A] [-S ] <search query> > fetch [-u <user>|-A] [-S ] <fields> <search query> > force-resync [-u <user>|-A] [-S ] <mailbox> > help <cmd> > import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> > kick [-a <anvil socket path>] [-f] <user mask>[|] > log find|reopen|test > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe > penalty [-a <anvil socket path>] [ ] > purge [-u <user>|-A] [-S ] > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] > reload > search [-u <user>|-A] [-S ] <search query> > sis deduplicate|find > stop > user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] > who [-a <anvil socket path>] [-1] [<user mask>] [ ] > dsync-local(kishore@test.org.com): Error: read( vmail@production1.baplc.com) failed: EOF (version not received) > dsync-local(kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmail production1.baplc.com ( http://production1.baplc.com/) doveadm dsync-server -ukishore@test.org.com > > [root@production2 test.org.com (http://test.org.com/)]# > > ================================= On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding, tech@leding.net wrote: > Fair enough but the command snippet I posted was taken
> > FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above… > > Here you appear to be exec’ing the command on prod2 and trying to pull from the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the remote of prod2… > > > > > > > > > > > On Jul 27, 2020, at 3:10 PM, Kishore Potnuru < kishore.reachme@gmail.com> wrote: > > > > > > I am executing the command from the new server. I was executing the command from production2 server only. It has the backup
> > > > > > The new version is: > > ==================== > > [root@production2 ~]# dovecot --version > > 2.2.36 (1f10bfa63) > > > > > > The old version is : > > ====================== > > [root@production1 ~]# dovecot --version > > 2.0.9 > > > > > > I have executed the command from the new server: > > > > > > > > ================================= > > [root@production2test.org.com (http://test.org.com/)]# doveadm backup -R -ukishore@test.org.comremote:vmail@production1.baplc.com > > vmail@production1.baplc.com's password: > > usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] > > > > altmove [-u <user>|-A] [-S
] <search query> > > auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] > > config [doveconf parameters] > > director add|flush|map|remove|status > > dump [-t <type>] <path> > > expunge [-u <user>|-A] [-S ] <search query> > > fetch [-u <user>|-A] [-S ] <fields> <search query> > > force-resync [-u <user>|-A] [-S ] <mailbox> > > help <cmd> > > import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> > > kick [-a <anvil socket path>] [-f] <user mask>[|] > > log find|reopen|test > > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe > > penalty [-a <anvil socket path>] [ ] > > purge [-u <user>|-A] [-S ] > > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] > > reload > > search [-u <user>|-A] [-S ] <search query> > > sis deduplicate|find > > stop > > user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] > > who [-a <anvil socket path>] [-1] [<user mask>] [ ] > > dsync-local(kishore@test.org.com): Error: read( vmail@production1.baplc.com) failed: EOF (version not received) > > dsync-local(kishore@test.org.com): Error: Remote command returned error 1: ssh -lvmailproduction1.baplc.com ( http://production1.baplc.com/)doveadm dsync-server -ukishore@test.org.com > > > > [root@production2test.org.com (http://test.org.com/)]# > > > > ================================= > > > > > > On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding < tech@leding.net> wrote: > > > Not sure if this matters but the prompt when attempting > > > > > > [root at production1 ( https://dovecot.org/mailman/listinfo/dovecot) test.org.com ( http://test.org.com/)]# doveadm backup -R -u kishore at test.org.com ( https://dovecot.org/mailman/listinfo/dovecot) > > > remote:vmail at production2.baplc.com ( https://dovecot.org/mailman/listinfo/dovecot) > > > > > > ...that would seem to me to indicate the old box. If so,
On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, tech@leding.net wrote: directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say “production1”…I just double-checked as well... option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing. the “doveadm backup” command shows it to be a “production" server… then per Kishore’s earlier posts, the machine where this is being attempted is running 2.0.9…not 2.2.36
> > > > > > Maybe nothing but thought I would mention it… > > > > > > > > > > > > > > > > > > > > > > On Jul 27, 2020, at 2:50 PM, Sami Ketola < sami.ketola@dovecot.fi> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > On 28. Jul 2020, at 0.10, Kishore Potnuru < kishore.reachme@gmail.com> wrote: > > > > > > > > > > Yes. Please find the details of the servers below. I am executing the command from one of the new servers. > > > > > > > > I find it very hard to believe this. Shall I look at the version control when backup was added as option to doveadm? > > > > > > > > 2.2.36 has it: > > > > > > > > [root@ketola ~]# dovecot --version > > > > 2.2.36.8 (0c9d56b41) > > > > [root@ketola ~]# doveadm backup > > > > doveadm backup [-u <user>|-A] [-S
] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g ] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> > > > > > > > > > > > > Sami
On Jul 27, 2020, at 4:59 AM, Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi
I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
I recently did a similar move
What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not.
Step 0.
Setup replication and have mail replicate from the old servers to the new servers.
- Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
I stopped Postfix on the old servers and did not start Postfix on the new servers. I waited until I saw that no mail was replicating from the old Dovecot to the new servers.
- copy/migrate the data from old server to new servers. Please suggest what is the best way?
Using the replication mechanism was the best method for me.
I tried this command also. It didn't work. It shows syntax again. Please see the supported commands in dovecot 2.0.9 version. This doesn't support replication also as per syntax, if i am not wrong. Please suggest me.
[root@production ~]# doveadm backup -u kishore@test.org.com remote:vmail@production2.test.org.com usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
On Mon, Jul 27, 2020 at 2:22 PM Admin dishaw.org admin@dishaw.org wrote:
On Jul 27, 2020, at 4:59 AM, Kishore Potnuru kishore.reachme@gmail.com wrote:
Hi
I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
I recently did a similar move
What is the best way to stop/copy/migrate the current production data to
the new servers? I am planning the following steps. Not sure if it is correct or not.
Step 0.
Setup replication and have mail replicate from the old servers to the new servers.
- Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
I stopped Postfix on the old servers and did not start Postfix on the new servers. I waited until I saw that no mail was replicating from the old Dovecot to the new servers.
- copy/migrate the data from old server to new servers. Please suggest what is the best way?
Using the replication mechanism was the best method for me.
On Jul 27, 2020, at 10:13 AM, Kishore Potnuru kishore.reachme@gmail.com wrote:
I tried this command also. It didn't work. It shows syntax again. Please see the supported commands in dovecot 2.0.9 version. This doesn't support replication also as per syntax, if i am not wrong. Please suggest me.
[root@production ~]# doveadm backup -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production2.test.org.com mailto:remote%3Avmail@production2.test.org.com
I’ve only used the tcps destination, not the remote. I don’t have 2.0.x on any machines, so I can’t test—have you checked the man page (man doveadm-backup)? To the best of my knowledge, Dsync existed in 2.0.x.
If you setup tcps, make sure you create a CA and certificates for the two servers. If you don’t want to do that and want to use tcp, either do that on a local network or tunnel the connection through SSH.
On Mon, Jul 27, 2020 at 2:22 PM Admin dishaw.org http://dishaw.org/
mailto:admin@dishaw.org> wrote: On Jul 27, 2020, at 4:59 AM, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Hi
I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
I recently did a similar move
What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not.
Step 0.
Setup replication and have mail replicate from the old servers to the new servers.
- Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
I stopped Postfix on the old servers and did not start Postfix on the new servers. I waited until I saw that no mail was replicating from the old Dovecot to the new servers.
- copy/migrate the data from old server to new servers. Please suggest what is the best way?
Using the replication mechanism was the best method for me.
Hi,
the idea was to run it on the new server and not on the old server. That is also why you should use -R parameter to pull the mails from remote, not push.
Sami
On 27. Jul 2020, at 17.13, Kishore Potnuru kishore.reachme@gmail.com wrote:
I tried this command also. It didn't work. It shows syntax again. Please see the supported commands in dovecot 2.0.9 version. This doesn't support replication also as per syntax, if i am not wrong. Please suggest me.
[root@production ~]# doveadm backup -u kishore@test.org.com mailto:kishore@test.org.com remote:vmail@production2.test.org.com mailto:remote%3Avmail@production2.test.org.com usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]
altmove [-u <user>|-A] [-S
] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S ] <search query> fetch [-u <user>|-A] [-S ] <fields> <search query> force-resync [-u <user>|-A] [-S ] <mailbox> help <cmd> import [-u <user>|-A] [-S ] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|] log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [ ] purge [-u <user>|-A] [-S ] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S ] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [ ] On Mon, Jul 27, 2020 at 2:22 PM Admin dishaw.org http://dishaw.org/
mailto:admin@dishaw.org> wrote: On Jul 27, 2020, at 4:59 AM, Kishore Potnuru
mailto:kishore.reachme@gmail.com> wrote: Hi
I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
I recently did a similar move
What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not.
Step 0.
Setup replication and have mail replicate from the old servers to the new servers.
- Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
I stopped Postfix on the old servers and did not start Postfix on the new servers. I waited until I saw that no mail was replicating from the old Dovecot to the new servers.
- copy/migrate the data from old server to new servers. Please suggest what is the best way?
Using the replication mechanism was the best method for me.
participants (5)
-
Admin dishaw.org
-
Aki Tuomi
-
Antonio Leding
-
Kishore Potnuru
-
Sami Ketola