It seems like you're experiencing an issue with the lveinfo command in CloudLinux. Specifically, the command is returning a UserName that does not exist and is persisting in the ve.cfg file. Here are some steps you can take to address this problem:

1. Check for Typos:

   • Double-check for any typos or misspellings in the UserName. It's possible that there might be a small error causing the mismatch.

2. Verify User Existence:

   • Make sure that the user associated with the ID actually exists on your system. You can use the getent passwd command to list all users.

3. Inspect the ve.cfg File:

   • Open the ve.cfg file in a text editor and manually correct the UserName if it's incorrect.

4. Restart LVE Services:

   • After making changes, it's a good idea to restart the LVE services to apply the modifications. You can do this by running service lvemanager restart.

5. Check for Cache Issues:

   • Sometimes, information can be cached. Try running the command with the --no-cache option to ensure it retrieves fresh data.

6. Contact CloudLinux Support:

   • If the issue persists, it might be a bug or a more complex configuration problem. Consider reaching out to CloudLinux support for assistance. They may have specific troubleshooting steps or solutions for your situation.

7. Review Documentation or Forums:

   • Check the CloudLinux documentation or community forums for any known issues or solutions related to the lveinfo command.

8. Backup and Restore Configuration:

   • If all else fails, consider taking a backup of your ve.cfg file, removing it, and letting CloudLinux regenerate it. This can sometimes clear out any lingering incorrect information.

Remember to always back up critical configuration files before making any changes, especially if you're manually editing them. This way, you can easily restore them in case anything goes wrong.