Console Error Logs

I get things in console that appear like this.

21.08 05:50:52 [Server] INFO at org.spongepowered.api.util.Functional.lambda$asyncFailableFuture$1(Functional.java:131) ~[Functional.class:1.8.9-1890-4.2.0-BETA-1620]

21.08 05:52:27 [Server] INFO at org.spongepowered.common.profile.query.UniqueIdQuery$SingleGet.call(UniqueIdQuery.java:64) ~[UniqueIdQuery$SingleGet.class:1.8.9-1890-4.2.0-BETA-1620]

They spam the console and its hard to read chat through it.

Please post the full log using something like pastebin

http://pastebin.com/FeQXr203 - This error log is from about 6AM EST to 6:08AM EST

com.mojang.authlib.exceptions.AuthenticationException: The client has sent too many requests within a certain amount of time

This happens when the same UUID is being looked up with Mojang - they have a limit of 1 request per minute for profiles.

Not sure if it’s a plugin or a sponge internal task that’s doing the lookup - either way, something is being too eager with the profile requests.

Would that be triggering the other errors?

What other errors? I’m just seeing this repeated over and over:

[06:07:28] [pool-3-thread-5/WARN]: Couldn't look up profile properties for com.mojang.authlib.GameProfile@432f23f2[id=39fb8daf-b797-329a-8e1e-02a34ebdc975,name=,properties={},legacy=false]
com.mojang.authlib.exceptions.AuthenticationException: The client has sent too many requests within a certain amount of time
	at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:65) ~[YggdrasilAuthenticationService.class:?]
	at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillGameProfile(YggdrasilMinecraftSessionService.java:175) ~[YggdrasilMinecraftSessionService.class:?]
	at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillProfileProperties(YggdrasilMinecraftSessionService.java:168) ~[YggdrasilMinecraftSessionService.class:?]
	at net.minecraft.server.management.PlayerProfileCache.lookupByIds(SourceFile:249) ~[lt.class:?]
	at net.minecraft.server.management.PlayerProfileCache.getOrLookupByIds(SourceFile:284) ~[lt.class:?]
	at org.spongepowered.common.profile.query.Query.fromUniqueIds(Query.java:70) ~[Query.class:1.8.9-1890-4.2.0-BETA-1620]
	at org.spongepowered.common.profile.query.UniqueIdQuery$SingleGet.call(UniqueIdQuery.java:64) ~[UniqueIdQuery$SingleGet.class:1.8.9-1890-4.2.0-BETA-1620]
	at org.spongepowered.common.profile.query.UniqueIdQuery$SingleGet.call(UniqueIdQuery.java:45) ~[UniqueIdQuery$SingleGet.class:1.8.9-1890-4.2.0-BETA-1620]
	at org.spongepowered.api.util.Functional.lambda$asyncFailableFuture$1(Functional.java:131) ~[Functional.class:1.8.9-1890-4.2.0-BETA-1620]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_77]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_77]
	at java.lang.Thread.run(Unknown Source) [?:1.8.0_77]

Can you list all your plugins ?

Is there a way to fix this?

39fb8daf-b797-329a-8e1e-02a34ebdc975

1f37bc10-d9e9-38ee-a37c-2b1b3ea0ff24

a5fe9b26-c59d-3cf3-b6e7-6ed1b192bbd4

9001a9bd-06a6-34d9-83d2-bb02c0a4fb1c

etc – all these UUIDs are not valid minecraft user UUIDs

Either a plugin/mod has generated their own UUIDs for ie Town/Clan etc bank accounts, etc, and it or some other system is then trying to generate all the lookups for these fake uuids repeatedly over and over - “I expect to get a player name, dammit, not an invalid result! If failed, throw it at it again until it gives a name!”
Or more likely, it is the native uuid-lookup system trying to get the info for the uuids in its cache gone-wild…

PERCHANCE that you had this server set in offline mode for a snip of time and had some accounts login in offline mode, and generate player profiles in offline mode? The system would be contaminated with those invalid, offline UUIDs (that it doesn’t bother looking up when in offline mode) that are generated for offline logins, and fails to process them.

I have seen sometimes in my own testing long ago that that minecraft error message about client sending too many requests in a time being a result of simply being a non-resolving UUID such as these – minecraft does try hard to resolve all the uuids on its to-do list.

IF they are indeed from offline-user usage, purging the accounts from the playerdata folder should fix.
However, if those accounts are integrated into plugin storage records such as bank account holders and a system is sweeping through all the entries in the bank account list to do the lookups (why such a system would do so is beyond understanding, but some authors do what they want), they would have to be purged from that system.

Where it will be more problematic is if those UUIDs are generated as placeholders like town banks, etc for bank accounts - in which case that should be a valid approach, but then some mod/plugin being used is trying to carry out lookups against those entries (again, #1 blame would be the plugin doing the recording of that data itself, #2 blame would be anything else that needs to check ‘the current this damned second user name of that offline player’ for some action) – UUIds/players found in the records of a “never ever used this in offline mode” server, that some plugin/mod is crazy about needing to get the offline user names for.

The fact that it takes a couple minutes, and happens after a few regular accounts login for a bit, suggests more that it is something that is scheduled, or impacts-everyone on the server online/offline during a regular burst moment – like “Lets pay everyone on the server $1 right now” but instead of doing only the online players, it is checking the offline player list as well (which then again, points back to more likely being Offline-uuid contamination) or else, some plugin that is generating FAKE PLAYER PROFILE files in order to act as placeholders, not just fake uuids for a bank-account.

========

  1. Has this server run in offline mode before, even briefly just allowing a few accounts to login?
  2. There are 3 UUIDs that are invalid - check through the logs to see if there are more, I just stopped with three. Go find those UUIDs on your system, and figure out what they are assocated with. Check the ban/whitelist/ops/cache json files for those numbers (and purge those entries if found); check the playerdata profile folders for those uuids, see if they exist - they shouldnt, unless a mod is creating them…
    2b) Check data-storage for your economy system, check your permissions file - perhaps they have been given a rank in the system///
    2c) Check all other plugin folders for any ‘userlists’ that get made - this includes plugins that make a folder and put a player-UUID file in it to store personallized information about that user — most “essentials” plugins do that kind of thing; primarily they would have been contaminated by offline usage, but might also generate one for fakes like town bank accounts

Really, if you ran in offline mode, the whole system is flooded with invalid player accounts and UUIDs, permissions files, regional protection data, etc – and it may be that players are walking around and the region-protection plugins are trying to resolve a bad UUID in their region owner list…

If never in offline mode, then identifying where these UUIDs come from, and where they can be found all through your server will help to identify which system put them there, why, and identify a candidate for which system is triggering the resolving when they should not be trying to look them up in the first place.

1 Like

Awesome detective work @TheBoomer

Thanks, @ZephireNZ - though without further input or research from the asker, its more just hypothesis and battle-strategy than it is detective work :slight_smile: