• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Mass Subdomain Creation Corrupts Config Files

R

RickAMP

Guest
The Action:

I ran an automated job that would create 414 subdomains in succession via the Plesk user interface.

The Symptom:

After coming in the next day to check on the robot's progress, I found that it was able to create all 414 subdomains, however, none of the domains on the server were reachable due to a configuration file issue.

The Message:

2012-06-04T09:30:21-04:00 ERR (3): New files of configuration for Apache web server were not built due to errors in configuration templates. The detailed error message was e-mailed to you, so please check the e-mail, fix the errors, and click <a href="/admin/subscription/webserver-configuration-rebuild/?returnUrl=%2Fhome%2Fadmin">here</a> to retry generating configuration.

The Workaround:

I found that if I deleted enough subdomains where there was only around 100 remaining, that I was able to rebuild the Apache config files and all the subdomains are accessible again.

The Questions:

1) I read that there is no maximum amount of subdomains when creating them on Apache with Plesk. Is this true?
2) Should I have had this problem?
3) What can I do to be able to create all 414 subdomains without a crash of my configuration file?

Thanks.
Rick
 
Back
Top