'=?utf-8?q?Re=3A?= Cyrus Murder Environment Upgrade'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: cyrus-info
Subject: =?utf-8?q?Re=3A?= Cyrus Murder Environment Upgrade
From: "Miguel Mucio Santos Moreira" <miguel () prodemge ! gov ! br>
Date: 2020-06-10 18:47:38
Message-ID: 930-5ee12b00-3-6abd6400 () 207816469
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Wolfgang,

If you don't mind, I'd like to know if when you upgraded backend server=
s from 2.4 version to 2.5 version you have an increase, in metadata siz=
e.Here we had 30% around of increase

Thanks one more time

Greetings
--

Miguel Moreira
DTE/SRE/GRE - Ger=C3=AAncia de Redes
+55(31)3339-1401
PRODEMGE - Companhia de Tecnologia da Informa=C3=A7=C3=A3o do Estado de=
 Minas Gerais

Aviso: Esta mensagem =C3=A9 destinada exclusivamente para a(s) pessoa(s=
) a quem =C3=A9 dirigida, podendo conter informa=C3=A7=C3=A3o sigilosa =
e legalmente protegida. O uso impr=C3=B3prio ser=C3=A1 tratado conforme=
 as normas da empresa e a legisla=C3=A7=C3=A3o em vigor. Caso n=C3=A3o =
seja o destinat=C3=A1rio, favor notificar o remetente, ficando proibida=
s a utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o, c=C3=B3pia e distribui=C3=
=A7=C3=A3o. Em Ter=C3=A7a, Junho 09, 2020 10:39 -03, Wolfgang Breyha <w=
breyha@gmx.net> escreveu:Hi!

On 09/06/2020 14:56, Miguel Mucio Santos Moreira wrote:
> Dear Wolfgang,
>
> Firstly thanks for your answer, secondly I have one more doubt, durin=
g this
> time where the new Mupdate Master is receiving mailboxes information =
from
> backend servers, is necessary stopping comunications between frontend=

> servers and mupdate master or none action is necessary besides that o=
ne
> you've mentioned before?
> We're concerned if frontend servers will connect to Mupdate Master an=
d
> receive from it an information which there's no mailboxes anymore unt=
il the
> backend push entirely mailboxes information and this situation to cau=
se any
> trouble.

I recommend the follow steps:
*) check that your currently running setup has no conflicts in mailboxe=
s.db
by running "ctl=5Fmboxlist -mw". It is possible that you see output if
somebody changes his mailboxes while you run the command, but it should=

not appear again if you run the command a second time. If everything is=

fine...

*) shut down all running cyrus
frontends first, then backends and mupdate last
*) backup your mailboxes.db on mupdate server
*) replace/update mupdate and start it with empty/removed mailboxes.db.=

*) backup your mailboxes.db on the backends
*) do the ctl=5Fmboxlist -m by hand on the backends (only one at the sa=
me
time) you can check if everything went ok with "-mw" at any time
afterwards.
*) start cyrus on backends

In our setup the frontends have mupdate running as well. I can't curren=
tly
remember if this is mandatory. If this is true in your setup then:
*) remove or rename the mailboxes.db database on the frontends and star=
t
them. They will fetch the database immediately from the mupdate server.=

This is visible in syslog as well and takes about 30 seconds in our
setup (~250MB mailboxes.db).
otherwise
*) start the frontends

At this point everything should be up and running again.

Watching syslog output all the time usually helps.

IIRC we updated the mupdate server to 2.5 first. Then we had a mix of 2=
.4
and 2.5 backends for some time. The 2.5 backends had some capabilities
suppressed. Frontends had 2.4 until all backends had 2.5. Last but not
least we upgraded to 2.5 on the frontends.

If you need more info/details feel free to ask.

Greetings, Wolfgang
--
Wolfgang Breyha <wbreyha@gmx.net> | https://www.blafasel.at/
Vienna University Computer Center | Austria

[Attachment #5 (text/html)]

<html>Wolfgang, If you don't mind, I'd like to know if when you upgraded \
backend servers from 2.4 version to 2.5 version you have an increase, in metadata \
size.Here we had 30% around of increase Thanks one more time Greetings -- Miguel Moreira DTE/SRE/GRE - Gerência de Redes +55(31)3339-1401 PRODEMGE - \
Companhia de Tecnologia da Informação do Estado de Minas Gerais Aviso: Esta mensagem é destinada exclusivamente para a(s) \
pessoa(s) a quem é dirigida, podendo conter informação sigilosa e legalmente \
protegida. O uso impróprio será tratado conforme as normas da empresa e a \
legislação em vigor. Caso não seja o destinatário, favor notificar o remetente, \
ficando proibidas a utilização, divulgação, cópia e distribuição. Em \
Terça, Junho 09, 2020 10:39 -03, Wolfgang Breyha &lt;wbreyha@gmx.net&gt; \
escreveu:<blockquote type="cite" \
cite="40e951d9-111a-e811-2a51-073413633d52@gmx.net">Hi! On 09/06/2020 \
14:56, Miguel Mucio Santos Moreira wrote: &gt; Dear Wolfgang, &gt; &gt; Firstly thanks for your answer, secondly I have one more doubt, during this &gt; time where the new Mupdate Master is receiving mailboxes information from &gt; backend servers, is necessary stopping comunications between frontend &gt; servers and mupdate master or none action is necessary besides that one &gt; you've mentioned before? &gt; We're concerned if frontend servers will \
connect to Mupdate Master and &gt; receive from it an information which there's \
no mailboxes anymore until the &gt; backend push entirely mailboxes information \
and this situation to cause any &gt; trouble. I recommend the follow \
steps: *) check that your currently running setup has no conflicts in \
mailboxes.db by running "ctl_mboxlist -mw". It is possible that you see output \
if somebody changes his mailboxes while you run the command, but it should not appear again if you run the command a second time. If everything is fine... *) shut down all running cyrus frontends first, then \
backends and mupdate last *) backup your mailboxes.db on mupdate server *) \
replace/update mupdate and start it with empty/removed mailboxes.db. *) backup \
your mailboxes.db on the backends *) do the ctl_mboxlist -m by hand on the \
backends (only one at the same time) you can check if everything went ok with \
"-mw" at any time afterwards. *) start cyrus on backends In our \
setup the frontends have mupdate running as well. I can't currently remember if \
this is mandatory. If this is true in your setup then: *) remove or rename the \
mailboxes.db database on the frontends and start them. They will fetch the \
database immediately from the mupdate server. This is visible in syslog as well \
and takes about 30 seconds in our setup (~250MB mailboxes.db). otherwise *) start the frontends At this point everything should be up and running \
again. Watching syslog output all the time usually helps. IIRC \
we updated the mupdate server to 2.5 first. Then we had a mix of 2.4 and 2.5 \
backends for some time. The 2.5 backends had some capabilities suppressed. \
Frontends had 2.4 until all backends had 2.5. Last but not least we upgraded to \
2.5 on the frontends. If you need more info/details feel free to ask. Greetings, Wolfgang -- Wolfgang Breyha &lt;wbreyha@gmx.net&gt; | \
https://www.blafasel.at/ Vienna University Computer Center | \
Austria</blockquote></html>

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

[prev in list] [next in list] [prev in thread] [next in thread] 