LuckPerms

LuckPerms

41.4k Downloads

Pex migration > User cannot be found

VoidAngel opened this issue · 29 comments

commented

Hello I have run into an issue after migrating from pex to luckperms.

Description:

After migrating from pex to luckperms, all luckperms commands do not work with usernames. It seems I have to use UUIDs only to edit or pull up info about a user. I know its better to use UUID anyways, but not all plugins have uuid placeholders (such as EZPrestige, or other ranking plugins). It is very strange, though, because the plugin seems like it has all the info it needs. If I run the command via UUID it even outputs the correct username.

NOTE: I, VoidAngel, have logged on to the server multiple times after migrating, so I should be in the luckperms cache, but it seems I am not somehow. See the below console output:

Evidence:

24.07 13:36:51 [Multicraft] VoidAngel ran command: lp user VoidAngel info
24.07 13:36:51 [Server] INFO [LP] A user for VoidAngel could not be found.
24.07 13:37:31 [Multicraft] VoidAngel ran command: lp user 37bdf967-50f0-4434-9c8f-f17070094d5c info
24.07 13:37:31 [Server] INFO [LP] > User Info: VoidAngel
24.07 13:37:31 [Server] INFO [LP] - UUID: 37bdf967-50f0-4434-9c8f-f17070094d5c (type: mojang)
24.07 13:37:31 [Server] INFO [LP] - Status: Offline
24.07 13:37:31 [Server] INFO [LP] - Primary Group: peasant
24.07 13:37:31 [Server] INFO [LP] - Parent Groups:
24.07 13:37:31 [Server] INFO [LP] -    > peasant
24.07 13:37:31 [Server] INFO [LP] - Contextual Data:
24.07 13:37:31 [Server] INFO [LP] -    Has contextual data: false
24.07 13:37:31 [Server] INFO [LP] -    Applicable contexts: None
24.07 13:37:31 [Server] INFO [LP] -    Prefix: None
24.07 13:37:31 [Server] INFO [LP] -    Suffix: None
24.07 13:37:31 [Server] INFO [LP] -    Meta: None

Is there a way to fix this? Perhaps a command? or something at startup to correct all the users?

Things that don't work:

  1. Restarting the server
  2. Being online while running the command
  3. Turning on "use-server-uuid-cache" DOES work in a sense, but the luckperms cache still does not update D: I'm worried about too many requests to Mojang by leaving it on. I have a lot of servers and a lot of players so I have to be careful about that. Correct me if I'm wrong please.
commented

Hey! Just out of interest, which backend are you using?

commented

Ah right I should mention that. xD
I'm using the default h2.
Also I'm on Luckperms 4.2.17 and Paper Spigot 1.12.1

commented

Hmm. Could you perhaps export your perms, delete the h2 and reimport please?

commented

Ive migrated about 6 servers from pex to luckperms already. They all have the same issue, but its not always the same users that dont get migrated correctly. On a few servers I can run "lp user VoidAngel info" with no problem, but for a user that is online even at that moment I can type "/lp user exampleuser info" and it will tell me that the user cannot be found.

Given the fact that I have already done this many times I dont think the outcome will change xD
But if you have something else in mind that I am not thinking of, I will try exporting and migrating again.

commented

Export, don't migrate
Literally type /lp export test /lp import test into console

commented

But that does sound like a bug 🤔 cc @lucko

commented

Oh sorry I understand now.
Will do 👍

commented

That worked :D The cache is now updating itself when players log in.
Thanks for the help codingJWilliams.

commented

Can you see if the migration works on the latest version? The version you’re using is quite old...

I’d recommend using your old PEX data on a test server to see if it’s working.

commented

The version you’re using is quite old...

this ^ - I think this was fixed already

commented

The spigot server is offline yes, but players are authenticated with bungee.

commented

Ah I see. I was just using the spigot release version when I made this ticket.
I just changed to v4.2.54 and tried migrating another server to pex and the same thing happened unfortunately. D:
using "/lp user VoidAngel info" while I was online returned no results.

Ive got my work around so I dont really care if its fixed xD I just want you guys to know that the bug still exists.

commented

Server running in offline mode?

commented

Is IP-Forwarding enabled on the bungee and the bungee mode on the Spigot?

commented

Hello,
I have the exactly same problem.
Running on spigot offline without bungee

commented

@BrainStone
Yes and yes

commented

From what I’ve seen almost everyone that migrates has issues resolving player names. Exporting, wiping and importing usually solves the issue, as that completely wipes the username cache.

Just had another case today.
So the PEX migration must somehow mess up the player cache.

commented

Doing the PEX migration shouldn't have any impact on how UUIDs are being saved by LP. Once a player has connected once, they should be permanently cached in the plugins storage.

Do you have any other plugins installed which could possibly be preventing LP from handling the connection, or clearing the data after they've logged in?

commented

Which storage type @BrainStone ?

I'd like to try to reproduce this myself, have been unable to so far.

commented

I can pass you a pex permissions.yml if you would like to test it with a large permissions file that can very likely reproduce the problem.

commented

Ok sure :)

commented

From what I’ve seen it’s the default H2, as most people just plug’n’play.

commented

All I did to migrate was:

  1. Install luckperms with a brand new luckperms folder generated.
  2. While pex is still on the server, do /luckperms migration permissionsex
  3. Wait until the migration is done, then remove pex and restart

After this you should find that most users (not 100% of them though) will not be cached correctly.

permissions.zip

commented

You might need to insert a fake record or something to make it work for you though (?) Juts thought about that because you wont have any data in that pex file for your minecraft account 🤔 And making brand new records with luckperms by just logging in might not reproduce the issue.

commented

Please can you confirm that this is fixed in .58.

The underlying bug has been fixed (so it won't happen on new migrations), and any data already migrated will be "fixed" when each player next connects to the server.

commented

Nice :D Ill try a migration tonight and see how it goes. Ill let ya know

commented

Hmm there's been another member with this issue, don't know what version they were running

commented

The new version is working great for me as far as I can tell. However, I'm still observing to make sure everything is correct.

commented

Marking as fixed for now.

@codingJWilliams Quite likely they were still using an older version.