Based on James' response, I'm guessing that rebuilding these files is more tricky if you're not using database prefixing. My suggestion if you encounter the "Sorry, a mysql user with the name x already exists." error is to simply post a ticket with cPanel and have them take a look. Better safe than sorry.James Otting said:The files there in /var/cpanel/databases are very particular about formatting, and usually cannot be edited by hand. That said, they're actually very easy to rebuild as long as you've not disabled database prefixing. As you have not, I simply removed all the files from /var/cpanel/databases/ and then ran /usr/local/cpanel/bin/setupdbmap to regenerate all the database mapping there from the actual users/dbs in mysql. Other files (like the caches) will be rebuilt automatically as needed. I was then able to create a test account (cptest) without issue. Please try things out yourself, and if you have further problems or questions, just let me know.
Basically, I would not suggest ever using that script unless the ramifications are truly understood. It is not the way to fix this type of issue on systems with database prefixing disabled. I realize it was specifically mentioned about the system not having database prefixing disabled, but my concern here is now the script has been mentioned and someone will run it when it shouldn't be run simply because it's been mentioned on here. Some people don't check or know if they do or don't have prefixing disabled. The script just plain shouldn't be mentioned in any situation due to the likelihood you might cause more problems than solve them.setupdbmap should not be run on a system that has disabled database prefixing. Additionally, running on a system that has been hacked back ( disable->enable prefixing) could/will have undesirable consequences/mappinng.
Anytime you suspect that executing setupdbmap is the proper course of action, I'd audit the results of the cpuser accounts to make sure no ancillary changes occurred outside the account you're trying to fix.
We do not need to see your root password. We have implemented a log-in system that works in conjunction with our ticket system and allows us to log into your server without a technical analyst ever seeing your root password. This is a significant change from the past and it was done to increase the security of our customers' interactions with support.He require my password root?, he need loguin in my server? NO!
|Thread starter||Similar threads||Forum||Replies||Date|
|S||Sorry, a mysql user with the name filedata already exists.||Databases||1|
|A||Error: site.com is already configured. Sorry, that domain is already setup||Databases||11|
|I||Sorry, a mysql user with the name * already exists.||Databases||7|
|connecting to mysql (sorry I know this is not really a cpanel question)||Databases||3|
|C||Sorry, you have exceeded the maximum allowed databases with mysql database unlimited||Databases||3|
|Sorry, a mysql user with the name filedata already exists.|
|Error: site.com is already configured. Sorry, that domain is already setup|
|Sorry, a mysql user with the name * already exists.|
|connecting to mysql (sorry I know this is not really a cpanel question)|
|Sorry, you have exceeded the maximum allowed databases with mysql database unlimited|