Kopano Core 8.2.0 final is now available

Wiz

We upgraded this morning to 8.2.0 - final and noticed a warning we have never seen before in server.log

Mon Feb 20 08:03:55 2017: [warning] Object not found unknown user "Everyone": Everyone

The upgrade itself went without a hitch and we also executed python /usr/sbin/kopano-search-upgrade-findroots.py … so no issues there.

Also, can you look into the possibility of including an archive of the source at the time of release (for both stable and pre-final/beta releases) in the supported download area as we are compiling our own mapi version against remi’s php56 on Centos 7?

Finally, we like to know why Kopano’s mapi.so version is way smaller in size than the version we compile - ours is 1.7MB and Kopano’s is ~ 400KB… We used the instructions at https://documentation.kopano.io/kopanocore_administrator_manual/installing.html?highlight=compile as reference. Again, this is on the latest Centos 7 release with only remi’s php56 and MariaDB 10.1 installed - what’s your secret sauce?

As reference, we use:

./configure --enable-epoll \ 
--enable-unicode \
--disable-static \
--with-userscript-prefix=/etc/kopano/userscripts \
--with-quotatemplate-prefix=/etc/kopano/quotamail \
--enable-release

We previously used --enable-swig, --disable-testtools, --enable-python, --enable-tcmalloc in addition to the above, however, the configuration script gave a warning that these options were no longer recognized so we dropped them.

Cheers
Wiz

Wiz

Hello again @fbartels

Another issue with this release:

Wed Feb 22 05:06:49 2017: [notice ] Startup succeeded on pid 9608
Wed Feb 22 05:06:49 2017: [crit   ] ----------------------------------------------------------------------
Wed Feb 22 05:06:49 2017: [crit   ] Fatal error detected. Please report all following information.
Wed Feb 22 05:06:49 2017: [crit   ] Application Server version: 8,2,0,523
Wed Feb 22 05:06:49 2017: [crit   ] OS: Linux, release: 3.10.0-514.6.1.el7.x86_64, version: #1 SMP Wed Jan 18 13:06:36 UTC 2017, hardware: x86_64
Wed Feb 22 05:06:49 2017: [crit   ] Thread name: z-s: 127.0.0.1
Wed Feb 22 05:06:49 2017: [crit   ] Peak RSS: 26568
Wed Feb 22 05:06:49 2017: [crit   ] Pid 9608 caught SIGSEGV (11), traceback:
Wed Feb 22 05:06:49 2017: [crit   ] Backtrace:
Wed Feb 22 05:06:49 2017: [crit   ] #0. /lib64/libkcutil.so.0(+0x2d8c0) [0x7fdca74a48c0]
Wed Feb 22 05:06:49 2017: [crit   ] #1. /lib64/libkcutil.so.0(+0x23c88) [0x7fdca749ac88]
Wed Feb 22 05:06:49 2017: [crit   ] #2. /lib64/libkcutil.so.0(generic_sigsegv_handler+0x1d6) [0x7fdca749aff6]
Wed Feb 22 05:06:49 2017: [crit   ] #3. /lib64/libpthread.so.0(+0xf370) [0x7fdca3b8a370]
Wed Feb 22 05:06:49 2017: [crit   ] Signal errno: Success, signal code: 1
Wed Feb 22 05:06:49 2017: [crit   ] Sender pid: 0, sender uid: 0, si_status: 0
Wed Feb 22 05:06:49 2017: [crit   ] User time: -131939379829056, system time: -131906613379592, signal value: 0
Wed Feb 22 05:06:49 2017: [crit   ] Faulting address: (nil), affected fd: 0
Wed Feb 22 05:06:49 2017: [crit   ] When reporting this traceback, please include Linux distribution name (and version), system architecture and Kopano version.
Wed Feb 22 05:06:49 2017: [warning] Killing self with signal had no effect; doing regular exit without coredump.
Wed Feb 22 05:09:15 2017: [ notice] Starting server version 8,2,0,523, pid 10817
Wed Feb 22 05:09:15 2017: [notice ] Listening for TCP connections on port 236
Wed Feb 22 05:09:15 2017: [notice ] Listening for priority pipe connections on /var/run/kopano/prio.sock
Wed Feb 22 05:09:15 2017: [notice ] Listening for pipe connections on /var/run/kopano/server.sock
Wed Feb 22 05:09:15 2017: [notice ] Connection to database 'kopano' succeeded
Wed Feb 22 05:09:15 2017: [notice ] Loading searchfolders
Wed Feb 22 05:09:15 2017: [notice ] Startup succeeded on pid 10817

