Kolab Server 3.4 on CentOS 32bit Feedback/Question

[Soliva Andrea]

Hi all there

I Setup in the last view days/week a Kolab Server based on CentOS 6.6 
32bit and I have no issues with Kolab 3.4 which means I do not recognize 
any None functionality even I enable full debug mode on the Services 
like ActiveSync, roundcube, cyrus-imap, postfix etc. The Servers homes 
about 7 Domains (seperated with multihome config). From this Point of 
view I have to really say:

"hey guys from the developement - WELL DONE - I'm also impressed about 
roundcube"

For your Information the Installation is running on:

Architecture:          i686
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 28
Stepping:              10
CPU MHz:               1800.092
BogoMIPS:              3600.18
L1d cache:             24K
L1i cache:             32K
L2 cache:              512K

Of course it is not a Server or Installation which is installed out of 
the box (not from installing Point of view) which means you have to 
invetigate to understand the Server topology and what is for what 
responsible etc. I had also contact with a friend which his Company is 
doing security for Kolab Server. From this Point of view I created also 
my own DH Parameter as restrictions on the protocols. From this  Point 
view I'm actually in testing Phase but it seems all is working fine :-) 
To mentione again really WELL DONE guys from devel.

As it "must" be at the end :-) I have one/two message which is shown in 
/var/log/message and in "dmesg" but to not have a misunderstanding 
"There is no Impact in functionality of the Kolab Server" all is running 
fine:

/var/log/message (showing up from time to time; since Setting preforc=1 
for ptloader I do not have this Messages regularly)
Jul 15 12:34:50 kolab imap/ptloader[1463]: No entries found
Jul 15 12:34:50 kolab imap/imaps[1741]: ptload(): bad response from 
ptloader server: identifier not found
Jul 15 12:34:50 kolab imap/imaps[1741]: ptload failed: but canonified 
cyrus-admin -> cyrus-admin

dmesg (it seems that this message are appearing on regular base)
ctl_cyrusdb[1451]: segfault at 7261763b ip b73d8c41 sp bfbe2df8 error 4 
in libc-2.12.so[b7368000+190000]
ctl_cyrusdb[2346]: segfault at 7261763b ip 00b21c41 sp bfc90508 error 4 
in libc-2.12.so[ab1000+190000]
ctl_cyrusdb[3139]: segfault at 7261763b ip b74e8c41 sp bfc92df8 error 4 
in libc-2.12.so[b7478000+190000]
ctl_cyrusdb[3449]: segfault at 7261763b ip b7505c41 sp bfa0c498 error 4 
in libc-2.12.so[b7495000+190000]
ctl_cyrusdb[3539]: segfault at 7261763b ip b75d0c41 sp bfe71d38 error 4 
in libc-2.12.so[b7560000+190000]

The first message regarding "ptload" as I feel after investigation in 
several Forums etc. is making some other "Installations" also thinking 
about but should not have any Impact on whatever?

The second one makes me thinking more....there is some message about 
such Messages like:

https://issues.kolab.org/show_bug.cgi?id=3963

I do not 100% know if this is already pushed to cyrus-imap I do not 
think so right? I have installed from Kolab Repo:

# cyradm --user cyrus-admin localhost
verify error:num=20:unable to get local issuer certificate
verify error:num=27:certificate not trusted
verify error:num=21:unable to verify the first certificate
IMAP Password:
               kolab> version
name       : Cyrus IMAPD
version    : git2.5+0-Kolab-2.5-108.1.el6.kolab_3.4
vendor     : Project Cyrus
support-url: http://www.cyrusimap.org
os         : Linux
os-version : 2.6.32-504.23.4.el6.i686
environment: Built w/Cyrus SASL 2.1.23
              Running w/Cyrus SASL 2.1.23
              Built w/OpenSSL 1.0.1e-fips 11 Feb 2013
              Running w/OpenSSL 1.0.1e-fips 11 Feb 2013
              Built w/zlib 1.2.3
              Running w/zlib 1.2.3
              CMU Sieve 2.4
              TCP Wrappers
              NET-SNMP
              mmap = shared
              lock = fcntl
              nonblock = fcntl
              idle = idled
kolab> quit

If I'm right it should be the latest available Version! At least I would 
like to mentione again:

I do not have any Impact all is working fine no Problem.

Does anybody have any Information about such Messages?

Any answer appriciated :-)

Have a nice day

Kind regards

Andrea