Thanks for the fast response! The update resolved the segmentation faults.

@bosim said in SIGSEGV in Kopano-core on db-server disconnect:

Do you have coredump enabled?

Hi Bo,
unfortunately not.
'changed that and will return with stacktrace, if it comes up again.
++umgfoin.

@dylan08 said in Warning K-1504: Unable to retrieve parents for groupmember relation...:

Maybe there is an error in kopano and search result should be the “member” attribute?

you can define which attributes kopano queries from the ldap. you can find the default values in /usr/share/kopano/ldap.openldap.cfg, any modifications to the defaults should be done in the ldap.cfg.

By default the following values are used:

# Optional, default = member # Active directory: member # LDAP: memberUid ldap_groupmembers_attribute = memberUid # Optional, default = text # Active directory: dn # LDAP: text ldap_groupmembers_attribute_type = text # The attribute of the user which is listed in ldap_groupmember_attribute # Active directory: empty, matching DNs # LDAP: uid, matching users in ldap_loginname_attribute ldap_groupmembers_relation_attribute = uid

@itserv its not supported, but it works.

you can influence these reminders with the following option from your server.cfg:

# Enable/disable reminders for shared stores shared_reminders = no

I’m also having this issue:

Thu Nov 9 09:31:22 2017: [error ] [ 745] gsoap connect: () Thu Nov 9 09:31:22 2017: [error ] [ 745] M4LMsgServiceAdmin::ConfigureMsgService() MSGServiceEntry failed 80040115: network error Thu Nov 9 09:31:22 2017: [crit ] [ 745] CreateProfileTemp(): ConfigureMsgService failed 80040115: network error Thu Nov 9 09:31:22 2017: [warning] [ 745] CreateProfileTemp failed: 80040115: network error Thu Nov 9 09:31:22 2017: [error ] [ 745] Unable to open admin session. Error 0x80040115

It happens twice after a reboot and then not anymore and doesn’t seem to have any other side effects. @bhavin your “solution” doesn’t work. In fact if you do have multiple virtual domains, you will break that configuration by removing the others. It doesn’t look the issue is postfix related. It looks more to me like an issue of the kopano-server service not yet being available in time. Might be solved by setting a longer timeout for the kopano-spooler service somewhere?

J.

Just upgraded from 8.3.4 to 8.4.3 latest. I don’t recall seeing this error before.

Hi @fbartels,

thanks for these tips, I will try them. Perhaps Im doing a user per user thing out of habit from zarafa-backup. I will try but I get the impression its really nfs causing the issue. I will try this. Thank you for feedback!

I think I have solved the Problem.

1.) Stop all kopano services
2.) Import the mysql zarafa.dump
3.) Remove all files from /var/lib/kopano/search/
4.) Start all services from kopano
5.) Wait until the new index files are done

Now, I have no Error setSyncStatus(): collision

Hi @externa1 ,

a 8.4.3 release has been pushed that should fix this.

To answer my own question: when looking into the code, this setting works only for connections coming from the outside world:

From GIT: kopanocore/gateway/IMAP.cpp:
if (!lpChannel->UsingSsl()
&& lpChannel->sslctx()
&& plain && strcmp(plain, “yes”) == 0
&& lpChannel->peer_is_local() <= 0) { … }

When I set disable_plaintext_auth to yes and connect from the outside world to the gateway, everything works well:

proxy# telnet kopano.gateway.server.net pop3
Trying 1.2.3.4…
Connected to kopano.gateway.server.net.
Escape character is ‘^]’.
+OK POP3 gateway ready
USER myusername
-ERR [AUTH] Plaintext authentication disallowed on non-secure (SSL/TLS) connections
QUIT

It’s more a documentation problem than a technical …

Hi @balaji ,

i don’t see an immediate reason why not.

@lherrmann

it looks like something went wrong with the original installation, although it was running fine, i.e. kopano-server webapp and everything else was fine.

I re-installed the packages again and it was fine.

No idea why.

@jengelh Eureka!! It is confirmed… Not a kopano issue at all and thank you for posting your mysql_config output.

