Kopano-Server startet nicht mehr nach update auf 8.6.2

kopano

#1

Ich habe gestern abend auf unserem Feuerwehr-Server UCS von 2.4-3 auf 3.0-0 upgedatet. Anschließend war dann noch das Kopano-Update dran. Nun startet der Kopano-Server nicht mehr. In der Log-Datei kommen folgende Meldungen:

Fri Jul  6 09:19:31 2018: [=======] Starting kopano-server version 8.6.2 (pid 8433)
Fri Jul  6 09:19:31 2018: [warning] Config warning: Option 'server_max_keep_alive_requests' is not used anymore.
Fri Jul  6 09:19:31 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Fri Jul  6 09:19:31 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Fri Jul  6 09:19:31 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Fri Jul  6 09:19:31 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Fri Jul  6 09:19:31 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Fri Jul  6 09:19:31 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Fri Jul  6 09:19:31 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Fri Jul  6 09:19:31 2018: [error  ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0. See kopano-coredump(5) for details.
Fri Jul  6 09:19:32 2018: [error  ] SQL [00000008] Failed: Duplicate entry 'x-ld-processed' for key 'gns', Query Size: 170, Query: "ALTER TABLE `names` ADD UNIQUE INDEX `gni` (`guid`(16), `nameid`), ADD UNIQUE INDEX `gns` (`guid`(16), `namestring`), DROP INDEX `guidnameid`, DROP INDEX `guidnamestring`"
Fri Jul  6 09:19:32 2018: [error  ] KDatabase::I_Update() query failed: "Duplicate entry 'x-ld-processed' for key 'gns'", query: ALTER TABLE `names` ADD UNIQUE INDEX `gni` (`guid`(16), `nameid`), ADD UNIQUE INDEX `gns` (`guid`(16), `namestring`), DROP INDEX `guidnameid`, DROP INDEX `guidnamestring`
Fri Jul  6 09:19:32 2018: [error  ] K-1216: Cannot update to schema v69, because the "names" table contains unexpected rows. Certain prior versions of the server erroneously allowed these duplicates to be added (KC-1108).
Fri Jul  6 09:19:32 2018: [error  ] K-1220: To fix the excess rows, use `kopano-dbadm k-1216`. Consult the manpage and preferably make a backup first.
Fri Jul  6 09:19:32 2018: [error  ] K-1221: Alternatively, the server may be started with --ignore-da to forego the schema update.
Fri Jul  6 09:19:32 2018: [warning] WARNING: Unable to upgrade database from version 8.6.2.0.68 to 8.6.2.0.70
Fri Jul  6 09:19:32 2018: [warning]    You can force the server to start with --ignore-database-version-conflict
Fri Jul  6 09:19:32 2018: [warning]    Warning, you can lose data! If you don't know what you're doing, you shouldn't be using this option!
Fri Jul  6 09:19:32 2018: [=======] Server shutdown complete.

Was kann ich denn da tun ?

LG
Helmut


#2

Huhu,

siehe https://kopano.com/releases/kopanocore-8-5-7/

Nachdem Sie das gelesen haben, sagt die Logdatei auch schon, wa szu tun ist:

Gruß
mosu


#3

Danke für die rasche Antwort :slight_smile:

Habe den angeführten Befehl jetzt durchgeführt. Der Kopano-Server startet noch immer nicht. Jetzt kommt die folgende Meldung:

Fri Jul  6 11:51:09 2018: [=======] Starting kopano-server version 8.6.2 (pid 3646)
Fri Jul  6 11:51:09 2018: [warning] Config warning: Option 'server_max_keep_alive_requests' is not used anymore.
Fri Jul  6 11:51:09 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Fri Jul  6 11:51:09 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Fri Jul  6 11:51:09 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Fri Jul  6 11:51:09 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Fri Jul  6 11:51:09 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Fri Jul  6 11:51:09 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Fri Jul  6 11:51:09 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Fri Jul  6 11:51:09 2018: [error  ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0. See kopano-coredump(5) for details.
Fri Jul  6 11:51:09 2018: [error  ] SQL [00000005] Failed: Cannot load from mysql.proc. The table is probably corrupted, Query Size: 33, Query: "DROP PROCEDURE IF EXISTS GetProps"
Fri Jul  6 11:51:09 2018: [error  ] KDatabase::I_Update() query failed: "Cannot load from mysql.proc. The table is probably corrupted", query: DROP PROCEDURE IF EXISTS GetProps
Fri Jul  6 11:51:09 2018: [error  ] Can't initialize database settings
Fri Jul  6 11:51:09 2018: [=======] Server shutdown complete.

Danke für die Hilfe!


#4

Dabei sollte wiederrum Kopano Crash nach Update auf UCS 4.3 helfen.


#5

Herzlichen Dank ! Das war es. Kopano läuft jetzt wieder.