Starting kopano-server is touch and go (not consistent) as it crashes requiring another start to actually startup.

Cheers
Wiz

deisenlord

Fyi, my upgrade went well, just “yum upgrade”, very slick, BRAVO!

externa1

@fbartels

When will this be available as it now some weeks later ?

Regards

Christian

fbartels

@externa1 we have a bit of a disagreement on how the repository integration for Univention should be achieved. Hopefully we have new idea until the end of the week (as Univention is also quite busy with their upcoming release).

externa1

@fbartels
thanks :)

christian

Atomius

@externa1 said in Kopano Core 8.2.0 final is now available:

when

@fbartels
any news on this? I try to avoid answers from the support alla “please update to latest release” and I can’t do this :(

fbartels

@Atomius sadly Univention is still busy with their upcoming release. If you’re feeling adventurous, then you can activate their test appcenter with the following command:

ucr set appcenter/index/verify=no update/secure_apt=no repository/app_center/server='appcenter-test.software-univention.de'

This will then give you Z-Push 2.3.5 and the Kopano App with Reposupport for 8.2.x.

EDIT: or less invasive. Just add the following line to /etc/apt/sources.list, then do an apt-get update && apt-get upgrade.

deb http://repo.z-hub.io/kopano4ucs/Univention_4.0/ /

Afterwards you can follow https://wiki.z-hub.io/display/K4U/Updating+Kopano+packages+directly+from+the+Kopano+download+server

Atomius

@fbartels

It’s working with ucr set. Now I’m a real Betatester instead of half one ;)

Core shows:

Version 8.1.1.10-8.1-2

Is that similar to 8.2?

fbartels

@Atomius thats just the version of the “app”, after you have enabled the repository like explained on the wiki page, there should be a package update which brings you to 8.2.1 (you can see the actual version in the WebApp settings).

Atomius

Everything went fine. System now runs 4.1-4 errata360 (after disabling fetchmail repo)

WebApp:
3.3.0.491-23.1
Kopano Core:
8.2.1-530

Thank you for your support ;)

fbartels

@Atomius please keep your posts in English.

I also got the news a few hours ago, that the update is now officially available.

Atomius

@fbartels

sorry for that, it’s a bit confusing as the support team answered in German :D changed that.

No problem, I think this situation would repeat often, as the development is faster than the audition ;)

HPH_ZForum

Hello,

@fbartels since the changelog mentions the “Extended and enforced SSL hostname verification” with additional configuration needs I’d like to know if UCS is also affected.
Since the UCS Apache proxies the connections, correct?

BR,
HP

fbartels

@HPH_ZForum that is only relevant to you, if you have services communication directly to port 237 of Kopano. This is not the case in the default configuraton of Kopano on Univention.

Since the UCS Apache proxies the connections, correct?

No, the Univention Apache does not proxy anything for Kopano.

HPH_ZForum

@fbartels ok, thank you!

HPH_ZForum

@fbartels said in Kopano Core 8.2.0 final is now available:

@Atomius thats just the version of the “app”, after you have enabled the repository like explained on the wiki page, there should be a package update which brings you to 8.2.1 (you can see the actual version in the WebApp settings).

@fbartels the Kopano repo (direct connection) is now the suggested, “official” way of getting Kopano updates for UCS?
Or do you suggest sticking with the UCS approved releases for stability? Does the “old” method even have a future?

BR,
TP

fbartels

@HPH_ZForum if you have a subscription and want to stay up to date the Kopano repository is the recommended way. The app itself will of course also be update from time to time, but not as frequently as the repositories (the app may skip one or two mayor versions).

HPH_ZForum

@fbartels there’s a pretty dangerous downside using this method: you can’t deny or postpone Kopano updates if you want to install UCS updates. You aren’t even aware about those being available besides the UCS updates.

After testing the UCR setting yesterday I wanted to install the SMB/Samba update to UCS ASAP and because of this I did also inadvertently install the Kopano 8.2.x upgrade for UCS.

ActiveSync is more or less fine, but WebApp and Deskapp can’t connect to Kopano Core anymore. I’m going to write about this in another thread!

BR,
HP