Essentials
Essentials copied to clipboard
EssentialsX
Found UUID x but player already has a UUID x. Not replacing UUID in usermap.
Type of bug
Error in console
/ess version output
I know you would ask if server is online or offline mode, the server is offline mode because I am using waterfall, the waterfall it self is online mode, and I am using Bungeeguard and ip tables to prevent non premium players from joining my back end, so there is no way these users could have double UUIDS, the only thing I can think of is NPCs "Citizens 2" because for a fact when someone donates they get an NPC that looks like them to show on spawn, but well most of the users showing this error when they login never donated. I am confused but tying to give leads.
Error log (if applicable)
No response
Bug description
[16:39:11 INFO]: [Essentials] Found UUID f51219be-6192-4bbe-a849-55a063b71643 for player vietnamfortnite, but player already has a UUID (a5e7bf09-bf65-4ced-8a30-1069756ba265). Not replacing UUID in usermap. java.lang.RuntimeException: null at com.earth2me.essentials.UserMap.trackUUID(UserMap.java:141) ~[?:?] at com.earth2me.essentials.UserMap.load(UserMap.java:168) ~[?:?] at com.earth2me.essentials.UserMap.load(UserMap.java:30) ~[?:?] at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3716) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2424) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2298) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2211) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache.get(LocalCache.java:4154) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4158) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:5147) ~[patched_1.17.1.jar:git-Paper-96] at com.earth2me.essentials.UserMap.getUser(UserMap.java:118) ~[?:?] at com.earth2me.essentials.BalanceTopImpl.calculateBalanceTopMap(BalanceTopImpl.java:32) ~[?:?] at org.bukkit.craftbukkit.v1_17_R1.scheduler.CraftTask.run(CraftTask.java:100) ~[patched_1.17.1.jar:git-Paper-96] at org.bukkit.craftbukkit.v1_17_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:54) ~[patched_1.17.1.jar:git-Paper-96] at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[patched_1.17.1.jar:git-Paper-96] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) ~[?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) ~[?:?] at java.lang.Thread.run(Thread.java:831) [?:?]
Steps to reproduce
When user logs in this keeps showing on console spamming.
Expected behaviour
Expected not to show errors on console
Actual behaviour
[16:39:11 INFO]: [Essentials] Found UUID f51219be-6192-4bbe-a849-55a063b71643 for player vietnamfortnite, but player already has a UUID (a5e7bf09-bf65-4ced-8a30-1069756ba265). Not replacing UUID in usermap. java.lang.RuntimeException: null at com.earth2me.essentials.UserMap.trackUUID(UserMap.java:141) ~[?:?] at com.earth2me.essentials.UserMap.load(UserMap.java:168) ~[?:?] at com.earth2me.essentials.UserMap.load(UserMap.java:30) ~[?:?] at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3716) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2424) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2298) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2211) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache.get(LocalCache.java:4154) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4158) ~[patched_1.17.1.jar:git-Paper-96] at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:5147) ~[patched_1.17.1.jar:git-Paper-96] at com.earth2me.essentials.UserMap.getUser(UserMap.java:118) ~[?:?] at com.earth2me.essentials.BalanceTopImpl.calculateBalanceTopMap(BalanceTopImpl.java:32) ~[?:?] at org.bukkit.craftbukkit.v1_17_R1.scheduler.CraftTask.run(CraftTask.java:100) ~[patched_1.17.1.jar:git-Paper-96] at org.bukkit.craftbukkit.v1_17_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:54) ~[patched_1.17.1.jar:git-Paper-96] at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[patched_1.17.1.jar:git-Paper-96] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) ~[?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) ~[?:?] at java.lang.Thread.run(Thread.java:831) [?:?]
Your usermap is polluted with incorrect UUIDs. Could you try stopping your server, renaming plugins/Essentials/usermap.csv to usermap.csv.bak, and starting your server back up?
I have done that, the issue is still there, done it before posting here as I found this solution on another similiar issue about poisned uuids. didn't fix my problem, which is so wierd. it just generates a new file, than from the first boot up the issue start again.
Your usermap is polluted with incorrect UUIDs. Could you try stopping your server, renaming
plugins/Essentials/usermap.csvtousermap.csv.bak, and starting your server back up?
Any other solution or tool to fix the pollution.
@antibitcoin I had the same issue. I just deleted all the userfiles in question. (The files matching the second UUID mentioned in the error message) and then at the end deleting usermap entirely. None of the usernames sounded familiar, so I didn't have any worries in deleting their data.
Not sure if there is any other way to fix it, but this was just my own solution :)
This happens to me also, after updating to 1.17.1 together with latest EssX dev build
@antibitcoin I had the same issue. I just deleted all the userfiles in question. (The files matching the second UUID mentioned in the error message) and then at the end deleting usermap entirely. None of the usernames sounded familiar, so I didn't have any worries in deleting their data.
Not sure if there is any other way to fix it, but this was just my own solution :)
I have also tried that with no use, it keeps coming back, I still think it might be citizens or something like that. or maybe the new minecraeft minecrosoft auth system, not sure if that out yet tho.
or maybe the new [Minecraft] [Microsoft] auth system,
This wouldn't affect UUIDs nor usernames.
it happens less frequent, mostly only during startup of the server, than sometimes when people logging in.
Yes, we understand it's an issue...
Please at least try what was mentioned here: https://github.com/EssentialsX/Essentials/issues/4342#issuecomment-877651547
Yes, we understand it's an issue...
Please at least try what was mentioned here: #4342 (comment)
tried, still the same problem
As of date April the eight of 2022, after updating PAPI ECLOUD UPDATE ALL, because there was an update needed for one or two plugins, the console started spamming and is was related to ExxentialsX. Even on a server that has no CITIZENS2 the console spams... So, I hope the link with PlaceholderAPI will be made and maybe this is the root source of the problem, but I don't know, I am not a programmer, just a maintainer....
This is still open lmao, they don't care to fix this so don't wait, and find alternatives to essentials. I am gonna let you in, on a big secrete. Essentials is not really essential.
Hey, if they don't care, where do we find an alternative? Went from Essentials to EssentialsX because they gave up on us and now EsX stops caring? I see, no obligation to the cause, just crap then?
This issue is pending a large overhaul of how EssentialsX stores user data, which will take some time to properly test, document and integrate. We could rush together some hacky fixes like past maintainers have done, but that would only lead to more issues for people down the line. This will be fixed when we have the time to properly review the changes needed.
This issue is pending a large overhaul of how EssentialsX stores user data, which will take some time to properly test, document and integrate. We could rush together some hacky fixes like past maintainers have done, but that would only lead to more issues for people down the line. This will be fixed when we have the time to properly review the changes needed.
We had so much positive use from EssentialsX that I am not gonna switch to something else if it is not very necessary or only when the plugin is abandoned and noone will pick things up. I am fully aware that a lot of people who develope and maintain plugins for the MC community are not being paid, and there are also some who sell a copy of it through premium - which won't make them run away after being paid, as I have noticed on a few occaisions - but the main fact is, we, and I mean the most of serverowners who make no profit at all like we do, have very much use of plugins that help maintain our servers, so our thanks go in your direction, team EssentialsX.
I hope the overhaul will help getting your fans back.
Thanks.
Your usermap is polluted with incorrect UUIDs. Could you try stopping your server, renaming
plugins/Essentials/usermap.csvtousermap.csv.bak, and starting your server back up?
[16:39:11 INFO]: [Essentials] Found UUID f51219be-6192-4bbe-a849-55a063b71643 for player vietnamfortnite, but player already has a UUID (a5e7bf09-bf65-4ced-8a30-1069756ba265). Not replacing UUID in usermap.
Delete: UUID f51219be-6192-4bbe-a849-55a063b71643
In the essentials/userdata folder and the issue will be resolved
Thank you for your help. but.. Players with that issue already quit playing long ago, never seen this issue again. closing this issue for now. as I see the dev have pulled it into a todo list https://github.com/EssentialsX/Essentials/pull/4581
Do I understand that this issue will be resolved? Because it is not the fact that users do not return often on servers, it is the simple fact that this occurred on our server when we updated Essentials from 2.20.0-dev 4 to 2.20.0-dev 5 so in our case it is not something that 'just happened a long time ago' but very recent, and as far as I can see, it makes no sense because my userdata is also in that list and I hate to tell people that by deleting the userfolder that their inventory is gone. I do hope you can resolve this, because the userdata is fine as far as I can see... But, never mind if you don't, we decided to step to a different plugin on that server, because errors on the console gives an indication that there is either something wrong on the server, the MC version we use (PAPER) or another plugin that did not withstand the test of time, sadly this happens often.
This issue has not yet been resolved. I plan to review the usermap rewrite PR as soon as I have a large block of time to review it, but this won't be possible for a while.
In the mean time, I'm reopening this issue to avoid confusion. Manually deleting usermap files is a workaround, not a proper solution, and this issue remains valid until EssentialsX is able to resolve these automatically.
@MrKiller01 There are no changes in 2.20-dev+5 related to user data. In addition, EssentialsX's userdata folder has no relation to inventories or other server data. Your issue likely cropped up due to interactions with other plugins that are out of our control. We will mitigate these in the future, but please be patient.
I noticed the -not to userinventories related- before I actually knew for sure. Sorry. Hope you can fix this in some time in the future though, our other servers are still running essentials. Might it be helpful to say that I updated on that peticular server the papi ecloud service for essentials? On the other server where I have no errors, an update is still pending for papi, but now I know this one has a very large user base and I will not let this huge list of errors fill the logs every time we restart it.
As stated in my previous comments, we intend to fix this as soon as possible. There is no ETA for the usermap rewrite PR.
As long I have checked all the users with this problem in my server were people who changed of uuid (semi premium things). The problem is this is generating a memory leak and consuming all cpu because is processing the usermap constantly.
This needs to be fixed or give a temporal solution because I can't be everyday deleting files manually.
Just to add I am encountering this error as well. Latest version of Paper (1.19 #29) and EssentialsX (2.19.4)
