Kopano suggested contacts lost - RESEARCH THREAD
this issue is a show-stopper, was many times reported but a real solution is not avail so far.
Here are my oberservations:
Univention Sever 4.4.3
after an update of the following UCS-packages on weekend, webapp does not suggest any e-mail addresses any more. The “history” is gone again:
2020-02-16 22:06:48 status installed univention-errata-level:all 4.4.3-443 2020-02-16 22:06:50 status installed univention-config:all 14.0.0-12A~22.214.171.124909041712 2020-02-16 22:06:50 status installed univention-management-console-login:all 11.0.4-55A~126.96.36.199002101402 2020-02-16 22:06:50 status installed univention-management-console-frontend:all 11.0.4-55A~188.8.131.52002101402 2020-02-16 22:06:50 status installed libc-bin:amd64 2.24-11+deb9u4 2020-02-16 22:06:50 status installed systemd:amd64 232-25+deb9u12A~184.108.40.206909191546 2020-02-16 22:06:51 status installed python-univention-management-console:all 11.0.4-55A~220.127.116.11002101402 2020-02-16 22:06:51 status installed libexif12:amd64 0.6.21-2+deb9u1 2020-02-16 22:06:51 status installed python-univention-directory-manager-rest:all 9.0.16-7A~18.104.22.168002061906 2020-02-16 22:07:13 status installed univention-saml-schema:all 6.0.2-24A~22.214.171.124002110948 2020-02-16 22:07:14 status installed univention-directory-manager-rest:all 9.0.16-7A~126.96.36.199002061906 2020-02-16 22:07:31 status installed univention-saml:all 6.0.2-24A~188.8.131.52002110948 2020-02-16 22:08:03 status installed univention-management-console-server:all 11.0.4-55A~184.108.40.206002101402 2020-02-16 22:08:18 status installed univention-management-console-web-server:all 11.0.4-55A~220.127.116.11002101402 2020-02-16 22:08:18 status installed univention-management-console:all 11.0.4-55A~18.104.22.168002101402 2020-02-16 22:08:18 status installed libc-bin:amd64 2.24-11+deb9u4 2020-02-16 22:08:19 status installed univention-config:all 14.0.0-12A~22.214.171.124909041712 /var/log/daemon.log.1:Feb 17 01:07:32 mailserver systemd: Stopping Kopano Groupware Core Storage Server... /var/log/daemon.log.1:Feb 17 01:07:38 mailserver systemd: Stopped Kopano Groupware Core Storage Server. /var/log/daemon.log.1:Feb 17 01:07:38 mailserver systemd: Started Kopano Groupware Core Storage Server.
It does not look like, a package itself is the reason for the “lost”.
All is see is, that the kopano-server was restarted at night.
Today at 7am, user noticed, that suggested contacts are all lost. Any ideas?
If this is really the version that you are running then this is a known issue with this version and a newer version is available for customers. The issue is that under certain situations Kopano WebApp will request an empty setting string, which will result in all WebApp settings being overwritten (which also includes the suggested contacts). The fix for this was applied in Kopano Groupware Core.
If you are running a different version then supplying further version information would be helpful. You can find commands to gather these at https://wiki.z-hub.io/display/K4U/Debugging+Kopano+on+Univention#DebuggingKopanoonUnivention-Nativepackagedapps.
thank you fbartels. Indeed this server was one out of nearly 100, that had not been updated. Shame on me, this one slipped through and might be indeed the solution.
sorry for the trouble!
but looks like, there is no new version for UCS than the one above. Any idea when there will be UCS updates?
@plzk-de yes, that is why I wrote “to customers”. If you have a subscription then you can easily update your UCS to the latest version by following https://kopano.com/blog/staying-up-to-date-with-kopano-releases-on-ucs/.
There will likely be a general update of the app in time for the UCS 5.0 release.
The thing is that the external Kopano repository breaks the update-path of UCS. If you ever had to manage more than a single UCS-Server with kopano, you do not want external repositories :)
I would be happy to go with subscriptions, if they would guarantee recent updates to UCS.
@plzk-de luckily you would not be the only one using these repositories ;-) Therefore we are always on the lookout of not disturbing the UCS update process through our repo.
The only case where some extra work is required is during upgrades between UCS releases (e.g. 4.2 to 4.3), but this extra work is documented and manageable imho https://wiki.z-hub.io/display/K4U/Performing+an+UCS+distribution+upgrade+with+Kopano+repositories+enabled.