Skip to main content

Weird cpses error messages

Comments

10 comments

  • flycast
    Turned out it was leftover session files - that is - cpses_[ahashofsomekind]. I was developing. I created an account, logged in, tried some stuff and then just closed the browser tab rather than log out. After that I deleted the account. When I would recreate the account with the same username it was getting session files crossed.
    0
  • cPanelKenneth
    I believe those session files should be deleted upon account termination. I've opened case 84485 to have this examined.
    0
  • Nixie86
    [quote="flycast, post: 1521842">Turned out it was leftover session files - that is - cpses_[ahashofsomekind]. I was developing. I created an account, logged in, tried some stuff and then just closed the browser tab rather than log out. After that I deleted the account. When I would recreate the account with the same username it was getting session files crossed.
    Could this be caused by any other reason? This is the only reference to this error that I found on the web. We saw this, and cleared all browser history before creating new account, and still showing this error. We backed up from a different hosted location and restoring to new location, if that makes a difference.
    0
  • cPanelMichael
    [quote="Nixie86, post: 1541822">Could this be caused by any other reason? This is the only reference to this error that I found on the web. We saw this, and cleared all browser history before creating new account, and still showing this error. We backed up from a different hosted location and restoring to new location, if that makes a difference.
    Your access level is listed as "Reseller Owner". Do you have root access to your system? If so, please open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • ccork79
    Michael, Can you post the resolution for this error? We're seeing the same error on other servers. Thanks!
    0
  • cPanelPeter cPanel Staff
    Hello, There is presently no solution as we have not seen any tickets with this error. In order for us to investigate and find a solution, please open a support ticket using the link in my signature. Then please post the ticket number here in this thread so we can update it accordingly.
    0
  • ccork79
    [quote="cPanelPeter, post: 1556972">Hello, Then please post the ticket number here in this thread so we can update it accordingly.
    Support Ticket Opened: Your Request id is: 4490491
    0
  • ccork79
    Here's the resolution from cPanel Support Staff member Citizen Kepler: ===== Hello, It appears that a few session specific MySQL users were left behind when an session was closed improperly. I have gone and cleared up the remains of these sessions, and the error is no longer appearing. For reference, below is the work preformed to resolve this error: 1) I ran a grep for the sessions that were currently in effect: # grep "cpses_" /var/cpanel/databases/ 2) I removed the following sections from any user's yaml that matched the cpses_########": dbs: {} server: X.X.X.X 3) I removed each of the cpses_######## lines from /var/cpanel/databases/users.db 4) I ran the following command to update the user-data: # /scripts/update_db_cache 5) I then removed all of the cpses_######## users from the mysql.user table to remove the users from mysql. This can be accomplished from the command line or from WHM>> PhpMyAdmin Thanks, Please let us know if you have any questions. -- Citizen Kepler Technical Analyst cPanel Inc. ===== Thanks again for the speedy help. Chris
    0
  • CitizenK
    I am glad that I could help ccork79 Thanks for the shout out. :)
    0
  • Skimice
    This is an older post but I ran into this same problem and tried the fix above but found that there weren't any entries for the specific user I was having problems with in the /var/cpanel/databases directory. My fix was actually pretty simple, I just reset the password for the user which forced a change for the MSQL password and allowed me to login.
    0

Please sign in to leave a comment.