The issue lies with Redhat/Centos MariaDB devel rpm packages, sourced from MariaDB repo, as they royally mangled up the installation/configuration of mariadb’s connector c files/paths ex-

Centos - /usr/lib64/mariadb is nowhere to be found so /usr/lib64/mysql is used instead seeing that mariadb_config/mysql_config reference /usr/lib64 and not /usr/lib64/mariadb which should be the correct path if the connector was installed correctly. This causes libmysqlclient to be used instead of libmariadbclient which is a no no seeing that mariadb 10.2 exclusively uses libmariadb/client.

Fedora appears to be using the correct paths in install.cmake and installs mariadb connector/libmariadbclient to /usr/lib64/mariadb and include files in /usr/include/mysql which is why you are not seeing this issue.

So when kopano calls mariadb_config or mysql_config in (cf. configure.ac) on Centos with mariadb 10.2.x-devel installed, it fumbles up and spits out the ‘reconnect’ error because the mariadb connector c isn’t properly installed by the official MariaDB rpm devel packages which is why it falls back to using the ‘reconnect’ method.

Solution [Centos/Redhat]: clone master branch of mariadb-connector-c and compile/install manually then build kopano

Correct connector cmake config to use on Centos:

-- MariaDB Connector/c configuration: -- CPack generation: TGZ -- SSL support: OPENSSL Libs: /usr/lib64/libssl.so;/usr/lib64/libcrypto.so -- Zlib support: yes (using bundled zlib) -- Installation layout: DEFAULT -- Include files will be installed in include -- Libraries will be installed in lib64/mariadb -- Binaries will be installed in bin -- Documentation included from -- Required: -- Configuring done -- Generating done which produces: [root@xn1-dev connector_c]# mariadb_config Copyright 2011-2017 MariaDB Corporation AB Get compiler flags for using the MariaDB Connector/C. Usage: mariadb_config [OPTIONS] --cflags [-I/usr/include -I/usr/include/mysql] --include [-I/usr/include -I/usr/include/mysql] --libs [-L/usr/lib64/mariadb/ -lmariadb -lnsl -ldl -lm -lpthread -lssl -lcrypto] --libs_r [-L/usr/lib64/mariadb/ -lmariadb -lnsl -ldl -lm -lpthread -lssl -lcrypto] --libs_sys [-lnsl -ldl -lm -lpthread -lssl -lcrypto] --version [10.2.9] --cc_version [3.0.3] --socket [/tmp/mysql.sock] --port [3306] --plugindir [/usr/lib64/mariadb/plugin] --tlsinfo [OpenSSL 1.0.2k]

With the bug squashed, I can now enjoy my weekend.

Thanks again

W

Hi @ThomasB ,
do you have experience with Linux and postfix?
Looks like with postfix it’s possible:
https://serverfault.com/questions/277651/how-can-i-get-postfix-to-send-mail-to-different-relay-hosts
http://www.postfix.org/SASL_README.html#client_sasl_sender
If your server is at home, ensure you have at least VDSL connection and a dyndns Service.

best regards
Merlin

I am very sorry I did waste your time in this instance, I apologise for this.

The username was mispelt and I didn’t delete it after all.

Very very sorry, I am going to have a coffee and hopefully my mind will clear up!

Hi all,
put issue to solved.
I missed to changed the sources.list file. Sorry and big thank you.

Hint: It might be you have to uninstall php5-mapi via “dpkg --remove --force-depends php5-mapi”

Hi Thomas,

look this,
https://forum.kopano.io/post/1137

I am not receiving this error since uprading to version 8.4.90.550.

Regards
Richard

Hi @lars ,

no there is no “made by Kopano” gui to manage your server, but once you have set everything up your main task is anyway only user management (for which a wide variety of ldap based solutions exist already).

If you want to have a look into complete packages that integrate Kopano and user/config management then solutions like https://www.univention.com/products/univention-app-center/app-catalog/kopano-core/ and https://www.clearcenter.com/blogs/timeline/replace-microsoft-exchange-enhance-your-productivity-with-kopano could be interesting for you.