Weird cpses error messages
I am getting weird cpses error messages on certain users. I have noticed the error when I create a new account in the last week. I thought it was related to the function I wrote to hook into the Account::Create - post hook but I do not think so now. It happens randomly when I create a new user - on average about 50% of the time.
When it happens it seems to stay broken on that account. I can reproduce it reliably by logging into the affected account using cPanel and then click on phpmyadmin. While cPanel redirects to phpmyadmin there is a message at the top of the screen that says:
When the error happens I get:
[QUOTE]You, "aaaa" are not authorized to access "cpses_aa4JfhySPo"
You, "aaaa" are not authorized to access "cpses_aaqRz7x4No"
You, "aaaa" are not authorized to access "cpses_aawy6IvBlu"
"aaaa_nbdj1"
Under normal conditions (when the bug does not happen) you get: [QUOTE]Please be patient, you will be redirected in a moment...
The issue it is causing me is the function I wrote creates a Wordpress install after a new account is set up. The API I am using (I've tried both Softtacular and Installatron) tries to set up a new dbuser but is getting these warning messages returned instead. The Softtacular and Installatron API does not know what to do with the messages. Softacular just fails with a: [QUOTE] The MySQL Connection could not be established.
nstallatron gives me a: [QUOTE]Technical Error: You, "aaaa," are not authorized to access "cpses_aa4JfhySPo" You, "aaaa," are not authorized to access "cpses_aaqRz7x4No" You, "aaaa," are not authorized to access "cpses_aawy6IvBlu" `aaaa_fl5h1'
About a week ago I upgraded to MySQL 5.5.32 and then rebuilt PHP.
Under normal conditions (when the bug does not happen) you get: [QUOTE]Please be patient, you will be redirected in a moment...
The issue it is causing me is the function I wrote creates a Wordpress install after a new account is set up. The API I am using (I've tried both Softtacular and Installatron) tries to set up a new dbuser but is getting these warning messages returned instead. The Softtacular and Installatron API does not know what to do with the messages. Softacular just fails with a: [QUOTE] The MySQL Connection could not be established.
nstallatron gives me a: [QUOTE]Technical Error: You, "aaaa," are not authorized to access "cpses_aa4JfhySPo" You, "aaaa," are not authorized to access "cpses_aaqRz7x4No" You, "aaaa," are not authorized to access "cpses_aawy6IvBlu" `aaaa_fl5h1'
About a week ago I upgraded to MySQL 5.5.32 and then rebuilt PHP.
-
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 -
I believe those session files should be deleted upon account termination. I've opened case 84485 to have this examined. 0 -
[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 -
[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 -
Michael, Can you post the resolution for this error? We're seeing the same error on other servers. Thanks! 0 -
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 -
[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: 44904910 -
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 -
I am glad that I could help ccork79 Thanks for the shout out. :) 0 -
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.
Comments
10 comments