> I just tried this patch, and everything compile fine.
> I wiped out my installation and mailbox partitions and started from
> scratch with this new version. I ran into another problem right away.
> When trying to do various cyradm operations, set ACL's and Deleting
> mailboxes, cyradm will just
Rob,
I reverted back again, I need to keep the box up for some folks to
test a new web interface for a few days, they are already shouting at
me. :) I know for a fact there were no stale imapd's around, I checked
that out when this happened, and completely removed the old
/usr/cyrus/bin fold
On Mon, 24 May 2004, AJ wrote:
I just tried this patch, and everything compile fine.
I wiped out my installation and mailbox partitions and started from
scratch with this new version. I ran into another problem right away.
When trying to do various cyradm operations, set ACL's and Deleting
mailbo
I just tried this patch, and everything compile fine.
I wiped out my installation and mailbox partitions and started from
scratch with this new version. I ran into another problem right away.
When trying to do various cyradm operations, set ACL's and Deleting
mailboxes, cyradm will just hang. No
> Simon Matter wrote:
>
>>>Bob Tito wrote:
>>>
>>>
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the
> On Mon, 24 May 2004, Ken Murchison wrote:
>
>>> The hash_enumerate() function is also used by some other cyrus-imapd
>>> programs so I could think, without having a closer look, that it could
>>> also break other programs, right? I suggest testing it on a affected
>>> platform with the patch appl
On Mon, 24 May 2004, Ken Murchison wrote:
The hash_enumerate() function is also used by some other cyrus-imapd
programs so I could think, without having a closer look, that it could
also break other programs, right? I suggest testing it on a affected
platform with the patch applied.
Obviously a fil
Simon Matter wrote:
Bob Tito wrote:
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
able to ge
> Bob Tito wrote:
>
>> Hi all,
>>
>> Not trying to steal the tread ;-)
>> But i hope additional/other info could be helpfull ?
>>
>> For the last couple of days i try to upgrade a FreeBSD 4.9 box from
>> 2.2.3 to 2.2.4 ...
>>
>> Luckally i did not have the problems described here, but NO WAY i was
Ken Murchison wrote:
Bob Tito wrote:
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
able to
Bob Tito wrote:
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
able to get sieve working wi
On Mon, 24 May 2004, Bob Tito wrote:
Luckally i did not have the problems described here, but NO WAY i was able to
get sieve working with unixhierachysep and altnamespace enabled.. The scripts
were just ignored.. reverting back to 2.2.3 solved the problem right away. I
disabled altnamespace, but
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
able to get sieve working with unixhierachys
> On Mon, 24 May 2004, Simon Matter wrote:
>
The backtrace is from RedHat 7.2 running ext3. Nothing special here.
Switching back to 2.2.3 made it work again and I also don't see any
corruption.
>>>
>>> Are the backtraces and straces consistent in their content?
>>
>> Here is an ltrac
>> Simon Matter wrote:
Simon Matter wrote:
>>On Sun, 23 May 2004, Simon Matter wrote:
>>
>>
>>
>>>I have just finished rebuilding my 2.2.4 rpms and I've got the same
>>>problem on my own server where I tested the build. I was able to
>>> access
>>>some
Hi all,
i am new subscriber here, so sorry for replying in this form.
2 days ago i tryed Cyrus-Imapd-2.2.4 on two host. And get same problem :
lmtp crash with BUSY error. But only for one host, and not allways(on
same user).I donwgraded to 2.2.3. For another host all works ok up to
today with 2.2
On Mon, 24 May 2004, Simon Matter wrote:
The backtrace is from RedHat 7.2 running ext3. Nothing special here.
Switching back to 2.2.3 made it work again and I also don't see any
corruption.
Are the backtraces and straces consistent in their content?
Here is an ltrace in case this helps:
[snip]
Ok,
> Simon Matter wrote:
>>>Simon Matter wrote:
>>>
>>>
>On Sun, 23 May 2004, Simon Matter wrote:
>
>
>
>>I have just finished rebuilding my 2.2.4 rpms and I've got the same
>>problem on my own server where I tested the build. I was able to
>> access
>>some folders but
> Simon Matter wrote:
>>>Simon Matter wrote:
>>>
>>>
>On Sun, 23 May 2004, Simon Matter wrote:
>
>
>
>>I have just finished rebuilding my 2.2.4 rpms and I've got the same
>>problem on my own server where I tested the build. I was able to
>> access
>>some folders but
Simon Matter wrote:
Simon Matter wrote:
On Sun, 23 May 2004, Simon Matter wrote:
I have just finished rebuilding my 2.2.4 rpms and I've got the same
problem on my own server where I tested the build. I was able to access
some folders but some others didn't work.
Was there anything consistant abou
Redhat 7.3 and EXT3 here too, also switching back to 2.2.3 fixed it.
AJ
Simon Matter wrote:
>>On Sun, 23 May 2004, Simon Matter wrote:
>>
>>
>>>I have just finished rebuilding my 2.2.4 rpms and I've got the same
>>>problem on my own server where I tested the build. I was able to access
>>>some fold
> Simon Matter wrote:
>
>>>On Sun, 23 May 2004, Simon Matter wrote:
>>>
>>>
I have just finished rebuilding my 2.2.4 rpms and I've got the same
problem on my own server where I tested the build. I was able to access
some folders but some others didn't work.
>>>
>>>Was there anything con
> Simon Matter wrote:
>
>>>On Sun, 23 May 2004, Simon Matter wrote:
>>>
>>>
I have just finished rebuilding my 2.2.4 rpms and I've got the same
problem on my own server where I tested the build. I was able to access
some folders but some others didn't work.
>>>
>>>Was there anything con
Simon Matter wrote:
On Sun, 23 May 2004, Simon Matter wrote:
I have just finished rebuilding my 2.2.4 rpms and I've got the same
problem on my own server where I tested the build. I was able to access
some folders but some others didn't work.
Was there anything consistant about these folders (spec
> On Sun, 23 May 2004, Simon Matter wrote:
>
>> I have just finished rebuilding my 2.2.4 rpms and I've got the same
>> problem on my own server where I tested the build. I was able to access
>> some folders but some others didn't work.
>
> Was there anything consistant about these folders (specific
> On Sun, 23 May 2004, Simon Matter wrote:
>
>> I have just finished rebuilding my 2.2.4 rpms and I've got the same
>> problem on my own server where I tested the build. I was able to access
>> some folders but some others didn't work.
>
> Was there anything consistant about these folders (specific
FYI, for me it happens everytime.
I wanted to note that the crash does not happen always. Even on the same
folder, sometimes it crashes, sometimes not.
Simon
---
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
> On Sun, 23 May 2004, Simon Matter wrote:
>
>> I have just finished rebuilding my 2.2.4 rpms and I've got the same
>> problem on my own server where I tested the build. I was able to access
>> some folders but some others didn't work.
>
> Was there anything consistant about these folders (specific
Rob,
Here are the details of my setup:
This only happens on mailboxes with quotas.
This was a fresh install, it did not seem to occur on an upgraded install.
I was using unixhierarchysep.
Simon, can you help with a gdb dump? I have no access to the system I
was using until Monday.
Thanks.
AJ
R
On Sun, 23 May 2004, Simon Matter wrote:
I have just finished rebuilding my 2.2.4 rpms and I've got the same
problem on my own server where I tested the build. I was able to access
some folders but some others didn't work.
Was there anything consistant about these folders (specifically, did they
h
Yes, the same thing happens here.. connection just drops.
I have reverted back to 2.2.3.
Simon Matter wrote:
Rob,
There is no core dumped from what I can tell, it looks like master
just dies for that process. Did you test this on a clean install of
2.2.4, and clean partitions and config director
> Rob,
>There is no core dumped from what I can tell, it looks like master
> just dies for that process. Did you test this on a clean install of
> 2.2.4, and clean partitions and config directories. This does not seem
> to occur on an install of 2.2.4 that was upgraded i.e., the mailboxes
> a
Rob,
There is no core dumped from what I can tell, it looks like master
just dies for that process. Did you test this on a clean install of
2.2.4, and clean partitions and config directories. This does not seem
to occur on an install of 2.2.4 that was upgraded i.e., the mailboxes
and databa
There were substantial changes in the handling of quotas in 2.2.4.
However, we're unable to replicate your problem.
Can you generate a GDB backtrace from a core dump to show where the
segfault is occuring?
On Fri, 21 May 2004, AJ wrote:
This problem does not appear in 2.2.3, I just wiped my ent
This problem does not appear in 2.2.3, I just wiped my entire 2.2.4
install and installed 2.2.3 and no issues. Ideas?
AJ
AJ wrote:
The pieces begin to come together here.. hopefully someone else benefits
from this post. I have managed to track the problem down to
not just accounts with a dot i
AJ wrote:
Here is an odd update to this...
I tried to create another user with a dot and it works fine.
It seems john.smith causes the error whereas al.jones does not.
Has anyone seen anything like this?
user/john.smith may be corrupt in some way. Try reconstructing the
mailbox and see what happe
The pieces begin to come together here.. hopefully someone else benefits
from this post. I have managed to track the problem down to
not just accounts with a dot in the mailbox name.
This problem is occuring on mailboxes with quotas only.
Mailboxes that do not have quotas do not experience this i
Here is an odd update to this...
I tried to create another user with a dot and it works fine.
It seems john.smith causes the error whereas al.jones does not.
Has anyone seen anything like this?
Thanks.
AJ
AJ wrote:
Hi,
I have an odd problem. I am running 2.2.4 fresh install and I have an
issue w
38 matches
Mail list logo
