we have UCS 4.3-3 errata419 with kopano core 8.6.8.2 running.
Today I wanted to create a new kopano and figured out that there seem to be some issues with kopano.
First the user wanted to login to he webapp and we got the error message MAPI_E_NOT_FOUND kopano-admin -details user shows the errors WARNING: Unable to get user store entry id. User possibly has no store. and Unable to show object quota information: missing or invalid argument (0x80070057).
So I figured out that no store has been created for the user. I had to create the user store manually with kopano-admin --create-store username.
Looks for me like some kind of bug.
Beside this I figured out in /var/log/kopano/server.log following error message a tons of times but we are using kopano without any issues and the bind secret in /etc/kopano/ldap.cfg is the same like in /etc/kopano-ldap.secret.
Wed Feb 13 14:20:54 2019: [warning] LDAP (simple) bind on uid=360xmedia,cn=users,dc=360x,dc=media failed: Invalid credentials
Wed Feb 13 14:20:54 2019: [warning] Authentication by plugin failed for user "360xmedia": Trying to authenticate failed: Failure connecting any of the LDAP servers; username = 360xmedia
this was reported before and afair should be fixed by now. Are you on the latest app version?
The error message says that someone with the username 360xmedia wanted to login, but supplied the wrong password. It has nothing to do with the credentials in ldap.cfg.
I think the server logs this in the optional audit log. But here its important to say that the server logs the ip address of the process that is talking to him. so in case of the gateway it could simply be localhost. (for which you then need to check the logging of gateway for the actual user ip)
What app do you mean? Kopano core app is 8.6.8.2; Kopano webapp app is 3.4.22.1782. As UCS is not showing any updates it’s all the latest.
Regarding the logging thing. /var/log/kopano/server.log is not showing any IP addresses or something else with the mentioned error message this is why I am asking how to trace where it comes from. I assume it must some kind of internal process as the message appears since weeks constantly thousand times per day.
I restartet kopano server after enabling audit and now I do not get the errors in the server.log any longer. But the issue that stores are not created still persists.
univention-app info
UCS: 4.3-3 errata428
Installed: benno-mailarchiv=2.4.6 collabora=4.0.0.2 cups=2.2.1 dhcp-server=12.0 dudle=1.2.0-1 kopano-core=8.6.8.2 kopano-webapp=3.4.22.1782 kopano-webmeetings=3.0.1.100 kvm=2.8 letsencrypt=1.2.2-8 nagios=4.3 onlyoffice-ds=5.2.4.94 openvpn4ucs=1.1.16 rocketchat=0.74.2 samba4=4.7 self-service=3.0 uvmm=7.0 z-push-kopano=2.4.4 4.2/mattermost=5.6.3 4.1/nextcloud=14.0.6-0
Upgradable: benno-mailarchiv
dpkg -l | grep kopano-server-pac
ii kopano-server-packages 8.7.0.0-0+1.1 all Metapackage to install the entire Kopano Core stack
So beside the user issue . . . is the issue that stores are not created fixed or will it be fixed in the future?
As we have provided our kopano subscription in the coresponding settings in our UCS and activated the option to pull from the Kopano repos I assume the latest available candidates will be installed?
Please correct me if my thinking is wrong. Or let me know if I should provide further information to get behind the issue.
@fbartels As you asked for the app versions, which I provided but not for a specific log regarding the issue that stores are not created I am wondering for that last answer. I would be happy to provide logs if one would be more specific than …