This happens when the option to transfer databases is NOT checked. The incoming account does not adopt the max database limit that I've set in the "Standard" package, with which it is created; it sets its own, which is 0.
My use case: I want to create a new database for a site, not transfer the old one. So I add some database / user / permission creation code in a Standardized Hook that fires on Accounts::Create(which is fired when an account is transferred over.)
Here is the API error:
Any idea of a way I can circumvent this? My next step is going to be to try and reassign the same Standard package on account creation before running the database creation hook; maybe it will override the bad maxsql limit. Here is the feedback from the Accounts::Create event if it's pertinent:
My use case: I want to create a new database for a site, not transfer the old one. So I add some database / user / permission creation code in a Standardized Hook that fires on Accounts::Create(which is fired when an account is transferred over.)
Here is the API error:
Code:
{
"apiversion": 3,
"func": "create_database",
"module": "Mysql",
"result": {
"data": null,
"status": 0,
"errors": ["(XID 6qjn27) You have reached your maximum allotment of databases (0)."],
"messages": null,
"metadata": {}
}
}
Code:
{
"contactemail" : "",
"maxftp" : "0",
"bwlimit" : 0,
"pass" : "HIDDEN",
"owner" : "root",
"max_defer_fail_percentage" : "unlimited",
"spf" : null,
"gid" : "",
"maxsub" : "0",
"useip" : "n",
"hasshell" : "n",
"user" : "REDACTED",
"featurelist" : "default",
"mxcheck" : "remote",
"no_cache_update" : 0,
"homeroot" : "/home",
"hascgi" : "n",
"domain" : "REDACTED.com",
"quota" : 0,
"digestauth" : "n",
"plan" : "Standard",
"is_restore" : 1,
"dkim" : null,
"force" : 0,
"skip_mysql_dbowner_check" : 0,
"max_email_per_hour" : "unlimited",
"homedir" : "/home/REDACTED",
"maxaddon" : 0,
"maxlst" : "0",
"locale" : "en",
"maxpop" : "0",
"maxsql" : "0",
"cpmod" : "paper_lantern",
"uid" : "",
"forcedns" : 1,
"useregns" : 0,
"maxpark" : 0
}
Last edited:
