Kopano won't start after upgrade to 4.2

kopano

#1

After the upgrade from 4.1 to 4.2 Kopano core won’t start at boot and needs to be manually started ‘service kopano-core start’.

Also Kopano files with nextcloud (don’t now about others) isn’t working. it just keeps loading.

Thank you for your support


Kopano Server startet sporadisch nicht richtig
Fehler nach Upgrade 4.2: Kopano startet nicht mehr
#2

Hi @stevenr,

the thing about kopano not starting after the upgrade already came up in Fehler nach Upgrade 4.2: Kopano startet nicht mehr, but up until now i was not able to reproduce this locally so its still unclear what could be wrong (although the last reply with the connection of not waiting long enough for mysql sounds plausible).

for the files plugin i only know about Kopano WebApp File Integration Error in relation to Univention.


#3

Thank you for your reply.

I wonder if it is possible to uninstall Kopano Core and reïnstall to solve this. Might try on our test system.

What would happen with the mailstores, would they become orphaned?

For now we keep starting the service manually each reboot.


#4

Hi,

Did a reinstall of Kopano Core many times on UCS (you’ll have to remove webapp webmeeting and z-push first, and you wont lose any config also the ldap users won’t be touched so you don’t get orphaned stores.

But best to try on test system first for sure.

rg
Christian


#5

What is the output of systemctl status kopano-server.service after a reboot, when the kopano-server is not running?
It should be similar to this (i added the * for pointing out the relevant info):

● kopano-server.service - Kopano Core Storage Server
   Loaded: *loaded* (/lib/systemd/system/kopano-server.service; *enabled*)
   Active: *active (running)* since Mi 2017-07-05 09:21:51 CEST; 1h 8min ago
     Docs: man:kopano-server(8)
           man:kopano-server.cfg(5)
           man:kopano-admin(8)
 Main PID: 2017 (kopano-server)
   CGroup: /system.slice/kopano-server.service
           └─2017 /usr/sbin/kopano-server -F

Jul 05 09:21:51 master systemd[1]: Starting Kopano Core Storage Server...
Jul 05 09:21:51 master systemd[1]: Started Kopano Core Storage Server.

The output of systemctl list-units | grep kopano and dpkg -l | grep kopano might also be helpful.


#6

I’m also updating another server from 4.1 to 4.2 with Kopano as we speak.

I’ll try to replicate the problem. If it works with this server I’ll get the info from the other server with the existing problem.


#7

Update: When I upgraded the other (test) 4.1 server to 4.2 (latest errate today) I can’t update/upgrade Kopano to the latest version. It says there is an update, but when I go to the app center there is no link to upgrade Kopano Core (there is for webapp & z-push).

I’m now fully uninstalling Kopano and reinstall to see what happens.

Update 2: All is working now after reinstalling Kopano on the ‘test’ server. Going to try this on the production server the next maintenance.

Update 3: to bad, it doesn’t work. After another reboot (after installing and configuring Let’s encrypt, don’t know if related?), Kopano-core won’t start anymore.

systemctl status kopano-server.service -l
● kopano-server.service - Kopano Core Storage Server
Loaded: loaded (/lib/systemd/system/kopano-server.service; enabled)
Active: failed (Result: exit-code) since do 2017-07-06 15:38:50 CEST; 7min ago
Docs: man:kopano-server(8)
man:kopano-server.cfg(5)
man:kopano-admin(8)
Process: 1935 ExecStart=/usr/sbin/kopano-server -F (code=exited, status=255)
Main PID: 1935 (code=exited, status=255)

jul 06 15:38:46 dc systemd[1]: Starting Kopano Core Storage Server…
jul 06 15:38:46 dc systemd[1]: Started Kopano Core Storage Server.
jul 06 15:38:50 dc kopano-server[1935]: An error occurred (80000007). Please check /var/log/kopano/server.log for details.
jul 06 15:38:50 dc systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
jul 06 15:38:50 dc systemd[1]: Unit kopano-server.service entered failed state.


#8

Please check /var/log/kopano/server.log at the time of booting the machine (jul 06 15:38:50). Is there a reason visible why the server failed to start? Maybe it is a subtle timing issue with another service.


#9

Here is the whole log. It certainly looks like Kopano wants to start to early before mysql and ldap are active.

Sun Jul 2 06:25:34 2017: [error ] Previous message logged 88 times
Sun Jul 2 06:25:34 2017: [warning] Log connection was reset
Sun Jul 2 06:25:58 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Sun Jul 2 10:57:57 2017: [error ] Previous message logged 100 times
Sun Jul 2 10:57:57 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Sun Jul 2 11:12:32 2017: [error ] Previous message logged 9 times
Sun Jul 2 11:12:32 2017: [warning] SQL [00000903] info: Try to reconnect
Sun Jul 2 11:29:57 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Sun Jul 2 15:22:10 2017: [error ] Previous message logged 100 times
Sun Jul 2 15:22:10 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Sun Jul 2 18:39:14 2017: [error ] Previous message logged 100 times
Sun Jul 2 18:39:14 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Sun Jul 2 21:56:31 2017: [error ] Previous message logged 100 times
Sun Jul 2 21:56:31 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Sun Jul 2 23:55:16 2017: [error ] Previous message logged 63 times
Sun Jul 2 23:55:16 2017: [warning] SQL [00000358] info: Try to reconnect
Sun Jul 2 23:55:16 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:16 2017: [error ] ECDatabaseMySQL::DoSelect(): query failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:16 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:16 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:21 2017: [warning] SQL [00000356] info: Try to reconnect
Sun Jul 2 23:55:21 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:21 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:21 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:26 2017: [warning] SQL [00000357] info: Try to reconnect
Sun Jul 2 23:55:26 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:26 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:26 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:31 2017: [warning] SQL [00000359] info: Try to reconnect
Sun Jul 2 23:55:31 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:31 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:31 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:36 2017: [warning] SQL [00000355] info: Try to reconnect
Sun Jul 2 23:55:36 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:36 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:36 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:41 2017: [warning] SQL [00000354] info: Try to reconnect
Sun Jul 2 23:55:41 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:41 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:41 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:46 2017: [warning] SQL [00000360] info: Try to reconnect
Sun Jul 2 23:55:46 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:46 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:46 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:51 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:51 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:51 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:51 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:56 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:56 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:55:56 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:55:56 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:01 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:01 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:01 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:01 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:06 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:06 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:06 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:06 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:11 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:11 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:11 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:11 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:16 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:16 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:16 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:16 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:21 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:21 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:21 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:21 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:26 2017: [warning] SQL [00000361] info: Try to reconnect
Sun Jul 2 23:56:26 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:26 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:26 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:31 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:31 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:31 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:31 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:36 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:36 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:36 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:36 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:41 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:41 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:41 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:41 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:46 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:46 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:46 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:46 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:51 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:51 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:51 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:51 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:56 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:56 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:56:56 2017: [warning] SQL [00000000] info: Try to reconnect
Sun Jul 2 23:56:56 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Sun Jul 2 23:57:01 2017: [warning] SQL [00000000] info: Try to reconnect
Mon Jul 3 00:00:06 2017: [warning] Previous message logged 7 times
Mon Jul 3 00:00:06 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Mon Jul 3 00:00:44 2017: [warning] SQL [00000352] info: Try to reconnect
Mon Jul 3 00:06:18 2017: [warning] Shutting down
Mon Jul 3 00:06:26 2017: [ notice] Server shutdown complete.
Mon Jul 3 00:09:17 2017: [ notice] Starting server version 8,1,1,10, pid 4172
Mon Jul 3 00:23:38 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Mon Jul 3 14:00:05 2017: [error ] Previous message logged 99 times
Mon Jul 3 14:00:05 2017: [warning] SQL [00000051] info: Try to reconnect
Mon Jul 3 14:15:00 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Mon Jul 3 16:23:43 2017: [error ] Previous message logged 22 times
Mon Jul 3 16:23:43 2017: [warning] SQL [00000040] info: Try to reconnect
Mon Jul 3 16:39:48 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Mon Jul 3 18:21:31 2017: [error ] Previous message logged 48 times
Mon Jul 3 18:21:31 2017: [warning] SQL [00000050] info: Try to reconnect
Mon Jul 3 18:45:02 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Tue Jul 4 00:15:11 2017: [error ] Previous message logged 100 times
Tue Jul 4 00:15:11 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Tue Jul 4 03:16:08 2017: [error ] Previous message logged 100 times
Tue Jul 4 03:16:08 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Tue Jul 4 08:14:34 2017: [error ] Previous message logged 100 times
Tue Jul 4 08:14:34 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Tue Jul 4 12:10:37 2017: [error ] Previous message logged 100 times
Tue Jul 4 12:10:37 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Tue Jul 4 16:02:58 2017: [error ] Previous message logged 86 times
Tue Jul 4 16:02:58 2017: [warning] SQL [00000183] info: Try to reconnect
Tue Jul 4 16:15:01 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Tue Jul 4 20:42:57 2017: [error ] Previous message logged 100 times
Tue Jul 4 20:42:57 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 00:53:52 2017: [error ] Previous message logged 100 times
Wed Jul 5 00:53:52 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 04:03:28 2017: [error ] Previous message logged 100 times
Wed Jul 5 04:03:28 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 07:44:22 2017: [error ] Previous message logged 100 times
Wed Jul 5 07:44:22 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 10:24:01 2017: [error ] Previous message logged 79 times
Wed Jul 5 10:24:01 2017: [warning] SQL [00000349] info: Try to reconnect
Wed Jul 5 10:41:54 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 14:20:24 2017: [error ] Previous message logged 99 times
Wed Jul 5 14:20:24 2017: [warning] Authentication by plugin failed for user “Administrator”: Trying to authenticate failed: Administrator not found in LDAP; username = Administrator
Wed Jul 5 14:20:24 2017: [warning] Failed to authenticate user “Administrator” from “192.168.1.60” using program “apache2”
Wed Jul 5 14:20:38 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 14:48:44 2017: [error ] Previous message logged 5 times
Wed Jul 5 14:48:44 2017: [warning] Shutting down
Wed Jul 5 14:48:47 2017: [ notice] Server shutdown complete.
Wed Jul 5 14:48:48 2017: [ notice] Starting server version 8,1,2,1, pid 22675
Wed Jul 5 14:51:10 2017: [warning] Shutting down
Wed Jul 5 14:51:16 2017: [ notice] Server shutdown complete.
Wed Jul 5 14:51:18 2017: [ notice] Starting server version 8,1,2,1, pid 23859
Wed Jul 5 15:11:05 2017: [warning] SQL [00000596] info: Try to reconnect
Wed Jul 5 15:11:05 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Wed Jul 5 15:11:05 2017: [warning] SQL [00000000] info: Try to reconnect
Wed Jul 5 15:11:05 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Wed Jul 5 15:11:06 2017: [warning] SQL [00000589] info: Try to reconnect
Wed Jul 5 15:11:06 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Wed Jul 5 15:11:06 2017: [error ] ECDatabaseMySQL::DoSelect(): query failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Wed Jul 5 15:11:06 2017: [warning] SQL [00000000] info: Try to reconnect
Wed Jul 5 15:11:06 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Wed Jul 5 15:11:06 2017: [error ] ECDatabaseMySQL::DoSelect(): query failed: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Wed Jul 5 15:11:06 2017: [warning] Writeout of logon/off time cache unsuccessful
Wed Jul 5 15:11:10 2017: [warning] SQL [00000591] info: Try to reconnect
Wed Jul 5 15:11:11 2017: [warning] SQL [00000000] info: Try to reconnect
Wed Jul 5 15:11:16 2017: [warning] SQL [00000598] info: Try to reconnect
Wed Jul 5 15:11:16 2017: [warning] SQL [00000595] info: Try to reconnect
Wed Jul 5 15:11:21 2017: [warning] SQL [00000597] info: Try to reconnect
Wed Jul 5 15:11:21 2017: [warning] SQL [00000592] info: Try to reconnect
Wed Jul 5 15:11:26 2017: [warning] SQL [00000594] info: Try to reconnect
Wed Jul 5 15:11:26 2017: [warning] SQL [00000593] info: Try to reconnect
Wed Jul 5 15:15:00 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:15:00 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:15:00 2017: [warning] Unable to get quota for user: Failure connecting any of the LDAP servers
Wed Jul 5 15:18:41 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:18:41 2017: [warning] Authentication by plugin failed for user “steven”: Trying to authenticate failed: Failure connecting any of the LDAP servers; username = steven
Wed Jul 5 15:18:41 2017: [warning] Failed to authenticate user “steven” from “file:///var/run/kopano/server.sock” using program “apache2”
Wed Jul 5 15:18:41 2017: [warning] SQL [00000000] info: Try to reconnect
Wed Jul 5 15:18:42 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 15:18:42 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:18:42 2017: [warning] Authentication by plugin failed for user “steven”: Trying to authenticate failed: Failure connecting any of the LDAP servers; username = steven
Wed Jul 5 15:18:42 2017: [warning] Failed to authenticate user “steven” from “file:///var/run/kopano/server.sock” using program “apache2”
Wed Jul 5 15:23:43 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 15:23:43 2017: [warning] LDAP (simple) bind failed: Can’t contact LDAP server
Wed Jul 5 15:23:43 2017: [warning] Authentication by plugin failed for user “steven”: Trying to authenticate failed: Failure connecting any of the LDAP servers; username = steven
Wed Jul 5 15:23:43 2017: [warning] Failed to authenticate user “steven” from “file:///var/run/kopano/server.sock” using program “apache2”
Wed Jul 5 15:28:47 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 15:37:40 2017: [error ] Previous message logged 2 times
Wed Jul 5 15:37:40 2017: [warning] Shutting down
Wed Jul 5 15:37:42 2017: [ notice] Server shutdown complete.
Wed Jul 5 15:37:43 2017: [ notice] Starting server version 8,2,1,530, pid 6626
Wed Jul 5 16:34:42 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 22:14:41 2017: [error ] Previous message logged 100 times
Wed Jul 5 22:14:41 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Wed Jul 5 23:56:56 2017: [error ] Previous message logged 30 times
Wed Jul 5 23:56:56 2017: [warning] Shutting down
Wed Jul 5 23:56:58 2017: [ notice] Server shutdown complete.
Wed Jul 5 23:58:21 2017: [ notice] Starting server version 8,2,1,530, pid 2073
Thu Jul 6 00:58:10 2017: [warning] LDAP (simple) bind failed: Invalid credentials
Thu Jul 6 00:58:10 2017: [warning] Authentication by plugin failed for user “steven”: Trying to authenticate failed: Failure connecting any of the LDAP servers; username = steven
Thu Jul 6 00:58:10 2017: [warning] Failed to authenticate user “steven” from “file:///var/run/kopano/server.sock” using program “apache2”
Thu Jul 6 02:19:38 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Thu Jul 6 10:10:31 2017: [error ] Previous message logged 81 times
Thu Jul 6 10:10:31 2017: [warning] Shutting down
Thu Jul 6 10:10:38 2017: [ notice] Server shutdown complete.
Thu Jul 6 10:13:22 2017: [ notice] Starting server version 8,2,1,530, pid 1966
Thu Jul 6 10:13:23 2017: [error ] ECDatabaseMySQL::Connect(): mysql connect fail: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Thu Jul 6 10:13:23 2017: [crit ] Unable to connect to database: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Thu Jul 6 10:13:23 2017: [ notice] Server shutdown complete.
Thu Jul 6 13:33:53 2017: [ notice] Starting server version 8,3,1,35, pid 32171
Thu Jul 6 13:34:24 2017: [warning] Shutting down
Thu Jul 6 13:34:26 2017: [ notice] Server shutdown complete.
Thu Jul 6 13:34:27 2017: [ notice] Starting server version 8,3,1,35, pid 355
Thu Jul 6 13:34:31 2017: [error ] createStore(): already exists
Thu Jul 6 13:34:31 2017: [error ] Failed to create store (id=1), errorcode=0x80000008
Thu Jul 6 13:34:47 2017: [warning] Shutting down
Thu Jul 6 13:34:49 2017: [ notice] Server shutdown complete.
Thu Jul 6 13:34:49 2017: [ notice] Starting server version 8,3,1,35, pid 840
Thu Jul 6 13:45:22 2017: [warning] LDAP (simple) bind failed: Invalid credentials
Thu Jul 6 13:45:22 2017: [warning] Authentication by plugin failed for user “steven”: Trying to authenticate failed: Failure connecting any of the LDAP servers; username = steven
Thu Jul 6 13:45:22 2017: [warning] Failed to authenticate user “steven” from “file:///var/run/kopano/server.sock” using program “apache2”
Thu Jul 6 14:27:48 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Thu Jul 6 15:21:20 2017: [error ] Previous message logged 29 times
Thu Jul 6 15:21:20 2017: [warning] Shutting down
Thu Jul 6 15:21:26 2017: [ notice] Server shutdown complete.
Thu Jul 6 15:23:14 2017: [ notice] Starting server version 8,3,1,35, pid 1952
Thu Jul 6 15:35:29 2017: [error ] LDAP search error: Can’t contact LDAP server. Will unbind, reconnect and retry.
Thu Jul 6 15:36:58 2017: [warning] Shutting down
Thu Jul 6 15:37:00 2017: [ notice] Server shutdown complete.
Thu Jul 6 15:38:48 2017: [ notice] Starting server version 8,3,1,35, pid 1935
Thu Jul 6 15:38:50 2017: [error ] KDatabase::Connect(): database access error -2147483641, mysql error: Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)
Thu Jul 6 15:38:50 2017: [crit ] Unable to connect to database: MYSQL not initialized
Thu Jul 6 15:38:50 2017: [ notice] Server shutdown complete.
Thu Jul 6 15:49:44 2017: [ notice] Starting server version 8,3,1,35, pid 3690


#10
Thu Jul 6 15:38:48 2017: [ notice] Starting server version 8,3,1,35, pid 1935
Thu Jul 6 15:38:50 2017: [error ] KDatabase::Connect(): database access error -2147483641, mysql error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Thu Jul 6 15:38:50 2017: [crit ] Unable to connect to database: MYSQL not initialized

The kopano-server could not start because the connection to the MySQL server failed. It seems as if the MySQL server was not ready to accept connection at that time, maybe the service was not fully running. That would explain why the manual start of kopano-server after the server boot works.

The kopano-server service definition should have a dependency to run after the mysql server, is that the case on your system?
systemctl show kopano-server.service
What does the service dependency chain to boot the kopano-server look like on your server?
systemd-analyze critical-chain kopano-server.service
Are there any warnings or errors in the mysql boot log?
journalctl -u mysql.service

You can see by these questions that this issue is hard to debug in the forum. An official support case would make it possible to debug it in depth on your server with a remote session.


#11

We have the same problem with Kopano not starting after the upgrade, exists on two different systems.

With regards the Kopano-files plugin, see this post in the Kopano forum. The fix worked for us.


Kopano don't start automatically on reboot
#12

We analyzed the issue in a support case. The problem in that specific case was, that the wrong mysql-server package version was installed. We currently have an issue where the mysql-server package for UCS 4.1 errata is newer than in UCS 4.2.

To get the currently installed version, the output of e.g. apt-cache policy mysql-server should be checked. If the installed package on your UCS 4.2 system is not from a UCS 4.2 repository, the mysql-server daemon init script will not wait long enough for the mysql process to start up.

An updated mysql-server erratum for UCS 4.2-1 will be relased soon. In the meantime, apt-get install mysql-server=5.5.54-0.A~4.2.0.201703071716 mysql-server-5.5=5.5.54-0.A~4.2.0.201703071716 will install the correct mysql-server version for UCS 4.2


Fehler nach Upgrade 4.2: Kopano startet nicht mehr
#13

Thank you damrose, it is working after we’ve had installed the correct msql-server as per your suggestion!

This problem is solved :smile:


#14

We have exactly the same problem again after Upgrade to 4.2-2 (errata level 189). The installed mysql package is 5.5.57-0.A~4.2.1.201708021657

~# apt-cache policy mysql-server
mysql-server:
  Installiert:           5.5.57-0.A~4.2.1.201708021657
  Installationskandidat: 5.5.57-0.A~4.2.1.201708021657
  Versionstabelle:
 *** 5.5.57-0.A~4.2.1.201708021657 0
        500 https://updates.software-univention.de/4.2/maintained/ 4.2-2/all/ Packages
        100 /var/lib/dpkg/status
     5.5.57-0.33.201707311954 0
        500 https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/all/ Packages
     5.5.55-0.29.201705021645 0
        500 https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/all/ Packages
     5.5.54-0.A~4.2.0.201703071716 0
        500 https://updates.software-univention.de/4.2/maintained/ 4.2-0/all/ Packages
     5.5.54-0.27.201701251948 0
        500 https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/all/ Packages
     5.5.53-0.26.201611161616 0
        500 https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/all/ Packages
     5.5.52-0.25.201609281418 0
        500 https://updates.software-univention.de/4.1/maintained/ 4.1-4/all/ Packages
     5.5.46-0.17.201512141630 0
        500 https://updates.software-univention.de/4.1/maintained/ 4.1-1/all/ Packages
     5.5.46-0.16.201512141629 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-5/all/ Packages
        500 https://updates.software-univention.de/4.0/maintained/component/ 4.0-4-errata/all/ Packages
     5.5.44-0.15.201508042121 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-3/all/ Packages
     5.5.40-0.14.201502051002 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-1/all/ Packages
     5.5.40-0.11.201411010605 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-0/all/ Packages
     5.1.73-1.41.201505131105 0
        500 https://updates.software-univention.de/3.2/maintained/component/ 3.2-5-errata/all/ Packages

#15

Is it really the same issue? Please check your system for the following details and post anything that may help to debug the problem.


Kopano Server startet sporadisch nicht richtig
#16

I have the same problem and my kopano didn´t start with the reboot of the machine. Here are the details:

/lib/systemd/system/kopano-server.service


[Unit]
Description=Kopano Core Storage Server
Documentation=man:kopano-server(8) man:kopano-server.cfg(5) man:kopano-admin(8)
After=network.target mysql.service mariadb.service
Wants=mysql.service

[Service]
Type=simple
Environment=LC_ALL=C LANG=C
ExecStart=/usr/sbin/kopano-server -F
ExecReload=/bin/kill -HUP $MAINPID
TimeoutStopSec=60

[Install]
WantedBy=multi-user.target

/var/log/kopano/server.log

Thu Jan  4 07:56:17 2018: [ notice] Starting kopano-server version 8.4.5.0 (pid 2437)
Thu Jan  4 07:56:17 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Thu Jan  4 07:56:17 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Thu Jan  4 07:56:17 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Thu Jan  4 07:56:17 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Thu Jan  4 07:56:17 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Thu Jan  4 07:56:17 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Thu Jan  4 07:56:17 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Thu Jan  4 07:56:19 2018: [error  ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0.
Thu Jan  4 07:56:19 2018: [error  ] KDatabase::Connect(): database access error Unknown error code (0x80000007), mysql error: Can't connect to local MySQL server through so$
Thu Jan  4 07:56:19 2018: [crit   ] Unable to connect to database: MYSQL not initialized
Thu Jan  4 07:56:19 2018: [ notice] Server shutdown complete.
Thu Jan  4 08:02:38 2018: [ notice] Starting kopano-server version 8.4.5.0 (pid 4507)
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Thu Jan  4 08:02:39 2018: [error  ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0.
Thu Jan  4 08:03:42 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"

systemd-analyze critical-chain kopano-server.service

root@ucs002090:~# systemd-analyze critical-chain kopano-server.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

kopano-server.service @1min 17.664s
ââbasic.target @36.588s
  ââsockets.target @36.587s
    ââclamav-daemon.socket @36.554s +33ms
      ââsysinit.target @36.552s
        âânfs-common.service @35.801s +750ms
          âârpcbind.target @35.800s
            âârpcbind.service @35.527s +271ms
              âânetwork-online.target @35.526s
                âânetwork.target @35.526s
                  âânetworking.service @10.330s +25.195s
                    ââlocal-fs.target @10.325s
                      ââproc-fs-nfsd.mount @2min 43.197s
                        ââlocal-fs-pre.target @6.511s
                          ââsystemd-remount-fs.service @6.182s +87ms
                            ââkeyboard-setup.service @4.631s +1.547s
                              ââsystemd-udevd.service @4.614s +14ms
                                ââsystemd-tmpfiles-setup-dev.service @3.658s +954ms
                                  ââkmod-static-nodes.service @3.204s +452ms
                                    ââsystem.slice @3.122s
                                      ââ-.slice @3.120s

journalctl -u mysql.service

Jan 04 07:55:33 ucs002090 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jan 04 07:56:14 ucs002090 mysql[1001]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jan 04 07:56:14 ucs002090 systemd[1]: mysql.service: control process exited, code=exited status=1
Jan 04 07:56:14 ucs002090 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jan 04 07:56:14 ucs002090 systemd[1]: Unit mysql.service entered failed state.


#17

The mysql-server is not in the critical chain to the kopano-server service. Which mysql-server package is installed? apt-cache policy mysql-server (i added that in my above answer)
Does the mysql-server start if you try to do it manually? service mysql-server start


#18
root@ucs002090:~# apt-cache policy mysql-server
mysql-server:
  Installiert:           5.5.57-0.A~4.2.1.201708021657
  Installationskandidat: 5.5.57-0.A~4.2.1.201708021657
  Versionstabelle:
 *** 5.5.57-0.A~4.2.1.201708021657 0
        500 https://updates.software-univention.de/4.2/maintained/ 4.2-2/all/ Packages
        100 /var/lib/dpkg/status
     5.5.57-0.33.201707311954 0
        500 https://updates.software-univention.de/4.1/maintained/ 4.1-5/all/ Packages
     5.5.54-0.A~4.2.0.201703071716 0
        500 https://updates.software-univention.de/4.2/maintained/ 4.2-0/all/ Packages
     5.5.52-0.25.201609281418 0
        500 https://updates.software-univention.de/4.1/maintained/ 4.1-4/all/ Packages
     5.5.46-0.17.201512141630 0
        500 https://updates.software-univention.de/4.1/maintained/ 4.1-1/all/ Packages
     5.5.46-0.16.201512141629 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-5/all/ Packages
     5.5.44-0.15.201508042121 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-3/all/ Packages
     5.5.40-0.14.201502051002 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-1/all/ Packages
     5.5.40-0.11.201411010605 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-0/all/ Packages

I think, that mysql starts by rebooting - but a little bit to slow. I didn´t must start mysql after a reboot. I only execute kopano-server start and then it works fine


#19

I noticed the problem again this morning.
http://help.univention.com/t/kopano-server-startet-sporadisch-nicht-richtig/7668/4.
After a first reboot, the error happend again. After the second reboot the system worked ok.

systemctl list-units | grep kopano
  kopano-dagent.service                                                                       loaded active running   Kopano Core Delivery Agent
  kopano-gateway.service                                                                      loaded active running   Kopano Core IMAP/POP3 Gateway
  kopano-ical.service                                                                         loaded active running   Kopano Core iCal/CalDAV Gateway
  kopano-monitor.service                                                                      loaded active running   Kopano Core Quota Manager
  kopano-presence.service                                                                     loaded active running   Kopano Core Presence Daemon
  kopano-search.service                                                                       loaded active running   Kopano Core Search Engine
● kopano-server.service                                                                       loaded failed failed    Kopano Core Storage Server
  kopano-spooler.service                                                                      loaded active running   Kopano Core Spooler

 systemctl status kopano-server.service
● kopano-server.service - Kopano Core Storage Server
   Loaded: loaded (/lib/systemd/system/kopano-server.service; enabled)
   Active: failed (Result: exit-code) since Di 2018-01-23 07:07:16 CET; 50min ago
     Docs: man:kopano-server(8)
           man:kopano-server.cfg(5)
           man:kopano-admin(8)
  Process: 2751 ExecStart=/usr/sbin/kopano-server -F (code=exited, status=255)
 Main PID: 2751 (code=exited, status=255)

Jan 23 07:07:15 ucs-1 systemd[1]: Started Kopano Core Storage Server.
Jan 23 07:07:16 ucs-1 kopano-server[2751]: An error occurred (80000007). Please check /var/log/kopano/server.log for details.
Jan 23 07:07:16 ucs-1 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Jan 23 07:07:16 ucs-1 systemd[1]: Unit kopano-server.service entered failed state.
cat /var/log/kopano/server.log

Tue Jan 23 07:07:15 2018: [ notice] Starting server version 8,3,1,35, pid 2751
Tue Jan 23 07:07:16 2018: [error  ] KDatabase::Connect(): database access error -2147483641, mysql error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Tue Jan 23 07:07:16 2018: [crit   ] Unable to connect to database: MYSQL not initialized
Tue Jan 23 07:07:16 2018: [ notice] Server shutdown complete.
journalctl -u mysql.service

Jan 23 07:06:36 ucs-1 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jan 23 07:07:15 ucs-1 mysql[1117]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jan 23 07:07:15 ucs-1 systemd[1]: mysql.service: control process exited, code=exited status=1
Jan 23 07:07:15 ucs-1 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jan 23 07:07:15 ucs-1 systemd[1]: Unit mysql.service entered failed state.
-- Reboot --
Jan 23 08:08:34 ucs-1 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jan 23 08:09:11 ucs-1 mysql[1119]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jan 23 08:09:11 ucs-1 systemd[1]: mysql.service: control process exited, code=exited status=1
Jan 23 08:09:11 ucs-1 systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jan 23 08:09:11 ucs-1 systemd[1]: Unit mysql.service entered failed state.
-- Reboot --
Jan 23 08:11:26 ucs-1 systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Jan 23 08:12:03 ucs-1 mysql[1133]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Jan 23 08:12:03 ucs-1 mysql[1133]: Checking for tables which need an upgrade, are corrupt or were
Jan 23 08:12:03 ucs-1 mysql[1133]: not closed cleanly..
Jan 23 08:12:03 ucs-1 systemd[1]: Started LSB: Start and stop the mysql database server daemon.

systemd-analyze critical-chain kopano-server.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

kopano-server.service @59.930s
└─basic.target @19.024s
  └─sockets.target @19.024s
    └─clamav-daemon.socket @19.019s +4ms
      └─sysinit.target @19.018s
        └─nfs-common.service @18.501s +517ms
          └─rpcbind.target @18.501s
            └─rpcbind.service @18.318s +182ms
              └─network-online.target @18.317s
                └─network.target @18.317s
                  └─networking.service @7.194s +11.122s
                    └─local-fs.target @7.192s
                      └─proc-fs-nfsd.mount @1min 3.528s
                        └─local-fs-pre.target @5.900s
                          └─systemd-remount-fs.service @5.458s +291ms
                            └─keyboard-setup.service @4.033s +1.422s
                              └─systemd-udevd.service @3.987s +45ms
                                └─systemd-tmpfiles-setup-dev.service @3.335s +651ms
                                  └─kmod-static-nodes.service @2.993s +340ms
                                    └─system.slice @2.956s
apt-cache policy mysql-server
mysql-server:
  Installiert:           5.5.57-0.A~4.2.1.201708021657
  Installationskandidat: 5.5.57-0.A~4.2.1.201708021657
  Versionstabelle:
 *** 5.5.57-0.A~4.2.1.201708021657 0
        500 https://updates.software-univention.de/4.2/maintained/ 4.2-2/all/ Packages
        100 /var/lib/dpkg/status
     5.5.57-0.33.201707311954 0
        500 https://updates.software-univention.de/4.1/maintained/ 4.1-5/all/ Packages
        500 https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/all/ Packages
     5.5.55-0.29.201705021645 0
        500 https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/all/ Packages
     5.5.54-0.A~4.2.0.201703071716 0
        500 https://updates.software-univention.de/4.2/maintained/ 4.2-0/all/ Packages
     5.5.54-0.27.201701251948 0
        500 https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/all/ Packages
     5.5.53-0.26.201611161616 0
        500 https://updates.software-univention.de/4.1/maintained/component/ 4.1-4-errata/all/ Packages
     5.5.52-0.25.201609281418 0
        500 https://updates.software-univention.de/4.1/maintained/ 4.1-4/all/ Packages
     5.5.46-0.17.201512141630 0
        500 https://updates.software-univention.de/4.1/maintained/ 4.1-1/all/ Packages
     5.5.46-0.16.201512141629 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-5/all/ Packages
     5.5.44-0.15.201508042121 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-3/all/ Packages
     5.5.40-0.14.201502051002 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-1/all/ Packages
     5.5.40-0.11.201411010605 0
        500 https://updates.software-univention.de/4.0/maintained/ 4.0-0/all/ Packages

Kopano failing ldap bind to MS Server 2016 AD [Solved]
#20

The MySQL init script simply waits for 30 seconds for the daemon to be available. Maybe the installation is too large. Does the situation improve if the wait time is increased? To do that, edit /etc/init.d/mysql at line 118:
for i in $(seq 1 30); do
replace the 30 with a higher value, e.g. 60.