Debian 7: Upgrade from Kolab 3.3 to 3.4

Thomas Spuhler thomas.spuhler at btspuhler.com
Sat Mar 14 16:21:44 CET 2015


On Friday, March 13, 2015 09:33:25 PM Jochen Hein wrote:
> I've just upgraded to 3.4 and am in progress testing and fixing some
> issues. All in all, my users right now only use mail (via imap) and
> webmail (standalone roundcube - I dislike providing unneeded remote
> services ).
> 
> What didn't work for me was the update to 389-dirsrv. I've had lots of
> sigill:
> 
> [3400732.019531] ns-slapd[4844]: segfault at 0 ip 00007f7ed1c32d00 sp 00007f7ec1ff3c28 error 4 in
> libback-ldbm.so[7f7ed1bfe000+98000] [3402241.119220] ns-slapd[7246]: segfault at 0 ip
> 00007fdd1fc06d00 sp 00007fdd0eff5c28 error 4 in libback-ldbm.so[7fdd1fbd2000+98000]
> [3402481.392977] ns-slapd[7542]: segfault at 0 ip 00007f3f9b4c8d00 sp 00007f3f82fe5c28 error 4 in
> libback-ldbm.so[7f3f9b494000+98000] [3403142.163259] ns-slapd[8081]: segfault at 0 ip
> 00007fcbecea5d00 sp 00007fcbdbfefc28 error 4 in libback-ldbm.so[7fcbece71000+98000]
> [3403202.255389] ns-slapd[8215]: segfault at 0 ip 00007faf6e329d00 sp 00007faf5c7f0c28 error 4 in
> libback-ldbm.so[7faf6e2f5000+98000] [3403262.351543] ns-slapd[8359]: segfault at 0 ip
> 00007f086f063d00 sp 00007f085a7e4c28 error 4 in libback-ldbm.so[7f086f02f000+98000]
> [3404211.720204] ns-slapd[8625]: segfault at 0 ip 00007f975a94bd00 sp 00007f97497eac28 error 4 in
> libback-ldbm.so[7f975a917000+98000] [3404271.744335] ns-slapd[10289]: segfault at 0 ip
> 00007ff237acdd00 sp 00007ff21f7e6c28 error 4 in libback-ldbm.so[7ff237a99000+98000]
> [3404331.847204] ns-slapd[10412]: segfault at 0 ip 00007f0b3d83dd00 sp 00007f0b2afedc28 error 4
> in libback-ldbm.so[7f0b3d809000+98000]
> 
> Trial and error showed, that ns-slapd would run when using roundcube and
> imap, but if I started postfix, I got the errors.
> 
> I've reverted to 389-dirsrv from Kolab 3.3, which seems to work:
> 
> ii  389-ds             1.2.11.29-0 all          389 Directory Server suite - metapackage
> ii  389-ds-base        1.2.11.29-0 amd64        389 Directory Server suite - server
> ii  389-ds-base-libs   1.2.11.29-0 amd64        389 Directory Server suite - libraries
> 
> Any idead what might be wrong? I've restarted the services after the
> upgrade, but did not reboot the VM. Would that be worth a try?
> 
> Jochen

I don't know why postfix would cause a segfault in libback-ldbm.so. This lib is part of 389-ds-base:
$ urpmf libback-ldbm.so
389-ds-base:/usr/lib64/dirsrv/plugins/libback-ldbm.so

and you need to upgrade 359-ds-base anyway because of the security issues:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8105
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8112

-- 
Best regards
Thomas Spuhler

All of my e-mails have a valid digital signature
ID 60114E63
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20150314/d161090a/attachment.sig>


More information about the users mailing list