• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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