failuer when updating database from 8.6.81.0.78 to 8.6.81.0.102

tjoen

Look in table “names” with something like phpMyAdmin
Are there really two records with the same key “gns” ?
If the records are exactly the same then it should be possible to delete one of them.
WARNING: this is the theory, never done by me

Vogi

I already had a look - but I am not familiar with mysql, so I am not sure what is supposed to be double.

I found “gns” only once (see screenshot)
the doúble entry seems to be related to the guid (0x860…) but there are hundrets entries with same guid - so I am afraid that just deleting would make it worse…

tjoen

Google on mysql and gns results in this
https://forum.kopano.io/topic/1260/kopano-core-update-mysql-duplicated-entry

Vogi

@tjoen
Thanks for the hint.
I found the same google link and already ran

kopano-dbadm k-1216

This worked without failure. But afterwards the same error comes again.
So it seems, that this is a different issue

tjoen

gns is a strange index: it is composed of guid and namestring
Does select guid from names gives unique values? or are there double entries.
If there are then you can do select namestring guid from names where guid is that-double-value
(edited modified select namestring to select guid)

jengelh

Can you provide the mysqldump of the names table and send it to development @ kopano.io (or a service ticket) please.

mysqldump kopano names | xz >bla.xz

Vogi

I sent you the requested dump.
Thanks for your help!

tjoen

I wonder if my guess is right: there are two guids with the same value.
Solution would be to make guid unique index. Obsoleting gns and gni. Much simpler

jengelh

The GUIDs are not meant to be unique, not in this case anyway.

tjoen

gns is meant to be unique. With two same namestrings with same GUIDs there is a problem. Same with gni

jengelh

believed to be fixed with kopanocore-8.6.81-158-g352e88092

Vogi

Yes… I was able to start the kopano-server without any manual changes to the database
Thank you!