KopanoCore does not start after Upgrade from UCS 4.2 to 4.3 (cannot load mysql.proc)

UCS - Univention Corporate Server
, , ,
#1

Hi everyone,

Kopano does not work anymore. What can I try to narrow down the error?

cat /var/log/kopano/server.log shows the following result:

Wed Apr  4 01:03:04 2018: [ notice] Starting kopano-server version 8.4.5.0 (pid 4476)
Wed Apr  4 01:03:04 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Wed Apr  4 01:03:04 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Wed Apr  4 01:03:04 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Wed Apr  4 01:03:04 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Wed Apr  4 01:03:04 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Wed Apr  4 01:03:04 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Wed Apr  4 01:03:04 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Wed Apr  4 01:03:04 2018: [error  ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0.
Wed Apr  4 01:03:07 2018: [error  ] SQL [00000014] Failed: Cannot load from mysql.proc. The table is probably corrupted, Query Size: 33, Query: "DROP PROCEDURE IF EXISTS GetProps"
Wed Apr  4 01:03:07 2018: [error  ] KDatabase::I_Update() query failed: DROP PROCEDURE IF EXISTS GetProps: Cannot load from mysql.proc. The table is probably corrupted
Wed Apr  4 01:03:07 2018: [error  ] Can't initialize database settings
Wed Apr  4 01:03:07 2018: [ notice] Server shutdown complete.
#2

a similar issue was reported and then fixed in Kopano Crash nach Update auf UCS 4.3

#3

Thank you very much, it worked.

Mastodon