Timo Sirainen wrote:
On Mar 26, 2009, at 1:00 PM, David Halik wrote:
Any thoughts on this Timo? Just wondering if you were able to
reproduce the problem and saw the same behavior. We can look into it
more if need be, but since I can replicate it on both Fedora and
Solaris, I'm guessing it's a
Yes, it'll be in next 1.1 and 1.2 releases.
On Mar 27, 2009, at 9:11 AM, David Halik wrote:
That did the trick! No more memory allocation issues. That you very
much for the patch and your help Timo. Should we expect the patch to
be in the final 1.2 release, or in a future version?
-Dave
That did the trick! No more memory allocation issues. That you very much
for the patch and your help Timo. Should we expect the patch to be in
the final 1.2 release, or in a future version?
-Dave
Timo Sirainen wrote:
On Mar 26, 2009, at 1:00 PM, David Halik wrote:
Any thoughts on this Timo
On Mar 26, 2009, at 1:00 PM, David Halik wrote:
Any thoughts on this Timo? Just wondering if you were able to
reproduce the problem and saw the same behavior. We can look into it
more if need be, but since I can replicate it on both Fedora and
Solaris, I'm guessing it's a fundamental bug wi
Any thoughts on this Timo? Just wondering if you were able to reproduce
the problem and saw the same behavior. We can look into it more if need
be, but since I can replicate it on both Fedora and Solaris, I'm
guessing it's a fundamental bug with how certain malformed emails are
searched.
Th
Unfortunately, the patch didn't help, BUT I've discovered some very
interesting things along the way that I think you'd like to hear:
1) The problem stems from certain emails with odd or badly formed
characters.
The reason I wasn't seeing it on one machine was because I was using a
differe
Great, thanks! I'll try it now and see how it goes. We've actually been
debugging this the last couple of days and it does seem to be related to
how E2BIG from iconv is handled. We set a watch on charset_to_utf8_try
and while most of the time it returned probably, every once in awhile it
woul
On Sat, 2009-03-21 at 18:58 -0400, David Halik wrote:
> Mar 21 18:43:57 er0.rutgers.edu IMAP(dhalik): : [ID 107833 mail.crit]
> Panic: Trying to allocate 2147483648 bytes
Attached patch probably helps?
diff -r 1adea68d749b src/lib-charset/charset-iconv.c
--- a/src/lib-charset/charset-iconv.c Mon
On 3/20/2009 6:26 PM, Timo Sirainen wrote:
Maybe you could try copying the libraries and using LD_LIBRARY_PATH (or
whatever it is in Solaris) to force using those libraries instead of the
default ones?
I could try that as a last resort, but I don't think it will help. We
build our own packa
On Fri, 2009-03-20 at 15:04 -0400, David Halik wrote:
> But just to be sure I moved my homedir to local disk temporarily, and
> you are totally right. The problem happened again! So now I'm stumped.
> It looks like it is neither NFS or INDEX, but an issue with Solaris as
> you suggested. It just
OK, so it isn't really the kind of bug I first thought it would be.
Instead it's allocating/leaking way too much memory.
I agree. I watched it closer again this time and it filled up all
available memory within 30 seconds.
Can you test what exactly is the difference? INDEX=MEMORY or bein
On Fri, 2009-03-20 at 13:57 -0400, David Halik wrote:
> Also, I've been keeping an eye on top while this was running and it
> seems that Dovecot is growing at an amazing rate, which is why it runs
> out of room I guess:
>
> 8081 dhalik 1 580 1030M 871M run 0:33 53.29% imap
OK,
Timo Sirainen wrote:
On Thu, 2009-03-19 at 15:25 -0400, David Halik wrote:
So far
everything is working smoothly, but when someone does a search through
directory with a large number of emails, dovecot dies and prints the
following message:
[ID 107833 mail.crit] Panic: Trying to allocate
On Thu, 2009-03-19 at 15:25 -0400, David Halik wrote:
> So far
> everything is working smoothly, but when someone does a search through
> directory with a large number of emails, dovecot dies and prints the
> following message:
>
> [ID 107833 mail.crit] Panic: Trying to allocate 2147483648 byte
Hi all,
I recently upgraded from courier to dovecot 1.1.12 on a Solaris 9 system
with about 100 users. We have been testing dovecot for sometime in a
mixed Linux/Solaris environment and are aware of the index endianess
issue with multiple archs. To solve this, we run with INDEX=MEMORY (as
se
15 matches
Mail list logo
