Segmentation fault (SEGV) in cyrus ptloader / CentOS 7

[Franz Skale]

Hi,
do you have updates on this issus ?
I have the same problem now with the "stable" editon of kolab.
I upgraded cyrus to the newest git and now it works, but after i add one
kolab the same problem occurs.
For now, my workaround is quite unusal, but perhaps you've a better
solution.

1.) service stop kolab-server
2.) I delete the failed mailbox with ldapdelete:
/usr/lib/mozldap/ldapdelete  -D cn="Directory Manager" -w xxxxxxxx
uid=deaduser,ou=People,dc=example,dc=org
3.) delete the failed mailbox:
 kolab dm user/deaduser at example.org
4.) service stop cyrus-imapd (killing the idled)
5.) service start cyrus-imapd
Check, that there's no error visible in the imapd.log
6.) service kolab-server start
7.) recreating the user.
It works for another user, than i have to do it all over again for the
new user.

The problem seems to be ptclient interaction with dirsrv389.

Rgds.

Franz


Am 17.12.14 um 11:21 schrieb Cornelius Hald:
> On Wed, 2014-11-26 at 11:40 +1300, Torsten Grote wrote:
>> On Tuesday 25 November 2014 13:04:45 Cornelius Hald wrote:
>>> I was hoping you could
>>> point me to a git tag like "kolab-3.3" so I could see what they changes
>>> are that have been committed since then. Unfortunately it doesn't look
>>> like it's that easy.
>> I'm not expert in packaging, but I think that what is typically done is the 
>> inclusion of a source tarball (coming from the repository). Then sometimes 
>> patches are added on top of that until a new version is released. Then a new 
>> source tarball is taken.
>>
>> This topic might actually be a lot better suited for the devel list.
> So I've asked there, but there seems to be basically no activity on the
> devel list. I guess communications between developers is not done there
> but at the Kolabsys offices instead...
>
> http://lists.kolab.org/pipermail/devel/2014-December/015185.html
>
> Is there something like a public roadmap? A list of issues (bugs and new
> features) that are planned for inclusion into the next release?
>
> Anyway, thanks for the information. I'll try to setup a test system over
> the holidays to see if the current developer packages of cyrus will fix
> those issues.
>
> Cheers,
> Conny
>
>>> So what is the relation between Kolab and Cyrus? Is all development done
>>> upstream? If yes, all relevant code should be in git.cyrusimap.org -
>>> right?
>> Yes, we do all our development upstream as much as possible. Jeroen is a Cyrus 
>> developer and its release manager. See the latest commits:
>>
>>     http://git.cyrusimap.org/cyrus-imapd/log/
>>
>> In Kolab:Development a fairly recent snapshot from git master is packaged and 
>> updated frequently. That is why it is called development. Issues you encounter 
>> might be fixed there, but also new issues might be introduced. Some people 
>> actually run Development to notice these things early and help fixing them 
>> before they find their way into a stable release.
>>
>>> Sorry for all the questions. If there is a document that explains those
>>> things, a link would be great. Thanks :)
>> I think there's no such document, but you are welcome to make one based on 
>> what your research. ;)
>>
>> Kind Regards,
>> Torsten
>>
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4254 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.kolab.org/pipermail/users/attachments/20141223/44fd37b1/attachment.p7s>