Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicated key Primary #25

Open
IlPicasso opened this issue Mar 22, 2014 · 6 comments
Open

Duplicated key Primary #25

IlPicasso opened this issue Mar 22, 2014 · 6 comments

Comments

@IlPicasso
Copy link

I still get very frequently this error

http://pastebin.com/PP32CPcf

It does not affect me thought, but It would be awesome to see that fixed

@geNAZt
Copy link

geNAZt commented Mar 22, 2014

Have you OverwriteUUID to true ?

@IlPicasso
Copy link
Author

OverwriteUUID: true

Do not alter this. It will be used automaticly.

Yes it is

@geNAZt
Copy link

geNAZt commented Mar 22, 2014

So this is a offline mode server or why ? (It does not base on UUIDs). Can you post me a bit of your Players Table ? (With the structure)

@IlPicasso
Copy link
Author

It is an offline mode server

You mean this?

http://gyazo.com/31b564196890f0604cae9302a484996d

and structure
http://gyazo.com/8e5d2751e347b345f435627b6f24f859

@geNAZt
Copy link

geNAZt commented Mar 22, 2014

Yes thanks. This lookd correct

@Absentee23
Copy link

I got this error today as well on an ONLINE server (with OverwriteUUID set to false), and it caused homes to break for me. I found this was because a second player entry was added to the database with the correct name, but a UUID of NULL set for that player name in the players database.

So when that player tried to use homes, it was looking for the homes associated to UUID NULL

To fix, first I rolled back to jenkins build 54 (didn't try with 55, rolling back the version was my first attempt at a fix, I don't know if it made any difference in the following:), then I had to delete all the entries with NULL UUIDs (but NOT the original rows), then the affected players had to relog twice, on the first relog it would show:
LOADED DATA: Absentee23 0d06b99ee7844847bde2a9a51d4eb7cf true null null
The first "null" refers to the IP address. Homes still don't work at this point. On the NEXT login, it shows the IP correctly and homes are working again for that player.

There were some issues contacting the login servers earlier today, but I don't know if it is related. I also updated from gesuit build 53/54 (unsure) to 55 earlier today, again, unsure if related. Yamler 1.5.2 (hasn't changed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants