Hi again!
Else as a simplication way can you replicate any manner a 2.3 with some
newer version?. At least in manual mode (not rolling)?.
Cheers.
---
EGOITZ AURREKOETXEA
Departamento de sistemas
944 209 470
Parque Tecnológico. Edificio 103
48170 Zamudio (Bizkaia)
ego...@sarenet.es
Good afternoon,
I was trying to upgrade part of our Cyrus imap installation, concretely
that one consisting in still 2.3. I was planning to set up Cyrus 3.0. I
have seen all works properly except for the unexpunge command because as
someone stated here, a reconstruct -V max was needed.The
Jonk, thank you for the idea. Somewhat looks strange as old mail server
worked w/o this problem 5+ years. But the system environment changed
dramatically, may be some filesystem quircks are significant for this
locks...
I will try gdb'ing the process when problem occurs once more
13.12.2018
Without running gdb on the process, I have no idea, but your problem
sounds similar to something we hit a very long time ago:
See https://www.oakton.edu/user/3/jwade/cyrus/Readme.html
In our cases, the problem was the imapd process that was holding the
lock was trying to obtain a second lock
Hi,
we moved from an old cyrus system to a newer one (2.14.19)
~18 months ago. The system runs very smooth. However I noticed
a couple of problems:
1) We are creating a user using a script. The script is executing
on the mail system some commands to create the mailboxes and the aliases.
I found
Hello
We had a company mail server under Oracle Linux 6 (a clone of RHEL6)
with cyrus-imapd 2.3.16 working for years w/o problems. There are >9M
messages in ~9500 mailboxes in two partitions. Daily mail traffic is
20-50K messages.
Some weeks ago we migrated the server to a new one under
