Unable to access scalix web/caldav with zero sized reply

[ricksaul]

I have a centos 5.2 server with scalix running on it however when yum upgraded to centos 5.3 I am now no longer able to use thunderbird/lightning to access calendars. When I browse to http://scalix.mysite.com/api/dav/Calendars/Users/ i get the error message

The following error was encountered:

* Zero Sized Reply

/var/log/messages reveals the the below.. I also have acommunity edition running with the same error message however I CAN access calendars..

Can anyone help ??

regards Rick


Apr 2 05:36:30 scalix-vm yum: Updated: bind-chroot - 30:9.3.4-10.P1.el5.i386
Apr 2 05:36:30 scalix-vm yum: bind-chroot - 30:9.3.4-10.P1.el5.i386: extra callback for package bind-chroot - 30:9.3.4-10.P1.el5.i386
in state 10
Apr 2 05:39:18 scalix-vm ntpd[18738]: synchronized to LOCAL(0), stratum 10
Apr 2 05:39:18 scalix-vm ntpd[18738]: kernel time sync enabled 0001
Apr 2 05:40:24 scalix-vm ntpd[18738]: synchronized to 121.0.0.42, stratum 2
[b]Apr 2 06:13:27 scalix-vm in.imap41d: unable to dlopen /opt/scalix/lib/security/om_ldap.so: /lib/libssl.so.6: undefined symbol: EVP_CIP HER_CTX_block_size[/b]

[ricksaul]

update to my own ticket..

apache erro log revealed segmentation fault errors. Restarting apache seems to have resolved some access to calendars however the error message

Apr 7 11:21:32 scalix-vm in.imap41d: unable to dlopen /opt/scalix/lib/security/om_ldap.so: /lib/libssl.so.6: undefined symbol: EVP_CIPHER_CTX_block_size

still resides..

[Valerion]

First try rebooting your machine to make sure all your apps are using the new updated libraries. If this still doesn't work, try this:

Try running ldd /opt/scalix/lib/security/om_ldap.so

You should get a line that says: libssl.so.6 => /lib/libssl.so.6 (0xf7c55000)

Make sure that openssl-0.9.8e-7.el5 is installed. rpm -qf /lib/libssl.so.6 will tell you to which package it belongs. If this still fails for you, maybe try removing openssl and replacing it with the one from CentOS 5.2 (I would suggest doing this in a test VM). This will show for sure whether there's a library incompatibility. If there is, you need to log a bug in Bugzilla (http://bugzilla.scalix.com),