Re: Squatter segfault on big mailbox

2020-01-02 Thread Gabriele Bulfon
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, 2 total words, temp file size is 12
Processing index character 152, 2 total words, temp file size is 12
Processing index character 153, 5 total words, temp file size is 26
Processing index character 172, 10 total words, temp file size is 66
Processing index character 176, 72 total words, temp file size is 498
Processing index character 191, 417128205 total words, temp file size is 
1251444163
Closing index: Not enough space
 
I will look and change the source to give more info on the backtrace of the 
error, but maybe someone here alreay has any idea?
 
Gabriele
 
 
Sonicle S.r.l. 
: 
http://www.sonicle.com
Music: 
http://www.gabrielebulfon.com
Quantum Mechanics : 
http://www.cdbaby.com/cd/gabrielebulfon
Da:
Gabriele Bulfon
A:
Vladislav Kurz
Mark
info-cyrus
Data:
17 dicembre 2019 7.26.35 CET
Oggetto:
Re: Squatter segfault on big mailbox
 
Hello, we're having the same problem with Cyrus 2.5.11 on XStreamOS/illumos
Any idea how to fix this?
Same problem both on 32 bit large files build, and 64 bit.
Looks like the Debian issue has no solution.
Can't believe this has never been addressed.
 
Gabriele
 
 
Sonicle S.r.l. 
: 
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 segfault on big mailbox
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 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 used strace to find out
if it is some particular mail, but it parsed everything fine, and failed
when dealing with some of the many temporary files squat.
The problematic mailboxes have just inbox10 GB (and15 GB with all
subfolders) and2 emails in inbox.
Has anyone else hit similar problem and solved it somehow?
I'm not sure about fixes, but there are some reports of similar
problems.  Have a look at the thread with the subject "Cyrus 2.5.10 IMAP
search" from the beginning of June this year. 
Apparently the format of the squatter database changed between 2.4 and
2.5, and some people (at least) have seen a 10x increase in the size of
the squatter database for the same mailbox.  For systems that only allow
2GB mmap, this can be a problem.
I'm not sure if this increase in size is a bug or a feature.
Mark
Hello Mark,
Thanks for the hint about old discussion. Unfortunately, there was no
solution to this issue mentioned. I found out that this was already
reported to debian, I wonder whetrher the maintainer forwarded the bug
report upstream.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871921
This is on 64-bit Linux, so mmap should not be limited to 2 GB.
And I also have noticed the extreme increase in squat file sizes.
--
Best Regards
Vladislav Kurz

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
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

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

Upgrade 2.4 -> 3: status 75, clean shutdown file missing

2020-01-02 Thread Mark
Good day,

I'm busy testing a change from Cyrus imapd version 2.4 -> 3.0.11

Everthing seems to be working, but there are a few things in the logs
that I'm mildly concerned about when shutting down:

imap[29733]: graceful shutdown
imap[29732]: graceful shutdown
imap[29724]: graceful shutdown
idled[29725]: graceful shutdown
imap[29735]: graceful shutdown
master[29721]: process type:DAEMON name:idled
path:/usr/local/cyrus/libexec/idled age:77.647s pid:29725 exited, status 75
master[29721]: process type:SERVICE name:imap
path:/usr/local/cyrus/libexec/imapd age:4.806s pid:29735 exited, status 75
master[29721]: process type:SERVICE name:imap
path:/usr/local/cyrus/libexec/imapd age:14.751s pid:29732 exited, status 75
master[29721]: process type:SERVICE name:imap
path:/usr/local/cyrus/libexec/imapd age:5.437s pid:29734 exited, status 75
master[29721]: process type:SERVICE name:imap
path:/usr/local/cyrus/libexec/imapd age:6.171s pid:29733 exited, status 75
master[29721]: process type:SERVICE name:imap
path:/usr/local/cyrus/libexec/imapd age:77.648s pid:29724 exited, status 75
master[29721]: All children have exited, closing down

In particular, is status 75 standard when shutting down?



Then, when starting up again, I get a message about skiplist shutdown
file being missing:

ctl_cyrusdb[29750]: skiplist: clean shutdown file missing, updating
recovery stamp

Is this an issue?  Is it normal?  I'm not using skiplist for any of my
databases:

annotation_db: twoskip
backup_db: twoskip
conversations_db: twoskip
duplicate_db: twoskip
mboxkey_db: twoskip
mboxlist_db: twoskip
ptscache_db: twoskip
quota_db: quotalegacy
search_indexed_db: twoskip
seenstate_db: twoskip
sortcache_db: twoskip
subscription_db: flat
statuscache_db: twoskip
tlscache_db: twoskip
tls_sessions_db: twoskip
userdeny_db: flat
zoneinfo_db: twoskip

Thanks,
Mark




Disclaimer: http://www2.peralex.com/disclaimer.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

Re: Migration issue with seen/subscription/sieve databases

2020-01-02 Thread Gionatan Danti

Il 02-01-2020 00:01 ellie timoney ha scritto:

I think, in that case, you should be fine!  It wasn't clear if your
installation had only ever been 2.3, or had previously been upgraded
to 2.3 from some earlier version in the past, so I thought I'd better
point it out just in case :)

Cheers,

ellie


Hi Ellie,
thanks again for your very useful comments.

Regards.

--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.da...@assyoma.it - i...@assyoma.it
GPG public key ID: FF5F32A8

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