s://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871921
I've seen squatter segfaulting when the index file got too large (in an older
Cyrus version). Can you check how large it is? How many messages are in the
mailbox/folder causing the crash?
How about system's ulimit? Can the cyr
Hi,
Vanilla Cyrus, no Xapian. I don't know how to run a debug-enable,
I only know the basics :/
ii cyrus-imapd
2.5.10-3+deb9u1 amd64 Cyrus mail system -
IMAP support
Best Regards,
Heiler Bemer
On Wed, Feb 5, 2020, at 9:36 PM, Heiler Bemerguy wrote:
> Is this normal ?
Absolutely not. Which Cyrus version are you running? Are you using the Xapian
search backend? Would you be able to run this with a debug-enabled build and
look at the core dump?
Cheers,
Robert
Cyrus Home Page: http
Is this normal ?
[2191259.566831] squatter[28914]: segfault at 7fa584008008 ip
563e2b9b04d9 sp 7ffe9fed4920 error 6 in squatter[563e2b9ab000+7000]
[2199792.860105] squatter[32985]: segfault at 7f3b83577008 ip
55fa60ec64d9 sp 7ffe6c6c1140 error 6 in squatter[55fa60ec1000+7000
t the non-indexed emails?. I
>> assume it should be extremely slow… so could this be launched?. Could you
>> advise me please, if another way is preferred?
>
> Normally, just the non-indexed emails.
>
> squatter -i (incremental) should be all you need to fill the gaps in
n-indexed emails.
squatter -i (incremental) should be all you need to fill the gaps in your index.
Obviously how long it takes depends on how much mail has arrived and how good
your disks are, but for 12 hours worth I wouldn't expect more than a couple of
hours to fill the gaps.
> - I a
Good morning,
We have mailboxes indexed with Xapian. We run for that Squatter in rolling mode
(-R) so that a log can create new index records while new mail enters.. is
removed and so… Nightly too move records between tiers and so…
In an emergency on one mailbox server, we moved traffic to
Tried looking into the source of squatter and verbosing on a specific folder
that always shows the problem.
Here is how it ends:
Processing index character 128, 9 total words, temp file size is 41
Processing index character 130, 8 total words, temp file size is 52
Processing index character 147
.
:
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbaby.com/cd/gabrielebulfon
--
Da: Vladislav Kurz
A: Mark
info-cyrus
Data: 11 ottobre 2017 9.37.21 CEST
Oggetto: Re: Squatter s
On Fri, May 10, 2019, at 3:58 PM, Michael Menge wrote:
> I can test again if search_fuzzy_always has an influence on
> the usage of the usage of the "search text".
Yes, please do.
Cheers,
Robert
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/piperm
Quoting Robert Stepanek :
On Fri, May 10, 2019, at 2:18 PM, Michael Menge wrote:
no the problem is not completly resolved jet.
See for details.
I tested this right now on the 3.0 branch, and I can confirm there's
an issue of matches not being found. I don't have an answer why this
is so,
On Fri, May 10, 2019, at 2:18 PM, Michael Menge wrote:
> no the problem is not completly resolved jet.
> See https://github.com/cyrusimap/cyrus-imapd/issues/2598 for details.
I tested this right now on the 3.0 branch, and I can confirm there's an issue
of matches not being found. I don't have an
ade from Cyrus-Imapd 2.4.x to 3.0.8. After some initial
problems
which we could fix cyrus imapd 3.0.8 is running stable. The one remaining
problem
we receive reports about is, that the search is not working/too slow.
First we discovered that one of the options for Squatter are not
supported
anymore
problem
we receive reports about is, that the search is not working/too slow.
First we discovered that one of the options for Squatter are not supported
anymore, "-s Skip mailboxes whose index file is older than their current
squat file (within a small time delta)." and that squatter d
Hello,
I have Cyrus 2.4 with thousand mailboxes and separated partitions for
data and metadata, with squat files in metamaildata partitions.
Every night at 2 I run "squatter -s -a -i" to update the indexes.
Two nights ago a metamaildata partition filled out. Starting from 2am
man
reports about is, that the search is not working/too slow.
First we discovered that one of the options for Squatter are not supported
anymore, "-s Skip mailboxes whose index file is older than their current
squat file (within a small time delta)." and that squatter does not like
"-r&
is not working/too slow.
First we discovered that one of the options for Squatter are not supported
anymore, "-s Skip mailboxes whose index file is older than their current
squat file (within a small time delta)." and that squatter does not like
"-r" in combination w
Squatter are not
supported anymore, "-s Skip mailboxes whose index file is older than
their current squat file (within a small time delta)." and that
squatter does not like "-r" in combination with the source "user"
> squatter -C /etc/imapd_be.conf -r us
On 10/11/17 07:37, Mark wrote:
> On 2017-10-10 16:05, Vladislav Kurz wrote:
>> Hello everyone,
>>
>> we have recently migrated our mail server from cyrus 2.2 to 2.5 (both
>> debian packages).
>>
>> We have a problem that squatter segfaults on some
Hello everyone,
we have recently migrated our mail server from cyrus 2.2 to 2.5 (both
debian packages).
We have a problem that squatter segfaults on some quite big mailboxes.
I had to add -i (--incremental) to at least index new mails. But users
cannot search in old mails (before migration). I
ments. Note that the squat backend and the squatter tool share
the same name, but really become two separate things, e.g. you'd still
use the squatter executable to index Xapian-backed search databases.
Bron wrote up a description of search setup in 2014:
https://blog.fastmail.com/2014/1
up the cyrus source code and looked for search-related code. As I
understand it, squatter is not used if the search string is shorter than 4
symbols. From squat.h it's quite clear:
/*
Don't change this unless you're SURE you know what you're doing.
Its only effect on the API
I found the reason why squatter was not running : because I built with
conversation support, squatter complained about these being a requirement but
not enabled in imapd.conf.
Enabled on impad.conf, restarted cyrus, squatter started full indexing!
And I also found my xapian config produced a lot
, mail delivery
problems, squatter holds at bad mbox and etc.I managed to find who faced to the
same problem https://github.com/cyrusimap/cyrus-imapd/issues/1599.
In my case I caught the bug exactly as described in link above. I decided to
look for more new cyrus version for centos7 and found in
tages to running squatter from cron vs. from
> > cyrus.conf?
>
> Advantage: more control. Disadvantage: none that I know of.
>
> > What does your cronjob look like?
>
> There's a version in contrib. It's called squatrunner.pl.
> --
> Sebastian Hagedorn -
What advantages / disadvantages to running squatter from cron vs. from
cyrus.conf?
Advantage: more control. Disadvantage: none that I know of.
What does your cronjob look like?
There's a version in contrib. It's called squatrunner.pl.
--
Sebastian Hagedorn - Weyertal 121, Z
- Message from Sebastian Hagedorn -
Date: Fri, 28 Apr 2017 15:45:00 +0200
From: Sebastian Hagedorn
Subject: Re: Squatter after upgrade
To: si...@simonandkate.net
Cc: "info-cyrus lists.andrew.cmu.edu"
--On 28. April 2017 um 23:13:46 +1000 Simon Wilso
- Message from Anton -
Date: Fri, 28 Apr 2017 21:22:04 +0700
From: Anton
Subject: Re: Squatter after upgrade
To: si...@simonandkate.net
Cc: "info-cyrus lists.andrew.cmu.edu"
Hi Simon!
Just put your squatter at the same place in EVENT section in ne
Hi Simon!
Just put your squatter at the same place in EVENT section in new server.
Actually I recommend you don't use stock cyrus version in centos 7 due to IDLE
bugs. Jump to 2.5.10 from kolab repo.
> 28 апр. 2017 г., в 8:13 ПП, Simon Wilson написал(а):
>
> Hi list,
&g
--On 28. April 2017 um 23:13:46 +1000 Simon Wilson
wrote:
I notice there is no SQUATTER entry in the new one - is it required, or
is the functionality no longer needed? Should I put a SQUATTER entry in
the new server's cyrus.conf?
If you want to use the SQUAT index, you need t
# Sieve or NNTP
delprune cmd="cyr_expire -E 3" at=0400
# this is only necessary if caching TLS sessions
tlsprune cmd="tls_prune" at=0400
# running squatter
squatter cmd="/usr/lib/cyrus-imapd/squatter -r user" period=1440
}
On the new one it's
Hi,
we are in the process of migrating from old cyrus imapd 2.3.16 servers
to new with cyrus 2.5.10.
We copy whith imapsync - i.e. to benefit from single instance strore.
Now the volume of the metadata is increasing to a factor of like 7-15!
It seems squatter is taking a lot more space now
On 15/06/15 16:06, Tecnología UNNOBA wrote:
> Hello!
>
> i'm using cyrus IMAPD since 11 years, on Debian VM. [0]
>
> Now, I found this problem and I can't find docs or comments about it on web:
>
> # cyrus squatter -riv user/jgcha...@comunidad.unnoba.edu.a
Hello!
i'm using cyrus IMAPD since 11 years, on Debian VM. [0]
Now, I found this problem and I can't find docs or comments about it on web:
# cyrus squatter -riv user/jgcha...@comunidad.unnoba.edu.ar
Indexing mailbox user/jgcha...@comunidad.unnoba.edu.ar... Writing index
update: No
bound and not CPU bound
Regards
Michael Menge
Quoting "Fabio S. Schmidt" :
Hi Jose ! Thanks for answering !
Your explanations are very appropriate and I couldn't agree more !
In fact, I'm just concerned if squatter causing a high load on a core even
when running with n
Hi Jose ! Thanks for answering !
Your explanations are very appropriate and I couldn't agree more !
In fact, I'm just concerned if squatter causing a high load on a core even
when running with nice 19 is the normal behavior, but I realize that it is
more a question about Linux
hank you Bron ! Once I unfortunately do not have the knowledgement
> necessary to create this patch, I will adjust my configurations to run
> squatter at specific times and disable the CPU consumption trigger on my
> monitoring solution.
>
> Even if when running with nice 19 my squatte
Thank you Bron ! Once I unfortunately do not have the knowledgement
necessary to create this patch, I will adjust my configurations to run
squatter at specific times and disable the CPU consumption trigger on my
monitoring solution.
Even if when running with nice 19 my squatter process causes a
Yes, all Cyrus processes are single threaded except mupdate. I don't think
that running squatter on multiple cores would necessarily be an improvement -
and regardless, it's not a priority for me to implement. We'd accept a patch
if someone did it and it integrated with the oth
Hi Menge ! Thanks for the tips !
I realize that running squatter every 3h is too often, once my enviroment
is still growning, we had around a tousand users but the predictions are to
have 50.000 users in a month or two. We are planning to change it to run
once each night and maybe at specific
Hi Melander !
I think that "squatter -s -i -r user" launches a recursive process on all
users, am I wrong?
On 14 July 2014 16:41, Mogens Melander wrote:
> Hi
>
> Did you launch a recursive process on all users, or did you
> launch a process per user ?
>
> On Mon,
Hi,
Quoting "Fabio S. Schmidt" :
Hi !
I'm running Cyrus 2.4.14 on Debian 6 64 Bits and I've noticed that when
squatter is running it only uses a single core. Has this behavior been
improved on newer versions?
Here is my entry:
squatter_1cmd="/usr/bin/nice
Hi
Did you launch a recursive process on all users, or did you
launch a process per user ?
On Mon, July 14, 2014 20:13, Fabio S. Schmidt wrote:
> Hi !
>
> I'm running Cyrus 2.4.14 on Debian 6 64 Bits and I've noticed that when
> squatter is running it only uses a single c
Hi !
I'm running Cyrus 2.4.14 on Debian 6 64 Bits and I've noticed that when
squatter is running it only uses a single core. Has this behavior been
improved on newer versions?
Here is my entry:
squatter_1cmd="/usr/bin/nice +n 19 /usr/lib/cyrus/bin/squatter -s -i -r
user&quo
On Feb 12, 2014 4:25 PM, "Dudi Goldenberg" wrote:
>
> >I thought this was required to get it to index subfolders also? Am I
reading the man page wrong?
> >Thanks,
> >Josh
>
> From squatter manpage:
>
> "The mailbox argument can be omitted, which
>So you can run it with -r with user specified to index all mailboxes including
>subs.
Excuse the typo... should of course be:
"So you can run it with -r with no user" etc.
Regards,
D.
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/in
>I thought this was required to get it to index subfolders also? Am I reading
>the man page wrong?
>Thanks,
>Josh
>From squatter manpage:
"The mailbox argument can be omitted, which indexes all mailboxes. Otherwise it
needs to be specified in the same format as used in cyra
On Feb 12, 2014 2:58 PM, "Dan White" wrote:
>
>> The entry has been in the config for 24 hours and I'm still seeing squat
>> errors. Here is the line I've added:
>> squatter cmd="/use/sbin/squatter -r user" period=30
>
>
> You hav
>I've added it as an event in Cyrus.conf but I am still getting the errors. The
>entry has been in the config for 24 hours and I'm still seeing squat errors.
>Here is the line I've added:
>squatter cmd="/use/sbin/squatter -r user" period=30
Just
On 02/12/14 13:36 -0600, Joshua Battles wrote:
>Hello,
>I am maintaining a mail server for a very active group of users with large
>mailboxes and am having trouble getting squatter to run.
>
>I've added it as an event in Cyrus.conf but I am still getting the errors.
>Th
Hello,
I am maintaining a mail server for a very active group of users with large
mailboxes and am having trouble getting squatter to run.
I've added it as an event in Cyrus.conf but I am still getting the errors.
The entry has been in the config for 24 hours and I'm still seeing sq
On 2013-06-24 13:24, Simon Matter wrote:
>> Hi Andy, could you file a bug for this? Then it will not be
>> forgotten...
>
> Or, could you check this bug here
> http://bugzilla.cyrusimap.org/show_bug.cgi?id=3757
>
> The patch below was the fix, could you verify if it also fixes your
> issue?
>
On Mon, 24 Jun 2013, Simon Matter wrote:
;
; Or, could you check this bug here
; http://bugzilla.cyrusimap.org/show_bug.cgi?id=3757
;
; The patch below was the fix, could you verify if it also fixes your issue?
Yes that patch fixes my issue too. I did search bugzilla but didn't
see that one becau
t;From 1661683d453ea444aae5832b4a2cb7fd54489672 Mon Sep 17 00:00:00 2001
From: Bron Gondwana
Date: Sun, 09 Dec 2012 19:42:17 +
Subject: Bug #3757 - don't segfault on mailbox close with no user
Broke squatter and possibly other users as well.
This is probably a 2.4 only fix - the code has changed
for statuscache a bit sinc
strlcpy(key + len, userid ? userid : "cyrus", sizeof(key) -
> len);
>
> *keylen = len;
>
>
> On Mon, 24 Jun 2013, Andy Fiddaman wrote:
>
> ;
> ; Hi,
> ;
> ; I've just upgraded my Cyrus installation to 2.4.17 and squatter is
> ; crashing i
my Cyrus installation to 2.4.17 and squatter is
; crashing in statuscache_buildkey() because userid is NULL.
;
; I'm not sure what the best fix for this is. Should squatter even be using
; the statuscache or should it populate "cyrus" as the username when
; initialising the index, o
Hi,
I've just upgraded my Cyrus installation to 2.4.17 and squatter is
crashing in statuscache_buildkey() because userid is NULL.
I'm not sure what the best fix for this is. Should squatter even be using
the statuscache or should it populate "cyrus" as the username when
in
root@imap:~# su - cyrus -c '/usr/bin/nice -n 19 /usr/bin/ionice -c 3
/usr/sbin/squatter -vis user/archive'
Indexing mailbox user/archive... Closing index: Cannot allocate memory
The mailbox has ~1,3 million emails with a total size of ~124Gb
The 2.6.32-5-686 Debian squeeze
Hello
We have noticed that squatter sometimes hangs. It's waiting for a lock
root@cyrprd6:/etc/cyrus-ugent/conf# strace -p 13858
Process 13858 attached - interrupt to quit
fcntl(13, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}
squatter 13858 cyrus 12uR REG
On Sun, Dec 9, 2012, at 07:55 PM, Patrick Boutilier wrote:
> On 12/09/2012 11:26 AM, Bron Gondwana wrote:
> > Please file a bug in bugzilla. It looks not too hard to fix. Will check
> > more when I'm not on a phone.
> https://bugzilla.cyrusimap.org/show_bug.cgi?id=3757
Yep - resolved in git now.
rking after I
upgraded to 2.4.17 a couple of days ago. Running squatter manaually as cyrus user give
the "Segmentation fault" error.
Has there been any changes regarding squatter since 2.4.16? I have read the
changelog but can't find any squatter related changes.
The maillog gives
of days ago. Running squatter
> manaually as cyrus user give the "Segmentation fault" error.
> Has there been any changes regarding squatter since 2.4.16? I have read the
> changelog but can't find any squatter related changes.
>
> The maillog gives the following er
On 12/09/2012 10:00 AM, Khalid Mehmood wrote:
My squtter configuation was working fine in 2.4.16, but it has stopped working after I
upgraded to 2.4.17 a couple of days ago. Running squatter manaually as cyrus user give
the "Segmentation fault" error.
Has there been any changes
Clement Hermann (nodens) wrote:
> Le 21/06/2011 18:28, Michael D. Sofka a écrit :
>> I run squatter in a perl program that forks three parallel squatter
>> processes on individual user's mailboxes. If a mailbox is locked the
>> particular squatter processing the mailbox q
Le 21/06/2011 18:28, Michael D. Sofka a écrit :
> I run squatter in a perl program that forks three parallel squatter
> processes on individual user's mailboxes. If a mailbox is locked the
> particular squatter processing the mailbox quits, but the main program
> continues to f
Per olof Ljungmark wrote:
> All,
>
> While migrating a few accounts from Exchange to Cyrus ( has nothing to
> do with the below really) and staring at log files I noted the following
>
> squatter[70553]: error locking index user/xyz: Mailbox is locked by POP
> server
&g
On 06/21/11 08:23, Bron Gondwana wrote:
> On Tue, Jun 21, 2011 at 02:16:07AM +0200, Per olof Ljungmark wrote:
>> All,
>>
>> While migrating a few accounts from Exchange to Cyrus ( has nothing to
>> do with the below really) and staring at log files I noted the fol
On Tue, Jun 21, 2011 at 02:16:07AM +0200, Per olof Ljungmark wrote:
> All,
>
> While migrating a few accounts from Exchange to Cyrus ( has nothing to
> do with the below really) and staring at log files I noted the following
>
> squatter[70553]: error locking index user/xyz:
All,
While migrating a few accounts from Exchange to Cyrus ( has nothing to
do with the below really) and staring at log files I noted the following
squatter[70553]: error locking index user/xyz: Mailbox is locked by POP
server
and squatter bails out without indexing the remaining mailboxes
> Also, does anyone know what this means for searches on material that has
> changed since the last squatter run? I have assumed, and hope, that the
> search procedure is something like this:
> search in the squatter index
> remove results referring to deleted items
> do an u
On Wed, 2009-09-02 at 08:44 -0400, Adam Tauno Williams wrote:
> On Wed, 2009-09-02 at 14:30 +0200, Paolo Cravero wrote:
> > Perhaps it is a bug in the documentation.
> > 'man squatter' in the DESCRIPTION says there's no incremental update:
> > "Squatte
On Wed, 2009-09-02 at 14:30 +0200, Paolo Cravero wrote:
> Perhaps it is a bug in the documentation.
> 'man squatter' in the DESCRIPTION says there's no incremental update:
> "Squatter creates an index of ALL messages in the mailbox, not just those
> since the last
--On 2. September 2009 14:30:18 +0200 Paolo Cravero
wrote:
Is it just a documentation error, so incremental indexing does work in
2.3.14?
Yes, it does.
--
.:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:.
.:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Kö
Hi.
Perhaps it is a bug in the documentation.
'man squatter' in the DESCRIPTION says there's no incremental update:
"Squatter creates an index of ALL messages in the mailbox, not just those
since the last time that it was run (i.e., it does NOT do incremental
up
# sudo -u cyrus squatter -v user.ross.R
Indexing mailbox user.ross.R... Writing index update: No such file or directory
Does anybody know what the error means, or what might be causing it?
I have squatter set to run nightly, but for about a month its only done
a few mailboxes and then stopped
--On 13. Juli 2009 15:36:07 +0200 Gabor Gombas wrote:
On Mon, Jul 13, 2009 at 02:09:40PM +0200, Sebastian Hagedorn wrote:
> 4 GB limit of 32 bit binaries?
Perhaps, although I haven't seen it.
That's only 3GB by default, 1GB of address space is reserved for the
kernel. Also, the stack, the
On Mon, Jul 13, 2009 at 02:09:40PM +0200, Sebastian Hagedorn wrote:
> >4 GB limit of 32 bit binaries?
>
> Perhaps, although I haven't seen it.
That's only 3GB by default, 1GB of address space is reserved for the
kernel. Also, the stack, the executable, and all the shared libraries
the executable
a process?
Swap file/partition full?
Unlikely.
Background:
I think the message "Virtual memory exhausted" is coming from your
operating system and not from the squatter process.
I disagree.
Squatter would have been said
switch (err) {
case SQUAT_ERR_OUT_OF_MEMORY:
fprintf
ull?
Background:
I think the message "Virtual memory exhausted" is coming from your
operating system and not from the squatter process.
Squatter would have been said
switch (err) {
case SQUAT_ERR_OUT_OF_MEMORY:
fprintf(stderr, "SQUAT: Out of memory (%s)\n", s);
does squatter allocate before it dies?
I monitored the process like this:
# while true; do grep VmSize /proc/16815/status; sleep 1; done;
The last lines are:
VmSize: 2453772 kB
VmSize: 2454608 kB
VmSize: 2454608 kB
VmSize: 2454884 kB
VmSize: 2192664 kB
VmSize: 2192664 kB
Of course
Sebastian Hagedorn schrieb:
> Processing index character 101, 681642 total words, temp file size is
> 2107147
> fatal error: Virtual memory exhausted
4 GB limit of 32 bit binaries?
How much RAM does squatter allocate before it dies?
--
Pascal Gienger
University of Konstanz, IT
Hi,
we run 2.3.14 and we have one user with an enormous mailbox (not his
INBOX!). It contains around 230,000 messages. We run squatter with a
cronjob on all mailboxes. Recently this one mailbox has apparently become
too big for squatter. When I try to squat it in verbose mode, it ends like
>>
> It seems like the default for cyr_expire runs at 4:00AM (delprune
> cmd="cyr_expire -E 3" at=0400) and I start squatter at 3:00AM. Do you
> think that this would cause the spike and server to lock up? We are
> running RHEL4U4
They both compete for a lot of resourc
On Nov 13, 2007 5:07 PM, Rob Banz <[EMAIL PROTECTED]> wrote:
>
>
> On Nov 13, 2007, at 16:47, Gerard wrote:
>
> > I am running squatter at 3am as a cron job on all of my servers. Over
> > the passed week I have one server where squatter spikes the load and
> &
On Nov 13, 2007, at 16:47, Gerard wrote:
> I am running squatter at 3am as a cron job on all of my servers. Over
> the passed week I have one server where squatter spikes the load and
> ends up locking up the server at around 8am every morning. Yeah, it
> seems to take that long to r
I am running squatter at 3am as a cron job on all of my servers. Over
the passed week I have one server where squatter spikes the load and
ends up locking up the server at around 8am every morning. Yeah, it
seems to take that long to run which may be an issue in itself. Has
anyone come accross
On Mon, 22 Oct 2007, Rob Mueller wrote:
>> squatter would really benefit from incremental updates. At the moment a
>> single new message in a mailbox containing 20k messages causes it to read
>> in all the existing messages in order to regenerate the index.
>
> We spok
> squatter would really benefit from incremental updates. At the moment a
> single new message in a mailbox containing 20k messages causes it to read
> in all the existing messages in order to regenerate the index.
We spoke to Ken about this ages back, and even offered to pay for the
On Sun, 21 Oct 2007, Vincent Fox wrote:
> I have seen squatter run more than 24 hours.
>
> This is on a large mail filesystem. I've seen it start up a
> second one while the first is still running. Should I:
>
> 1) Forget about squatter
> 2) Remove from cyrus.conf, run
I have seen squatter run more than 24 hours.
This is on a large mail filesystem. I've seen it start up a
second one while the first is still running. Should I:
1) Forget about squatter
2) Remove from cyrus.conf, run from cron every other day
3) Find some option to cyrus.conf for same effe
>
> Are you running the command line squatter as root? If so, then maybe
> there's a file early in the squatter run that's root owned and causing
> squatter to abort when run as the cyrus user - I'm afriad I don't know
> much about squatter, but that would be my
On Wed, Sep 05, 2007 at 03:15:33PM -0400, Robert Banz wrote:
>
> On Sep 5, 2007, at 14:49, Michael D. Sofka wrote:
>
> > On Wednesday 05 September 2007 09:44:16 am Robert Banz wrote:
> >
> >> Sep 5 02:00:00 ms1.mail.umbc.edu squatter[29759]: [ID 454541
> >&
On Wednesday 05 September 2007 09:44:16 am Robert Banz wrote:
> Sep 5 02:00:00 ms1.mail.umbc.edu squatter[29759]: [ID 454541
> local6.debug] skipping mailbox user/a28/Spam
> Sep 5 02:00:00 ms1.mail.umbc.edu squatter[29759]: [ID 454541
> local6.debug] skipping mailbox user/a28/Trash
On Sep 5, 2007, at 14:49, Michael D. Sofka wrote:
> On Wednesday 05 September 2007 09:44:16 am Robert Banz wrote:
>
>> Sep 5 02:00:00 ms1.mail.umbc.edu squatter[29759]: [ID 454541
>> local6.debug] skipping mailbox user/a28/Spam
>> Sep 5 02:00:00 ms1.mail.umbc.edu squ
Hidey ho everybody,
So, one of my backend mailservers in my cyrus cluster is doing
something silly:
Sep 5 02:00:00 ms1.mail.umbc.edu master[29759]: [ID 392559
local6.debug] about to exec /local/cyrus/bin/squatter
Sep 5 02:00:00 ms1.mail.umbc.edu squatter[29759]: [ID 621814
local6.notice
At Sun, 22 Apr 2007 00:28:29 +0200, Per olof Ljungmark wrote:
Subject: Re: squatter segfaults on large mailboxes - FreeBSD
>
> Sorry, no. Although the system itself is configured to dump cores there
> are no traces left behind here. This is a test setup so it is likely
> that I co
Greg A. Woods wrote:
At Fri, 20 Apr 2007 21:45:05 +0200, Per olof Ljungmark wrote:
Subject: Re: squatter segfaults on large mailboxes - FreeBSD
The error is
Indexing mailbox user/spamdump/archive/2006/08... Segmentation fault
kernel: pid 6988 (squatter), uid 60: exited on signal 11
Never mind
At Fri, 20 Apr 2007 21:45:05 +0200, Per olof Ljungmark wrote:
Subject: Re: squatter segfaults on large mailboxes - FreeBSD
>
> > The error is
> > Indexing mailbox user/spamdump/archive/2006/08... Segmentation fault
> > kernel: pid 6988 (squatter), uid 60: exited on sign
The error is
Indexing mailbox user/spamdump/archive/2006/08... Segmentation fault
kernel: pid 6988 (squatter), uid 60: exited on signal 11
Never mind - corrupted mailbox - sorry for the noise.
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
Cyrus-IMAP 2.3.8 with UOA autocreate patches
FreeBSD 6-STABLE
The command was:
su cyrus -c "/usr/local/cyrus/bin/squatter -r -s -v user"
The error is
Indexing mailbox user/spamdump/archive/2006/08... Segmentation fault
kernel: pid 6988 (squatter), uid 60: exited on signal 11
The
1 - 100 of 163 matches
Mail list logo
