bunker I have to exact same problem after I ran the zypper up command today. No one was able to reach their malboxes.. Your temporary fix resolved the situation. Ouff. Thank you very much for your help!
WalterH crpb Thank you, this fixes the login problem. But for the developers, this is a shame, the release a new software without an automated data base upgrade.
jengelh WalterH We have automatic DB upgrade. mysql_adaptor.cfg:: schema_upgrade=host:authoritative.servername.localnet. Since 2021-07-20, the Appliance's g-setup tool injects it on first install.
crpb @WalterH there was an Database-Update! The Table didn't exist before. I was first a bit stunned about which table @proficleaner talked about until i switched my Testmachine to Community. And it was Version 108 till then.
crpb WalterH I know! Mine was 108 until i switched to the Broken One :P profilcleaner: Meine Gromox DB Version ist 109
Vinzento Hello, I just installed the update and got the same Problem. The Temporary FIX from crpb did not help me. journalctl -b |grep zcore output: Oct 17 15:25:42 grommunio.domain.de zcore[915]: [ldap_adaptor]: bind as "" on "": Can't contact LDAP server Oct 17 15:25:42 grommunio.domain.de zcore[915]: [ldap_adaptor]: search with filter mail=test-user@domain.de: No such object Oct 17 15:25:42 grommunio.domain.de zcore[915]: auth rejected for "test-user@domain.de":
crpb Thats's an LDAP-Problem. And not a missing rowCOLUMN in the SQL-Table :P. What does grommunio-admin ldap check say?
crpb Vinzento And if you search for that User? grommunio-admin user query username --filter username=email@address.tld? But this bind as "" on "": looks odd. Try an grommunio-admin mconf modify authmgr set authBackendSelection alywas_ldap
Vinzento crpb sry didnt see your reply grommunio-admin user query username --filter username=email@address.tld returns something like: "test-user@domain.de" grommunio-admin mconf modify authmgr set authBackendSelection alywas_ldap still doesn't work edit: I can also import new Users via ldap in the WebAdmin
Vinzento I Inspected the connection with tcpdump and Wireshark. this is followed by a package with: "resultCode: noSuchObject (32)" I assume the ldap object can not be found, because there is no baseObject given in the search request. But I don't know why, because ldap_search_base in /etc/gromox/ldap_adaptor.cfg is set and I checked it twice. (I have redacted all personal information) This is all i have for now Does someone have an idea?
high selbes problem hier, gerade erst die update der letzten woche gezogen. und was passiert. login problem. ist wohl noch noch nicht online..