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
Plugin Autorank v3.4 generated an exception while executing task 83 #191
Comments
I would like too add, after running more test that this only accurs when adding the "data.yml" file. I took a fresh install of it on my test server, added each file one by one starting the server after each transfer, and only when i add the data.yml file it happens. I have done it in different orders and still produces the same result. Here is the contents of my data.yml file: Regards |
This here is the latest error. I deleted all files relevant to player data, and all was fine till now. [00:04:12 INFO]: [Autorank] Could not find name of account with uuid: 'd6a411df-4863-3579-ab15-5a4909d50864' I have traced the UUID to the specific player, but when checking all the other files it all matches up and nothing seems to be wrong with that UUID. Any information would be great. Regards |
UPDATE: I have even tried deleting EVERY file, and even when running a fresh version, with no players online, it still accurs. It has gotten to the point where the players which UUID are showing cannot rank up further, as Autorank does not know whom they are |
Have you deleted the data.yml as well? |
I have, and for some reason, when they file is generated again, the file seems to still contain the same information, though i don't know where it is getting it from |
Could you stop the server, delete the file, then start the server back up again? |
I will do it now |
This is very strange.... i feel like i have wasted your time. I did that twice before, yet it didn't help. I do it now, and no errors occur and the data.yml file is empty. Thank you for getting back to me on the matter, Much appreciated, if anything happens i will let you know. -Jeb |
Good to hear ;) I'll close it for now. Open a new ticket if you get any errors. |
Good Day,
I have had this specific error for a while, been trying to solve it the good ol' fashioned way, but 2 weeks later i still can't figure it out.
I have updated to the latest dev build as well as tried other versions, still no luck.
I have however tried it on a test server, and found if i use my config files from my current server, the error reproduces on the test server, yet a fresh install seems to be fine.
The problem is that because i don't know which file specifically is causing the error, i am very reluctant to replace them.
Here is the full error:
Exception in thread "Craft Scheduler Thread - 5"
[22:35:13 WARN]: org.apache.commons.lang.UnhandledException: Plugin Autorank v3.4 generated an exception while executing task 83
at org.bukkit.craftbukkit.v1_8_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at me.armar.plugins.autorank.util.uuid.storage.UUIDStorage.getPlayerName(UUIDStorage.java:245)
at me.armar.plugins.autorank.util.uuid.UUIDManager.getPlayers(UUIDManager.java:130)
at me.armar.plugins.autorank.util.uuid.UUIDManager.getPlayerFromUUID(UUIDManager.java:90)
at me.armar.plugins.autorank.leaderboard.Leaderboard.getSortedPlaytimes(Leaderboard.java:104)
at me.armar.plugins.autorank.leaderboard.Leaderboard.updateLeaderboard(Leaderboard.java:185)
at me.armar.plugins.autorank.leaderboard.Leaderboard$2.run(Leaderboard.java:84)
at org.bukkit.craftbukkit.v1_8_R1.scheduler.CraftTask.run(CraftTask.java:71)
at org.bukkit.craftbukkit.v1_8_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
... 3 more
If you see anything that pops out at you, please let me know, i am not good at reading error reports in the first place :P.
Thanx in advance.
-Jeb
The text was updated successfully, but these errors were encountered: