Hi,
cyrus-imapd 3.0.13, CentOS 8
replication over IMAP, no sync_server
I try to find out why rolling replication is failing in my case. They
sync_client -A works fine.
I have enabled logging for cyrus_admin in /var/lib/imap/log/cyrus_admin
On the replica side /var/lib/imap/log/cyrus_admin:
I followed those steps:
1) shutdown imap daemon
2) rm /var/imap/db/*
3) rm /var/imap/tls_session.db and /var/imap/deliver.db
4) reconstruct -f (as cyrus user)
5) changed /usr/local/etc/imapd.conf in this manner:
#tlscache_db: berkeley-nosync
tlscache_db: skiplist
#ptscache_db: berkeley
ptscache
error detected; run recovery
> Jan 4 11:58:41 mail lmtpunix[60221]: DBERROR: critical database situation
> Jan 4 11:58:41 mail master[60046]: service lmtpunix pid 60221 in READY
> state:
> terminated abnormally
>
>
> I am wondering what is my best option?
> Upgrade to 2.4 (at
Oh good, you can just delete those two BDB files with Cyrus shut down (and
change them to skiplist while you're at it!)
Once you've done that you can delete everything in the $confdir/db folder too.
(delete might mean take a copy somewhere else until you're happy everything is
working of course
Am Mittwoch, 4. Januar 2017, 12:08:55 CET schrieb absolutely_free--- via Info-
cyrus:
> After deleting /var/imap/db/*, /var/imap/mailboxes.db and
> /var/imap/deliver.db, it rans fine for about 20 minutes, and after:
tls_sessions and deliver.db are not important (afaik) .
Files within ./db ARE impo
Indeed, with all the right libraries. You can't upgrade libdb without
everything going to shit, which is why we have ditched BDB - the upgrade
path is bogus.
Bron.
On Wed, 4 Jan 2017, at 21:20, absolutely_free--- via Info-cyrus wrote:
>
> Hi Bron,
> thank you for you reply.
> What do y
I am wondering what is my best option?
Upgrade to 2.4 (at least)?
Thank you
>Messaggio originale
>Da: "Niels Dettenbach"
>Data: 04/01/2017 11.28
>A: , "absolutely_f...@libero.it"
>Ogg: Re: R: Re: DBERROR: critical database situation
>
>Am Mittw
Am Mittwoch, 4. Januar 2017, 11:18:42 CET schrieb absolutely_free--- via Info-
cyrus:
> ./tls_sessions.db: Berkeley DB (Btree, version 9, little-endian)
> ./deliver.db: Berkeley DB (Btree, version 9, little-endian)
>
> So, I can convert tls_sessions and deliver db to skiplist format, right?
> How
Hi Bron,thank you for you reply.What do you mean with "get some version 10
binaries"?Do you mean "binaries from FreeBSD 10"?
Thank you
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
Hi Niels,
thank you for your reply.
I am using cyrus from sources (ports).
root@mail:/var/imap# find . -name "*.db" -exec file '{}' \;
./mailboxes.db: Cyrus skiplist DB
./annotations.db: Cyrus skiplist DB
./db.backup1/annotations.db: Cyrus skiplist DB
./db.backup1/mailboxes.db: Cyrus skiplist DB
> I've been using Cyrus-imap 2.0.16.
>> I've seen that there are two process "ctl_mboxlist -r" running along
>> 30 days and they consume a lot of CPU.
>> Is this an anomaly?
>> The imap service it's ok but a little slow.
>>
>> Is it adv
On 10/25/12 13:59 +0200, Ana B. Diez wrote:
>Hi all,
>
>I've been using Cyrus-imap 2.0.16.
>I've seen that there are two process "ctl_mboxlist -r" running along 30 days
>and they consume a lot of CPU.
>Is this an anomaly?
>The imap service it's ok
Hi all,
I've been using Cyrus-imap 2.0.16.
I've seen that there are two process "ctl_mboxlist -r" running along 30 days
and they consume a lot of CPU.
Is this an anomaly?
The imap service it's ok but a little slow.
Is it advisable to kill them and restart the service
Hello,
I found this useful patch
https://bugzilla.cyrusimap.org/show_bug.cgi?id=3244
It would be very useful if this patch could be added to standard of
Cyrus-imapd 2.4.x
Regards
Marco
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/
When I upgrade from 2.3.7 to 2.3.13, on a 64 bit machine, do I need to
do a reconstruct -r on the entire user tree?
I'm looking at the ugrading doc, and it says "Due to byte alignment
issues in cyrus.index, all mailboxes will have to be reconstructed."
when upgrading from 2.3.3
febbraio 2008 17.43
A: Toschi Pietro
Cc: info-cyrus@lists.andrew.cmu.edu
Oggetto: Re: R: R: Error creating mailboxex with an "&" inside
On Feb 5, 2008 5:22 PM, Toschi Pietro <[EMAIL PROTECTED]> wrote:
Test result: failed.
Even if testsaslauthd -u test\&[EMAIL PR
't know. Maybe in the authentication side.
>
> Thanx
>
> Pietro
>
>
> -Messaggio originale-
> Da: Alain Spineux [mailto:[EMAIL PROTECTED]
> Inviato: martedì 5 febbraio 2008 17.43
> A: Toschi Pietro
> Cc: info-cyrus@lists.andrew.cmu.edu
> Oggetto: Re: R: R:
5 febbraio 2008 17.43
A: Toschi Pietro
Cc: info-cyrus@lists.andrew.cmu.edu
Oggetto: Re: R: R: Error creating mailboxex with an "&" inside
On Feb 5, 2008 5:22 PM, Toschi Pietro <[EMAIL PROTECTED]> wrote:
>
> Test result: failed.
>
> Even if testsaslauthd -u test\&
On Tue, 5 Feb 2008, Toschi Pietro wrote:
>
> Test result: failed.
>
> Even if testsaslauthd -u test\&[EMAIL PROTECTED] -p results in
> an 0: OK "Success." response, and the mailbox really exists on IMAP
> server, I can't successfully login using IMAP clients to the IMAP
> server.
>
> Maybe som
mp;[EMAIL PROTECTED])
but dont allow you to manage it !
Try this
> sam user/test&[EMAIL PROTECTED] anyone p
you will get an error !
>
>
> -Messaggio originale-
> Da: Toschi Pietro
> Inviato: martedì 5 febbraio 2008 15.49
> A: 'Michael Menge'; 'Jorey
that cyrus and sasl communicate
-Messaggio originale-
Da: Toschi Pietro
Inviato: martedì 5 febbraio 2008 15.49
A: 'Michael Menge'; 'Jorey Bump'
Cc: info-cyrus@lists.andrew.cmu.edu
Oggetto: R: R: Error creating mailboxex with an "&" inside
I'm afraid I think y
] Per conto di Michael Menge
Inviato: martedì 5 febbraio 2008 15.20
A: info-cyrus@lists.andrew.cmu.edu
Oggetto: Re: R: Error creating mailboxex with an "&" inside
Hi,
i think you have another problem, & has to be encoded in imap as &- .
The encoding is done by the mailclie
Hi,
i think you have another problem, & has to be encoded in imap as &- .
The encoding is done by the mailclient. But on the other hand cyrus
expacts the user
to have a folder under user that matches the username used for authentication.
IMHO using & in username is a bad idea as the authenti
Unfortunately I am using imapsync to migrate messages between already created
top-level mailboxex, but it doesn't seem to take care of those details for me
and failed to create every subfolder with special character until I applied the
Kolab patch that modified GOODCHAR macro in mailboxes.c.
Ap
On Mon, 12 Nov 2007, Bron Gondwana wrote:
>> It seems to me that the replication code ought to be a bit more robust
>> than this when a replica goes down or loses network connectivity. Is
>> the 2.3.10 code any better than 2.3.9 in the way this kind of situation
>> is handled?
>
> I believe David
On Sat, Nov 10, 2007 at 07:09:53PM -0800, Rich Wales wrote:
> After about a week of having synchronization running perfectly in my
> 2.3.9 system, I finally got another bailout incident with sync_client
> on my master server.
>
> This happened just after I shut down my replica server (to move it t
After about a week of having synchronization running perfectly in my
2.3.9 system, I finally got another bailout incident with sync_client
on my master server.
This happened just after I shut down my replica server (to move it to
a different location). About two minutes after the replica went dow
Great!
A very useful feature in a real multidomain environment I think!
I am currently busy working on logging some IMAP events patching imapd.c. I'll
enforce your patch immediately after that and let you know my results.
Thank you a lot.
P
-Messaggio originale-
Da: Alain Spineux [mail
PROTECTED]
Inviato: mercoledì 7 novembre 2007 18.17
A: Toschi Pietro
Cc: Cyrus Mailing List
Oggetto: Re: R: sieve_admins imapd.conf option
On Nov 7, 2007 2:56 PM, Toschi Pietro <[EMAIL PROTECTED]> wrote:
> Ok, I see.
> But I wasn't able to find any source file in cyrus source tree t
On Nov 7, 2007 2:56 PM, Toschi Pietro <[EMAIL PROTECTED]> wrote:
> Ok, I see.
> But I wasn't able to find any source file in cyrus source tree that reads
> that config option! Since it actually results correctly used, I expected that
> at least one source file (maybe related to the module) loads
Ok, I see.
But I wasn't able to find any source file in cyrus source tree that reads that
config option! Since it actually results correctly used, I expected that at
least one source file (maybe related to the module) loads and
evaluates it.
Or am I missing something?
Pietro Toschi
Actalis S.
On Sun, Nov 04, 2007 at 08:42:21PM -0800, Rich Wales wrote:
> Wesley Craig wrote:
>
> > But most sync_server errors that will cause sync_client to bail out
> > ought to cause sync_server to give a reasonably unique log message
> > for the failure.
>
> As I explained earlier this evening, I didn't
Wesley Craig wrote:
> But most sync_server errors that will cause sync_client to bail out
> ought to cause sync_server to give a reasonably unique log message
> for the failure.
As I explained earlier this evening, I didn't see ANYTHING AT ALL in
the replica server's logs that resembled any sort
On 04 Nov 2007, at 22:57, Rich Wales wrote:
> Should I be looking for similar syslog messages on my replica server
> too (and checking syslog.conf on that system if necessary)?
No, not similar. But most sync_server errors that will cause
sync_client to bail out ought to cause sync_server to giv
Wesley Craig wrote:
> If you're running with -r -l . . . , you should be getting messages
> like:APPEND user.mariein syslog at level INFO. If you're
> not seeing those, then you have syslog configured to filter them.
Thanks. It looks like that's what was h
The log files are pretty obvious in what they say, e.g., they just
list mailboxes or users to check. So I suspect they would reveal to
you which mailboxes are problematic. I sort of assume that you're
running sync_client with -l, otherwise it doesn't log much. If it's
run with -l, it sho
If you're running with -r -l (-v is for interactive use -- it causes
printf output), you should be getting messages like:
APPEND user.marie
in syslog at level INFO. If you're not seeing those, then you have
syslog configured to filter them. See the man page for syslog.c
what the log is telling me.
Yes, I am using the "-l" flag (sync_client -r -l -v), but I'll have
to say once again that neither /var/log/messages nor any other log
file on my master server shows any other sync-related error message
of any sort whatsoever, except for the "Error in d
Wesley Craig wrote:
> No, sync_server doesn't take much in the way of command line options.
Hmmm. OK, thanks.
> If the problem appears to be reproducible, you can enable telemetry
> logging or examine the mailboxes that are causing problem.
I currently have absolutely no idea as to what is cau
On 04 Nov 2007, at 14:27, Rich Wales wrote:
> No, sorry, as best I can tell, there isn't anything non-routine in any
> of the log files on my replica server.
> Do I need to specify any command-line flags to sync_server?
No, sync_server doesn't take much in the way of command line
options. If th
Wesley Craig wrote:
> The replica sync_server will also log to syslog.
No, sorry, as best I can tell, there isn't anything non-routine in any
of the log files on my replica server.
Do I need to specify any command-line flags to sync_server?
--
Rich Wales === Palo Alto, CA, USA =
On 04 Nov 2007, at 13:11, Rich Wales wrote:
> Where would I find this log info? As I said earlier, the only info
> I've
> found so far are the "Error in do_sync(): bailing out!" notices in the
> /var/log/messages file. Are there some other log files saved
> somewhere
> else? I do have "-l" a
Wesley Craig wrote:
> Both sync_client and sync_server typically log problems. Those
> logs are probably immediately helpful. Further information would
> depend on the reason for the bail out.
Where would I find this log info? As I said earlier, the only info I've
found so far are the "Error i
On 03 Nov 2007, at 23:20, Rich Wales wrote:
> Wesley Craig wrote:
>> It usually dies for a reason, i.e., some discrepancy that either
>> sync_client or sync_server couldn't handle. The typical way to
>> handle it is to contact someone.
>
> What sort of debugging output am I going to need to genera
Wesley Craig wrote:
> It usually dies for a reason, i.e., some discrepancy that either
> sync_client or sync_server couldn't handle. The typical way to
> handle it is to contact someone.
What sort of debugging output am I going to need to generate in order
for anyone to have a chance of tracking
Ken Murchison wrote:
> sync_client in 2.3.10 should be much more resilient.
That's good to know. However, I'm reluctant to upgrade quite yet,
given that 2.3.10 has only been out for a week and (judging from the
"Cyrus IMAPd 2.3.10 Released" thread") seems to have a few problems.
Can you (or any
On 31 Oct 2007, at 22:42, Rich Wales wrote:
> Can you (or anyone else) suggest anything I can do in the meantime
> (while I'm still running 2.3.9) to ensure that a sync_client stays
> running on my master server, or to start a new one as needed if it
> dies?
It usually dies for a reason, i.e., som
t that the "sync_client -r"
> processes on the master tend to die after a while -- at which point no
> more sync activity happens, ever, until I restart Cyrus on the master.
>
> Here are the sync-related lines in my configuration files.
>
> On the master:
>
>
I'm running 2.3.9 on a FreeBSD 6.2 system.
Recently, I installed 2.3.9 on an Ubuntu 7.10 system and set it up as
a replica of my original server.
Everything seems to be running well, except that the "sync_client -r"
processes on the master tend to die after a while -- at which poi
ailbox with sub-folder.
> I remove the cyrus.index from this sub-folder, run cyrreconstruct on the
> mailbox
> and expect to have the cyrus.index file rebuild.
> But the file is not rebuild.
> If I use the * wildcard to include all sub-folder of the mailbox, then
> the file is reb
mailbox, then
the file is rebuild.
I dont understand what is '-r' for then.
Any idea ?
A bug or a feature ?
bash-3.2$ ls
./spool/domain/m/mydomain.loc/c/user/catchall^mydomain^loc/alias2/cyrus.index
./spool/domain/m/mydomain.loc/c/user/catchall^mydomain^loc/alias2/cyrus.index
bash-
IDLE URLAUTH] Success (no protection)
Authenticated.
Security strength factor: 0
A4 GETACL INBOX
* ACL INBOX [EMAIL PROTECTED] lrswipkxtecda manager r
A4 OK Completed
A7 MYRIGHTS INBOX
* MYRIGHTS INBOX lrswipkxtecda
A7 OK Completed
A8 CREATE INBOX/foo
A8 OK Completed
A9 MYRIGHTS INBOX/boo
A9 NO Mailbox do
-Messaggio originale-
Da: Alain Spineux [mailto:[EMAIL PROTECTED]
Inviato: giovedì 27 settembre 2007 19.41
A: Toschi Pietro
Cc: info-cyrus@lists.andrew.cmu.edu
Oggetto: Re: R: question from a beginner
On 9/27/07, Toschi Pietro <[EMAIL PROTECTED]> wrote:
> Thanks for your an
On 9/27/07, Toschi Pietro <[EMAIL PROTECTED]> wrote:
> Thanks for your answer, but I posted my question here because it's related to
> how to make that using cyrus: unfortunately I would like to monitor all the
> mailboxes (or at least a large subset of them) of my server, so writing a
> client
Thanks for your answer, but I posted my question here because it's related to
how to make that using cyrus: unfortunately I would like to monitor all the
mailboxes (or at least a large subset of them) of my server, so writing a
client application that polls every mailbox is not admitted (I don't
Hi Dmitriy and Hi list members,
Cyrus authentication and authorization is a matter of great confusion to me
too. I previously asked this list about that topic (see "groups, members, LDAP
and ptloader" thread) and had some interesting replays but I feel I'm still
missing much knowledge.
For my f
Cyrus doesn't support mailbox autocreation in it's mainstream version, AFAIK
You'll need to download it from source and apply a patch available from Athen's
University.
Please check http://email.uoa.gr/projects/cyrus/ (autocreate inbox patch for
cyrus) for more details.
By
P
n module:
>
> /etc/imapd.conf
>
> ...
>
> virtdomains: yes
>
> # default value of %d for ldap_filter and ldap_base
>
> # %% = %
> # %u = user
> # %U = user portion of %u (%U = test when %u =
> [EMAIL PROTECTED])
> # %d = domain
>> Now everything seems to have come back up but the replication still has
>> problems. The client process on the master bails out frequently with
>> these errors in the log:
>
>It looks like you have some corruption in cyrus.index files on the replica
>following the crash. Try running reconst
James Ralston wrote:
I need to clear the \Reserved flag that was set on a mailbox (because
a renamemailbox operation failed halfway through.)
Is it safe to run "ctl_cyrusdb -r" while the server is running, or do
I need to shut down the server first?
Shutdown the server.
--
Kenneth
I need to clear the \Reserved flag that was set on a mailbox (because
a renamemailbox operation failed halfway through.)
Is it safe to run "ctl_cyrusdb -r" while the server is running, or do
I need to shut down the server first?
If the former, will running "ctl_cyrusdb -r"
this system.log message (or several, at the same time)Jul 28 11:51:03 servername imap[15434]: idle for too long, closing connectionFrom the cyrus source code, the -r option calls 'genquotareport', which in turn triggers the system.log sudo message. However, I cannot figure out why thi
system.log message (or several, at the same time)Jul 28 11:51:03 servername imap[15434]: idle for too long, closing connectionFrom the cyrus source code, the -r option calls 'genquotareport', which in turn triggers the system.log sudo message. However, I cannot figure out why this is be
>On my servers I have /var/lib/imap and /var/spool/imap. To migrate
>everything on another box with the same software releases, I simply stop
>cyrus, rsync both dirs to the new box and start it again. You only have a
>problem if you for example use BDB for some database backends and your old
>an
erator. Did you try
reconstruct -f -r user/forry/Mail ?
If usr/forrie/Mail didn't have the cyrus.* files, are you sure the
mailbox was made with an imap client?
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.
Forrest Aldrich wrote:
Hours after my crash, I am figuring a few things out. One of the
problems has to do with permissions on sasl2.db.
Right now, I have run "reconstruct -r" and it caught all but one
subdirectory in my restored archive. This other directory has
cyrus.index
Hours after my crash, I am figuring a few things out. One of the problems has to do with permissions on sasl2.db.Right now, I have run "reconstruct -r" and it caught all but one subdirectory in my restored archive. This other directory has
cyrus.index files, etc. and is quite large
t to allow to two different servers access in R/W
mode.
I've read about cyrus-murder which allows to distribute mailboxes along
different servers but if the server that has the mailbox for [EMAIL PROTECTED]
goes offline, this mailbox is not available.
With maildir/mailbox format, there i
Hello ,
I have just upgraded the cyrus-sasl 2.1.15 to 2.1.17 with several patch.
the usual switch %u on /etc/saslauthd.conf is no longer working !
The latest 2.1.17 changes it to be [EMAIL PROTECTED] if I want the full email address
as
the login name.
(I use LDAP backend)
It's fine for general
Jules Agee wrote:
[EMAIL PROTECTED] wrote:
On Fri, 16 Apr 2004, Luca Manganelli wrote:
NO SPAM, DAMN IT!
What? You don't like spam with your eggs?
Try the spam egg sausage and spam, that's not got much spam in it.
I like green eggs with my SPAM
---
Cyrus Home Page: http://asg.web.cmu.edu/cy
[EMAIL PROTECTED] wrote:
On Fri, 16 Apr 2004, Luca Manganelli wrote:
NO SPAM, DAMN IT!
What? You don't like spam with your eggs?
Try the spam egg sausage and spam, that's not got much spam in it.
--
Jules Agee
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.an
On Fri, 16 Apr 2004, Luca Manganelli wrote:
> NO SPAM, DAMN IT!
What? You don't like spam with your eggs?
--
Amos
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
've attached the script. It's pretty primitive (I prefer Python, but
tasks like this are quicker in the shell). Nonetheless, I think this is
a cleaner way of doing things than reconstructing all the mailboxes.
I'll be moving to using python's imaplib to do all this soon.
As for the &
On Fri, 2004-04-16 at 22:58, Craig Ringer wrote:
A message in which he failed to actually attach the file he was talking
about. It's attached this time, as text/plain so that overzealous mail
scanners don't remove it.
Craig Ringer
#!/bin/bash
#
# /var/tmp/scan/clamout is a file containg the outp
, which seems to work.
Back to
the main topic, our cron entry (Red Hat Linux) is:
su - cyrus -c "/usr/lib/cyrus-imapd/reconstruct -r user >
/dev/null"
and the "-r" does seem to work for us!
John
At 04:05 AM 4/16/
Title: New Page 1
NO SPAM, DAMN
IT!
-Messaggio originale-Da: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Inviato: venerdì 16 aprile 2004
10.56A: [EMAIL PROTECTED]Oggetto:
?
北 京 天 通 特 价 机 票
网
Thanks, but I must have a different version or something, here's what i get when
i run that.
localhost.localdomain> reconstruct -r -f user.chris
usage: reconstruct [-r] mailbox
so that second line is telling me that my usage is incorrect. I cannot use the
-f or the -m flag, and even t
Hello all,
If I am trying to reconstruct user.chris.Sent and user.chris.Save, should I be
able to simply run: "reconstruct -r user.chris"?
If so, it does not seem to work. I have to manually reconstruct every single
subdirectory.
If I misunderstood the "-r" option, what is
> "Luca Manganelli" <[EMAIL PROTECTED]> 03/12/04 06:11pm >>>
>> -Messaggio originale-
>> Da: Mike O'Rourke [mailto:[EMAIL PROTECTED]
>> Inviato: venerdì 12 marzo 2004 17.45
>> A: [EMAIL PROTECTED]
>> Oggetto: Re: Problem in authenticating via sasldb2
>> 1. saslauthd has *nothing* to do wi
On Mon, 8 Mar 2004, Luca Manganelli wrote:
> Mar 8 18:57:19 ksmail-test perl: No worthy mechs found
Totally absurd I know, and I'm sorry that this doesn't help your
situation at all, but whenever I see this message, I can't help but
to think of Wayne's World. Yeah, pretty sad. It's a Monday.
> For debugging outputs:
>
> # saslauthd -d -a pam
Ok.
> > sasl_pwcheck_method: saslauthd
> > sasl_mech_list: pam
>
> No, this is wrong. Here should be "plain login":
I changed it into:
sasl_mech_list: plain login
and restarted both imap and sasl daemons. But it doesn't work. The log i
Hi,
I have a few question about database recovery, aka "ctl_cyrusdb -r".
What exactly is the purpose of database recovery ? On which database
does it operate ? If the database is corrupted, can it fix it ? The
way I understand it is that, in case imapd stop abruptely, it will
r
On Thu, 26 Feb 2004, Etienne Goyer wrote:
> I have a few question about database recovery, aka "ctl_cyrusdb -r".
>
> What exactly is the purpose of database recovery ? On which database
> does it operate ? If the database is corrupted, can it fix it ?
Operates on all d
ead (with cyrus down). I *suppose*
it does the same job as ctl_cyrusdb -r on berkeley databases.
---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
> On Fri, 19 Dec 2003 16:55:29 +0100,
> Paul Boven <[EMAIL PROTECTED]> (pb) writes:
pb> The system in question is Solaris 9 Sparc, cyrus-imapd-2.2.2-BETA,
pb> cyrus-sasl-2.1.17. Berkely is db-4.1.25.
I don't know if this will alter things any, but since you're
already using latest of the
Hi everyone,
Due to some form of database-corruption (again!) ctl_cyrusdb -r won't
work anymore. During the checkpoint (ctl_cyrusdb -c), the following
messages appear:
ctl_cyrusdb: unable to sync environment
ctl_cyrusdb: unable to archive environment
This is logged to syslog when
On Thu, 27 Mar 2003, Andrew McNamara wrote:
> >A SAN is just a different transport mechanism between the host and the
> >drives -- the protocol is the same old SCSI that has been around for
> >years. That said, there is less interoperability than one would like at
> >this point.
> >
> >The basic
>A SAN is just a different transport mechanism between the host and the
>drives -- the protocol is the same old SCSI that has been around for
>years. That said, there is less interoperability than one would like at
>this point.
>
>The basic problem with NFS is that either you violate standard U
Andrew McNamara wrote:
You probably don't want to be running cyrus on an NFS partition.
The only other option would be a SAN, and people here trust them even
less. BTW, they've successfully been running a large, heavily used,
Oracle instance for several years now over NFS to a Netapp with se
>> We've noticed that "ctl_cyrusdb -r" is quite slow when working against an
>> NFS spool (Netapp) on an otherwise quiesent system. Looking at a gcore,
>> I see that the slow part is preening the mailboxes (deleting reserved
>> mailboxes), rather than rolli
On Wed, 26 Mar 2003, Andrew McNamara wrote:
> We've noticed that "ctl_cyrusdb -r" is quite slow when working against an
> NFS spool (Netapp) on an otherwise quiesent system. Looking at a gcore,
> I see that the slow part is preening the mailboxes (deleting reserved
&
We've noticed that "ctl_cyrusdb -r" is quite slow when working against an
NFS spool (Netapp) on an otherwise quiesent system. Looking at a gcore,
I see that the slow part is preening the mailboxes (deleting reserved
mailboxes), rather than rolling the checkpoints forward. The pro
On Sat, 14 Dec 2002, Jatin Nansi wrote:
Hi
Have you checked if the checkpoint are really done.
I had that kind of problem twice and each time the ctl_cyrusdb -r take
long because it was several days the checkpoint wasn't made.
I didn ' solve the problem but i never got it again.
I h
Lawrence Greenfield wrote:
--On Saturday, December 14, 2002 5:50 PM +0530 Jatin Nansi
<[EMAIL PROTECTED]> wrote:
[...]
Will ctl_cyrusdb -r take 10 hours ? I dread the day when the system will
need downtime again.
This is on a decent 2 x P3 1 GHz with 100 GB scsi raid and 1 GB RAM,
abou
--On Saturday, December 14, 2002 5:50 PM +0530 Jatin Nansi
<[EMAIL PROTECTED]> wrote:
[...]
Will ctl_cyrusdb -r take 10 hours ? I dread the day when the system will
need downtime again.
This is on a decent 2 x P3 1 GHz with 100 GB scsi raid and 1 GB RAM,
about 2000 users, 50 MB per us
Hello,
I am also quite interested in this topic as I will be using Solaris 9 with
UFS logging enabled on each slices. Can others from this mailing list
confirm that disabling UFS logging on the Cyrus slice (partition) will
speed up the "ctl_cyrusdb -r" process ? I guess if it's
delete: starting txn 2147483653
---
Will ctl_cyrusdb -r take 10 hours ? I dread the day when the system will
need downtime again.
This is on a decent 2 x P3 1 GHz with 100 GB scsi raid and 1 GB RAM,
about 2000 users, 50 MB per user.
I really need reboot times to
---
Will ctl_cyrusdb -r take 10 hours ? I dread the day when the system will
need downtime again.
This is on a decent 2 x P3 1 GHz with 100 GB scsi raid and 1 GB RAM,
about 2000 users, 50 MB per user.
I really need reboot times to be between 5 to 10 minutes, as against
Hi,
I have a cyrus IMAP system here which is taking way too long to start
up, stopping just at ctl_cyrusdb -r. There does not seem to be any
activity going on, but ctl_cyrusdb just doesnot exit.
I am running cyrus-imapd-2.1.8 on a redhat 7.3 system. The backend
database is DB3.
I need some
>From a CVS pull of just a couple of hours ago, when I try to use
'reconstruct -r' I always get:
-r: Mailbox does not exist
Could this be a result of:
altnamespace: yes
(Haven't altered default for unixhierarchysep.)
--
Amos
1 - 100 of 103 matches
Mail list logo
