RE: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca)
Hi, Quoting Simpson, John R john_simp...@reyrey.com: John Simpson Senior Software Engineer, I. T. Engineering and Operations All the basics seem to be working, thank you again for your help. One last question. With rolling replication, should the replica automatically catch up to the master or do I need to seed the replica with rsync (or a batched sync_client)? You should use sync_client -u to bring the replic in sync with the master. This will also take care of sieve scrtipts and mailboxes that don't change often. I can replicate individual mailboxes with sync_client -m mailbox and mailboxes are replicated when they receive a new message, but if neither of those actions takes place the replica is not populated. Yes M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen smime.p7s Description: S/MIME Signatur Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
two imapd istances with different altnamespace
Hi, my mail server runs cyrus 2.3 with altnamespace: no parameter. We make extensive use of shared folders and we are happy with this setting and with personal folders unser INBOX. But now need to use a software that only understands alternative namespace and i was thinking about using two different imapd.conf files that differ only in the line: altnamespace:no altnamespace: yes in cyrus.conf i will put: imap cmd=imapd listen=imap prefork=0 imap2 cmd=imapd -C /etc/imapd2.conf listen=10143 prefork=0 It's possible to do this setting? And it's safe using different namespaces on the same mailstore? Thanks Giuseppe Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: user_deny.db, very high load and Apple-Spotlight
On Thursday 14 October 2010 13:30:22 Marc Patermann wrote: Hi, Mark Heisterkamp schrieb am 12.04.2010 09:03 Uhr: [..] I think we shouldn't advise 5000 users not to use Spotlight, we should deactivate user_deny.db. By the way, what is this database really good for? If we want someone not to use cyrus-service we deny this person by ldap for example. Kenneth Murchison stated in some mail on this list that user_deny.db is used once per login, that's definitely not true, it is used every time the client 'uses' an IMAP-folder and that can be pretty often! Maybe we can change this behaviour by some config? Is it possible to deactivate fetching user_deny.db-entries by some config-option or do we have to patch the sources? I have this issue, too. But there is no Mac involved. It is just Thunderbird on the client (Win*/Linux) side. I created user_deny.db with touch to make the one error message go away. Now I have lots of fetching ... messages in the log (2.3.16). Is there anything to do about this? You could either upgrade to 2.4.0 as the user_deny.db code has been changed there to only try to open the database once. Or I guess you could just backport these two patches to your 2.3.16 release: http://git.cyrusimap.org/cyrus-imapd/commit/?id=e82c657e2f6a3d304d19d737104cec4782da15c0 http://git.cyrusimap.org/cyrus-imapd/commit/?id=3a755fac0d4b43071774af2a646ac4fa51aba8f3 regards, Ralf -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus IMAPd 2.4.0 Released
Per olof Ljungmark wrote: On 10/13/10 18:44, Simon Matter wrote: Simon Matter wrote: On Tue, Oct 12, 2010 at 02:23:18PM -0700, David Lang wrote: (...) IIRC autocreate is on the official todo list, isn't it? That would solve it forever. Simon Excuse my ignorance, but where can I find the Official ToDo list? Our official todo list is everything that is not in CLOSED status in Bugzilla on http://bugzilla.cyrusimap.org. I'm working to clean that up. You can help, if you want; - Examine old bug reports logged against a version prior to 2.3, and determine whether this report still applies to a more recent release (2.3.x, 2.4.x). Here's a list (you require editbugs privileges for this list): http://bugzilla.cyrusimap.org/bugzilla3/buglist.cgi?cmdtype=runnamednamedcmd=legacy- review a) When you know it's resolved you can correct the target milestone (set it to the most recent release when in doubt), and close the bug with CLOSED FIXED. b) If you know the problem still exists, update the version number the bug is logged against to the most recent version number you know the problem still exists in. c) When in doubt, make the changes that represent your best guess, but do not close it, and assign it to me (vanmeeu...@kolabsys.com). Kind regards, -- Jeroen van Meeuwen Senior Engineer, Kolab Systems AG e: vanmeeu...@kolabsys.com t: +316 42 801 403 w: http://www.kolabsys.com pgp: 9342 BF08 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Cyrus stops responding to imap:143 requests
Hello all,
for some time now we have been bugged with this problem: in our setup we have
cyrus-imapd (on HOST1) listening to both imaps:993 and imap:143 ports, the
former for the users, and the latter for a saslauthd -a rimap running on
another host (on HOST2; for SMTP AUTH purposes). While the imaps:993 has been
working flawlessly, from time to time imap:143 stops working. The socket is
still there, LISTENing, but when telnet'ing it it does not respond:
HOST2$ telnet HOST1 imap
Trying HOST1...
Connected to HOST1.
Escape character is '^]'.
The connection is established:
HOST2$ netstat -ntpe | grep 84545334
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp0 0 HOST2:49774 HOST1:143 ESTABLISHED1000
84545334 2310/telnet
but on the other side:
HOST1# netstat -ntpae|grep :49774
tcp0 0 HOST1:143 HOST2:49774 SYN_RECV0 0
-
Now, on the HOST1 side, master preforks several imapd -s and imapd processes,
but while there is a imapd -s listening to 993:
# netstat -ntpa|grep 0.0.0.0:993
tcp0 0 0.0.0.0:993 0.0.0.0:* LISTEN
725/imapd
it is master who is listening to 143:
# netstat -ntpa|grep 0.0.0.0:143
tcp0 0 0.0.0.0:143 0.0.0.0:* LISTEN
28090/master
But what is really strange is that master does not seem to include the
LISTENing port in its select() call:
# netstat -ntpae | grep master
tcp0 0 0.0.0.0:110 0.0.0.0:* LISTEN
0 24593785 28090/master
tcp0 0 0.0.0.0:143 0.0.0.0:* LISTEN
0 *24593773* 28090/master
tcp0 0 0.0.0.0:20030.0.0.0:* LISTEN
0 24593803 28090/master
tcp0 0 :::993 :::*LISTEN
0 24593777 28090/master
tcp0 0 :::995 :::*LISTEN
0 24593789 28090/master
tcp0 0 :::110 :::*LISTEN
0 24593783 28090/master
tcp0 0 :::143 :::*LISTEN
0 24593771 28090/master
tcp0 0 :::2000 :::*LISTEN
0 24593795 28090/master
tcp0 0 :::2003 :::*LISTEN
0 24593801 28090/master
# ls -laF /proc/28090/fd|grep socket
lrwx-- 1 root root 64 Oct 15 09:46*10*- socket:[24593773]
lrwx-- 1 root root 64 Oct 15 09:46 13 - socket:[24593777]
lrwx-- 1 root root 64 Oct 15 09:46 16 - socket:[24593779]
lrwx-- 1 root root 64 Oct 15 09:46 19 - socket:[24593783]
lrwx-- 1 root root 64 Oct 15 09:46 22 - socket:[24593785]
lrwx-- 1 root root 64 Oct 15 09:46 25 - socket:[24593789]
lrwx-- 1 root root 64 Oct 15 09:46 28 - socket:[24593791]
lrwx-- 1 root root 64 Oct 15 09:46 31 - socket:[24593795]
lrwx-- 1 root root 64 Oct 15 09:46 34 - socket:[24593797]
lrwx-- 1 root root 64 Oct 15 09:46 37 - socket:[24593801]
lrwx-- 1 root root 64 Oct 15 09:46 40 - socket:[24593803]
lrwx-- 1 root root 64 Oct 15 09:46 43 - socket:[24593805]
lrwx-- 1 root root 64 Oct 15 09:46 46 - socket:[24593808]
lrwx-- 1 root root 64 Oct 15 09:46 5 - socket:[24593753]
lrwx-- 1 root root 64 Oct 15 09:46 7 - socket:[24593771]
# strace -p 28090
Process 28090 attached - interrupt to quit
select(48, [8 11 14 17 20 23 26 29 32 35 38 41 44 47], NULL, NULL, {3, 544000})
= 1 (in [47], left {2, 30})
read(47, \1\0\0\0\2330\0\0, 8)= 8
[...]
The dirty way of solving this is to kill and restart master again, but in the
meantime our users are no longer able to use SMTP AUTH from HOST2...
Any clues of what is going on here?
Cheers,
Rodrigo Ventura
ISR / IST
PS: after restarting master, it is still not including 143 on its select(), but
someone is responding to 143:
HOST2$ telnet HOST1 143
Trying HOST1...
Connected to HOST1.
Escape character is '^]'.
* OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID STARTTLS AUTH=PLAIN AUTH=OTP
AUTH=DIGEST-MD5 AUTH=CRAM-MD5 SASL-IR COMPRESS=DEFLATE] HOST1 Cyrus IMAP
v2.3.16 server ready
HOST2$ netstat -ntpa|grep 143
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp0 0 HOST2:33584 HOST1:143 ESTABLISHED3398/telnet
HOST1# netstat -ntpae|grep :33584
tcp0 0 HOST1:143 HOST2:33584 ESTABLISHED 96
27619330 18847/imapd
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: user_deny.db, very high load and Apple-Spotlight
Ralf Haferkamp wrote: On Thursday 14 October 2010 13:30:22 Marc Patermann wrote: Hi, Mark Heisterkamp schrieb am 12.04.2010 09:03 Uhr: [..] I think we shouldn't advise 5000 users not to use Spotlight, we should deactivate user_deny.db. By the way, what is this database really good for? If we want someone not to use cyrus-service we deny this person by ldap for example. Kenneth Murchison stated in some mail on this list that user_deny.db is used once per login, that's definitely not true, it is used every time the client 'uses' an IMAP-folder and that can be pretty often! Maybe we can change this behaviour by some config? Is it possible to deactivate fetching user_deny.db-entries by some config-option or do we have to patch the sources? I have this issue, too. But there is no Mac involved. It is just Thunderbird on the client (Win*/Linux) side. I created user_deny.db with touch to make the one error message go away. Now I have lots of fetching ... messages in the log (2.3.16). Is there anything to do about this? You could either upgrade to 2.4.0 as the user_deny.db code has been changed there to only try to open the database once. Or I guess you could just backport these two patches to your 2.3.16 release: http://git.cyrusimap.org/cyrus-imapd/commit/?id=e82c657e2f6a3d304d19d737104 cec4782da15c0 http://git.cyrusimap.org/cyrus-imapd/commit/?id=3a755fac0d4b43071774af2a64 6ac4fa51aba8f3 Could any of you please submit a bug-report in our Bugzilla? I can then go through the motions of backporting those to the 2.3 branch if appropriate (e.g. if Bron and/or Ken agree). You may just get a 2.3.17 out of it. Kind regards, -- Jeroen van Meeuwen Senior Engineer, Kolab Systems AG e: vanmeeu...@kolabsys.com t: +316 42 801 403 w: http://www.kolabsys.com pgp: 9342 BF08 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: user_deny.db, very high load and Apple-Spotlight
On Friday 15 October 2010 11:47:15 Jeroen van Meeuwen (Kolab Systems) wrote: Ralf Haferkamp wrote: On Thursday 14 October 2010 13:30:22 Marc Patermann wrote: Hi, Mark Heisterkamp schrieb am 12.04.2010 09:03 Uhr: [..] I created user_deny.db with touch to make the one error message go away. Now I have lots of fetching ... messages in the log (2.3.16). Is there anything to do about this? You could either upgrade to 2.4.0 as the user_deny.db code has been changed there to only try to open the database once. Or I guess you could just backport these two patches to your 2.3.16 release: http://git.cyrusimap.org/cyrus-imapd/commit/?id=e82c657e2f6a3d304d19 d737104 cec4782da15c0 http://git.cyrusimap.org/cyrus-imapd/commit/?id=3a755fac0d4b43071774 af2a64 6ac4fa51aba8f3 Could any of you please submit a bug-report in our Bugzilla? Acutally there is one already :), that's want resulted in the 2.4 change: http://bugzilla.cyrusimap.org/bugzilla3/show_bug.cgi?id=3206 I can then go through the motions of backporting those to the 2.3 branch if appropriate (e.g. if Bron and/or Ken agree). You may just get a 2.3.17 out of it. thanks, Ralf -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: user_deny.db, very high load and Apple-Spotlight
Ralf Haferkamp wrote: On Friday 15 October 2010 11:47:15 Jeroen van Meeuwen (Kolab Systems) You could either upgrade to 2.4.0 as the user_deny.db code has been changed there to only try to open the database once. Or I guess you could just backport these two patches to your 2.3.16 release: http://git.cyrusimap.org/cyrus-imapd/commit/?id=e82c657e2f6a3d304d19 d737104 cec4782da15c0 http://git.cyrusimap.org/cyrus-imapd/commit/?id=3a755fac0d4b43071774 af2a64 6ac4fa51aba8f3 Could any of you please submit a bug-report in our Bugzilla? Acutally there is one already :), that's want resulted in the 2.4 change: http://bugzilla.cyrusimap.org/bugzilla3/show_bug.cgi?id=3206 Sorry, let me rephrase: Should there be a bug-report already, would you please comment on it with the extra information you provided? Anyway, I've done so accordingly. Thanks for the references! Kind regards, -- Jeroen van Meeuwen Senior Engineer, Kolab Systems AG e: vanmeeu...@kolabsys.com t: +316 42 801 403 w: http://www.kolabsys.com pgp: 9342 BF08 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: two imapd istances with different altnamespace
On 15/10/10 10:01 +0200, Giuseppe Ravasio wrote: Hi, my mail server runs cyrus 2.3 with altnamespace: no parameter. We make extensive use of shared folders and we are happy with this setting and with personal folders unser INBOX. But now need to use a software that only understands alternative namespace and i was thinking about using two different imapd.conf files that differ only in the line: altnamespace: no altnamespace: yes in cyrus.conf i will put: imap cmd=imapd listen=imap prefork=0 imap2cmd=imapd -C /etc/imapd2.conf listen=10143 prefork=0 It's possible to do this setting? And it's safe using different namespaces on the same mailstore? The altnamespace doc says that should work, with the caveat that sieve scripts will need to be updated. http://www.cyrusimap.org/docs/cyrus-imapd/2.3.16/altnamespace.php -- Dan White Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Cyrus Add-ons
Hi Guys, Can you add reference to Korreio on new cyrus website? Korreio provide a GUI for cyrus, like a cyradm. If possible add a link to Korreio, the URL is: http://korreio.sf.net (the Cyrus Admin GUI), Thanks. -- Reinaldo de Carvalho http://korreio.sf.net http://python-cyrus.sf.net While not fully understand a software, don't try to adapt this software to the way you work, but rather yourself to the way the software works (myself) Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: two imapd istances with different altnamespace
Ouch... I missed that the doc says When configured to use one (or both) of the options below and i also find the right google keys to find out this post: http://blog.fastmail.fm/2008/08/11/alternate-namespace-imap-port-may-help-outlook-ol-express-apple-mail-and-bis-users/ So it seems that i can use both namespaces at the same time! About sieve scripts if my sieve cmd=timsieved listen=127.0.0.1:sieve prefork=0 points to the altnamespace: no config it seems to me that there is no need to convert all my users sieve scripts. I'm right? Thanks Giuseppe On 10/15/2010 03:32 PM, Dan White wrote: On 15/10/10 10:01 +0200, Giuseppe Ravasio wrote: Hi, my mail server runs cyrus 2.3 with altnamespace: no parameter. We make extensive use of shared folders and we are happy with this setting and with personal folders unser INBOX. But now need to use a software that only understands alternative namespace and i was thinking about using two different imapd.conf files that differ only in the line: altnamespace: no altnamespace: yes in cyrus.conf i will put: imap cmd=imapd listen=imap prefork=0 imap2 cmd=imapd -C /etc/imapd2.conf listen=10143 prefork=0 It's possible to do this setting? And it's safe using different namespaces on the same mailstore? The altnamespace doc says that should work, with the caveat that sieve scripts will need to be updated. http://www.cyrusimap.org/docs/cyrus-imapd/2.3.16/altnamespace.php Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus Add-ons
Reinaldo de Carvalho wrote: Hi Guys, Can you add reference to Korreio on new cyrus website? Korreio provide a GUI for cyrus, like a cyradm. If possible add a link to Korreio, the URL is: http://korreio.sf.net (the Cyrus Admin GUI), Thanks. Hi Reinaldo, You have an interesting project going on there. One question; where is the source code repository? Kind regards, -- Jeroen van Meeuwen Senior Engineer, Kolab Systems AG e: vanmeeu...@kolabsys.com t: +316 42 801 403 w: http://www.kolabsys.com pgp: 9342 BF08 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus Add-ons
On 10/15/2010 09:58 AM, Reinaldo de Carvalho wrote: Hi Guys, Can you add reference to Korreio on new cyrus website? Korreio provide a GUI for cyrus, like a cyradm. If possible add a link to Korreio, the URL is: http://korreio.sf.net (the Cyrus Admin GUI), Thanks. I put an External Projects section on the Download page and included this. Thanks, Dave -- Dave McMurtrie, SPE Email Systems Team Leader Carnegie Mellon University, Computing Services Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus Add-ons
On Fri, Oct 15, 2010 at 11:12 AM, Jeroen van Meeuwen (Kolab Systems) vanmeeu...@kolabsys.com wrote: Hi Reinaldo, You have an interesting project going on there. One question; where is the source code repository? Hi Jeroen, Source code is the program code (is python). []'s -- Reinaldo de Carvalho http://korreio.sf.net http://python-cyrus.sf.net While not fully understand a software, don't try to adapt this software to the way you work, but rather yourself to the way the software works (myself) Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus Add-ons
On Fri, 15 Oct 2010, Reinaldo de Carvalho wrote: On Fri, Oct 15, 2010 at 11:12 AM, Jeroen van Meeuwen (Kolab Systems) vanmeeu...@kolabsys.com wrote: Hi Reinaldo, You have an interesting project going on there. One question; where is the source code repository? Source code is the program code (is python). I think he meant where is the version-control repository (i.e. git, subversion, mercurial, bazaar, or whatever you use for version control). -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus Add-ons
On Fri, Oct 15, 2010 at 2:20 PM, Henrique de Moraes Holschuh h...@debian.org wrote: On Fri, 15 Oct 2010, Reinaldo de Carvalho wrote: On Fri, Oct 15, 2010 at 11:12 AM, Jeroen van Meeuwen (Kolab Systems) vanmeeu...@kolabsys.com wrote: Hi Reinaldo, You have an interesting project going on there. One question; where is the source code repository? Source code is the program code (is python). I think he meant where is the version-control repository (i.e. git, subversion, mercurial, bazaar, or whatever you use for version control). I'am using RCS (newest SCCS). -- Reinaldo de Carvalho http://korreio.sf.net http://python-cyrus.sf.net While not fully understand a software, don't try to adapt this software to the way you work, but rather yourself to the way the software works (myself) Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Weird sync problems in 2.4.0
Hi Bron, the permissions are correct. If I run reconstruct -G I get a uid xxx guid mismatch message for a certain mail each time (although this message is not in the mailbox sync_client is choking on). Shouldn't reconstruct -G take care of this ? Regards Stephan Am Wednesday 13 October 2010 23:13:20 schrieben Sie: On Wed, Oct 13, 2010 at 09:13:24PM +0200, steff...@gmx.de wrote: Yes, I ran reconstruct -G a couple of times. Can you check the permissions on ths spool directories and the sync. directory? That's the next thing I can think of... Bron ( they all have to be writable by the Cyrus user ) Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
sync_client fails to exit when manual replication and rolling replication are combined (2.3.16-8)
Greetings all,
With the help of this list, I've successfully upgraded our lab 2.3.7
(RHEL/CentOS packaged) server to 2.3.16-8 and tested rolling replication,
manual replication by user, and manual replication by mailbox. Everything was
going better than expected until I shut down cyrus-imapd and /var/log/maillog
started filling up with DB errors.
If I shut down cyrus-imapd with rolling replication enabled and have not run
sync_client manually, both Cyrus and sync_client shut down cleanly.
However, if I have run sync_client manually while rolling replication is
enabled the rolling replication instance will not exit. Instead, it appears to
start spawning subprocesses and throwing database errors. The change in
database errors (below) appears to coincide with the completion of Exporting
cyrus-imapd databases. The critical DB error messages continue until
sync_client is killed.
I've run ctl_cyrusdb -r as suggested by the run recovery message.
Below are the steps that reproduce the problem, /var/log/maillog, the most
relevant portions of imapd.conf and cyrus.conf, and the packages installed on
the system. cyrus-imapd-2.3.16-8 was built with rpmbuild -ba on CentOS 5.4
64-bit using
http://www.invoca.ch/pub/packages/cyrus-imapd/cyrus-imapd-2.3.16-8.src.rpm.
The cyrus-sasl and db4 packages are from CentOS. Please let me know if any
other information would be useful.
Thank you for your help.
Best regards,
John
# /usr/lib/cyrus-imapd/sync_client -v -u testu...@testdomain.net
USER testu...@testdomain.net
ADDSUB testu...@testdomain.net INBOX
# date ; service cyrus-imapd stop
Fri Oct 15 14:51:34 EDT 2010
Shutting down cyrus-imapd: [ OK ]
Exporting cyrus-imapd databases: [ OK ]
Oct 15 14:50:58 eml-store04 sync_client[23742]: USER received NO response:
IMAP_MAILBOX_NONEXISTENT Failed to access inbox for testu...@testdomain.net:
Mailbox does not exist
NOTE: Despite this message, the user appears identical on the
master and replica when checked with ctl_mboxlist -d.
Oct 15 14:51:35 eml-store04 master[22922]: attempting clean shutdown on SIGQUIT
Oct 15 14:51:35 eml-store04 master[22922]: process 22950 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22949 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22948 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22947 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22946 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22945 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22944 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22943 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22939 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22938 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22937 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22936 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22935 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22934 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22933 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22932 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: process 22931 exited, status 75
Oct 15 14:51:35 eml-store04 master[22922]: All children have exited, closing
down
Oct 15 14:51:35 eml-store04 sync_client[23914]: DBERROR db4: region 1
(environment): reference count went negative
Oct 15 14:51:35 eml-store04 sync_client[23916]: DBERROR db4: region 1
(environment): reference count went negative
Oct 15 14:51:35 eml-store04 sync_client[23919]: DBERROR db4: region 1
(environment): reference count went negative
Oct 15 14:51:35 eml-store04 sync_client[23925]: DBERROR db4: region 1
(environment): reference count went negative
Oct 15 14:51:35 eml-store04 sync_client[23929]: DBERROR db4: region 1
(environment): reference count went negative
... many more ...
Oct 15 14:51:41 eml-store04 sync_client[25331]: DBERROR db4: region 1
(environment): reference count went negative
Oct 15 14:51:41 eml-store04 sync_client[25332]: DBERROR db4: region 1
(environment): reference count went negative
Oct 15 14:51:41 eml-store04 sync_client[25333]: DBERROR db4: PANIC: fatal
region error detected; run recovery
Oct 15 14:51:41 eml-store04 sync_client[25333]: DBERROR: critical database
situation
Oct 15 14:51:41 eml-store04 sync_client[25353]: DBERROR db4: PANIC: fatal
region error detected; run recovery
Oct 15 14:51:41 eml-store04 sync_client[25353]: DBERROR: critical database
situation
... continue until sync_client is killed ...
From /etc/cyrus.conf:
START {
# do not delete this entry!
recover cmd=ctl_cyrusdb -r
# this is only necessary if using idled for IMAP IDLE
idled cmd=idled
syncclient
Re: Begin using a metapartition on existing system?
On Fri, Oct 15, 2010 at 05:02:36PM -0500, Scott Lambert wrote: I'm not doing well with my Google-foo. I initially setup our first Cyrus-IMAPd system recently. I had a conceptual misunderstanding and thought that the config directory could be configured to hold the metadata. Actually, I thought it would happen by default. I don't know what I was thinking. Now that I have that sorted out in my head, and we are out of I/O bandwidth, I want to configure a metapartition-default on a new RAID1 and move the metadata to it. I haven't been able to find documentation that says if it is safe to add the metapartition directives to the config for an existing partition on a running system. What would be the proceedure for this? Something like?: * rsync the metapartition_files to the new metapartition-default * shut down cyrus-imapd * rsync the metapartition_files to the new metapartition-default * change the imapd.conf * remove the metapartition_files from partition-default * start cyrus-imapd I would like to do it without stopping cyrus-imapd, but I suspect that changing it on a running system was not planned for in the feature. I would be most happy to be wrong. You'll find you are definitely right. You'll have to shut it down. You can make it a lot shorter by moving the 'start cyrus-imapd' before the 'remove the metapartition_files from partition-default' step. Cyrus won't mind about the spare files being there. But doing it on the fly - ouch. Definitely not designed for. It probably wouldn't be a massively hard problem to solve, but it's such a rare case that nobody much cares enough to make it work. Regards, Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Weird sync problems in 2.4.0
On Fri, Oct 15, 2010 at 08:40:40PM +0200, steff...@gmx.de wrote: Hi Bron, the permissions are correct. If I run reconstruct -G I get a uid xxx guid mismatch message for a certain mail each time (although this message is not in the mailbox sync_client is choking on). Shouldn't reconstruct -G take care of this ? Now that would have been nice to know about earlier. Error messages matter. That is actually the message that sync_client is choking on - though sync_client could probably be nicer about the error. Actually, you're right - with the correct flags reconstruct -G should be taking care of it, and not implementing those flags is my fault. I'll have to add another flag for this, because it's messy to fix. Basically it means you've had file corruption - and you need to decide if you want to create a brand new message with the corrupted content, or try to restore the old file from backup. At least that's how we've been treating it at FastMail. For now - just go and look at the message on your spool - the corruption will probably be pretty obvious! Then unlink the offending message and re-run reconstruct. It should fix your replication. For later - I'm adding extra flags to reconstruct that will be useful in this situation. They'll be in the next release. Regards, Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Begin using a metapartition on existing system?
On Fri, Oct 15, 2010 at 08:52:25PM -0700, Bron Gondwana wrote: On Fri, Oct 15, 2010 at 05:02:36PM -0500, Scott Lambert wrote: [SNIP] I want to configure a metapartition-default on a new RAID1 and move the metadata to it. I haven't been able to find documentation that says if it is safe to add the metapartition directives to the config for an existing partition on a running system. What would be the proceedure for this? Something like?: * rsync the metapartition_files to the new metapartition-default * shut down cyrus-imapd * rsync the metapartition_files to the new metapartition-default * change the imapd.conf * remove the metapartition_files from partition-default * start cyrus-imapd I would like to do it without stopping cyrus-imapd, but I suspect that changing it on a running system was not planned for in the feature. I would be most happy to be wrong. You'll find you are definitely right. You'll have to shut it down. You can make it a lot shorter by moving the 'start cyrus-imapd' before the 'remove the metapartition_files from partition-default' step. Cyrus won't mind about the spare files being there. Okay, I was worried that it might confuse things, particularly me, having the files in both locations. But doing it on the fly - ouch. Definitely not designed for. It probably wouldn't be a massively hard problem to solve, but it's such a rare case that nobody much cares enough to make it work. That makes sense. Thanks for all the work you've put into Cyrus, Bron, and Ken and everybody. -- Scott LambertKC5MLE Unix SysAdmin lamb...@lambertfam.org Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: sync_client fails to exit when manual replication and rolling replication are combined (2.3.16-8)
On Fri, Oct 15, 2010 at 03:42:21PM -0400, Simpson, John R wrote: However, if I have run sync_client manually while rolling replication is enabled the rolling replication instance will not exit. Instead, it appears to start spawning subprocesses and throwing database errors. The change in database errors (below) appears to coincide with the completion of Exporting cyrus-imapd databases. The critical DB error messages continue until sync_client is killed. [ ... ] Oct 15 14:51:41 eml-store04 sync_client[25333]: DBERROR db4: PANIC: fatal region error detected; run recovery Oct 15 14:51:41 eml-store04 sync_client[25333]: DBERROR: critical database situation Oct 15 14:51:41 eml-store04 sync_client[25353]: DBERROR db4: PANIC: fatal region error detected; run recovery Oct 15 14:51:41 eml-store04 sync_client[25353]: DBERROR: critical database situation ... continue until sync_client is killed ... Nothing magic about sync_client itself here - it's something with the hand run sync_client and attaching/detaching from the environment. This has been on the TODO list at FastMail for a while - and your information may actually help us narrow down the cause. We don't use BDB, but the log messages annoy us too! Regards, Bron. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
