search for: production2

...ull 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 at 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: > =...

...] [<ip/bits>] zlibconnect <host> [<port>] > On Jul 27, 2020, at 3:28 PM, Kishore Potnuru <kishore.reachme at 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 at production2 ~]# dovecot --version > 2.2.36 (1f10bfa63) > > > The old version is : > ====================== > [root at production1 ~]# d...

...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,...

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 at production2 ~]# dovecot --version 2.2.36 (1f10bfa63) The old version is : ====================== [root at production1 ~]# dovecot --version 2.0.9 I have executed the comman...

...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 at 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 wron...

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, 2...

...> > > > > > On Jul 27, 2020, at 4:16 PM, Kishore Potnuru <kishore.reachme at 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. > > > > &g...

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: ====================...

...> > > >> On Jul 27, 2020, at 4:16 PM, Kishore Potnuru <kishore.reachme at gmail.com <mailto:kishore.reachme at 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 inc...

Hi All, I have tried the below command to migrate the data from the old server(dovecot version: 2.0.9) to new servers(dovecot version: 2.2.36 (1f10bfa63)). But it's throwing an error. old server name: production1 new server1 name: production2 (for HA/Replication) new server2 name: production3 (for HA/Replication) I have configured replication between production2 and production3, which is working fine. The issue is, the below command I am trying is from production2 server and trying to take the data from production1 server. ---------...

Hi Aki & Dovecot team, Just continuing with the previous discussion "Migration from one server to 2 new servers". Hi, I have tried the same way as per your suggestion. But it's throwing an error. ------------- [root at production2 log]# doveadm backup -a All -R -u kishore at test.ba.com imapc: dsync(kishore at test.ba.com): Info: imapc(production1.baplc.com:143): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992) dsync(kishore at test.ba.com): Warning: imapc(production1.baplc.com:143): connect(xxx.xxx.xxx.xxx, 1...

...;/etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem 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 =...

.... rest all i kept the same. passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes #pass = yes } passdb { driver = passwd-file args = username_format=%u /etc/dovecot/passwd } Now I am getting the below Authentication error from production2. Seems I have made some mistake. ----- [root at production2 dovecot]# doveadm backup -a All -R -u kishore at test.testorg.com imapc: dsync(kishore at test.testorg.com): Info: imapc(production1.testorg.com:143): Connected to 161.2.11.119:143 (local xxx.xxx.xxx.xxx:39200) dsync(kishore at test.testo...

...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 at production ~]# doveadm backup -u kishore at test.org.com remote:vmail at production2.test.org.com usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] altmove [-u <user>|-A] [-S <socket_path>] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf par...

Thank you for the response. So, both password files (master and regular user credentials) have the same contents in this scenario, correct? -Kishore On Mon, Aug 3, 2020 at 11:42 PM Joseph Tam <jtam.home at gmail.com> wrote: > On Mon, 3 Aug 2020, Kishore Potnuru wrote: > > > =============== > > Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there

...e: > > Hi Aki & Dovecot team, > > Just continuing with the previous discussion "Migration from one server to 2 new servers". > > Hi, > > I have tried the same way as per your suggestion. But it's throwing an error. > > ------------- > [root at production2 log]# doveadm backup -a All -R -u kishore at test.ba.com <mailto:kishore at test.ba.com> imapc: > dsync(kishore at test.ba.com <mailto:kishore at test.ba.com>): Info: imapc(production1.baplc.com:143 <http://production1.baplc.com:143/>): Connected to xxx.xxx.xxx.xxx:143 (local y...

...know if you need any other details. please provide the following outputs/answers: 1) Are users able to login and access their mailboxes on production1 with an IMAP client? On your old server (production1): 2) ps aux | grep dovecot 3) netstat -lntp 4) ls -la /etc/dovecot On your new server (production2): 5) telnet production1.testorg.com 143 Thanks and regards Markus

...sticky sessions. They told me that files in the first server will be replicated during the night to the secondary. I still have my old Capistrano recipe to be updated. I thought I can create two different environments, one for the first server, one for the second one, something like production1 and production2; what do you think about it? Do you have any suggestion or advice? Why sticky sessions? I wasn''t my choice. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39U...

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

Like most, I have a test and a production env. Both are CentOS 5, Ruby 1.8.6, Rails 2.0.2, MySQL 5, and Apache. Both were setup using the same procedure. Except for the hardware (test: Intel, prod: AMD) and memory (test: 512M, prod: 1G), both systems are essentially the same right down to the Rails env. Unfortunately, memory usage is very different for each. The test system has 2 mongrel