It's fixed now... but it was rather strange.
I created a new account using WHM, which I've done hundreds of times before, and Apache promptly crashed and wouldn't restart. It turns out that a bunch of invalid entries for the new domain got written to the end of the httpd.conf file, preventing Apache from starting.
I manually edited httpd.comf amd deleted the invalid entries, succesffuly started Apache, backed up the working httpd.conf, logged into WHM, and deleted the account. Then I performed a DNS cleanup and successfuly re-created it with no problems.
I've never had this happen when using WHM before. Anyone else aware of any recent bugs that would cause this, or was it perhaps a momentary network fart?
-Rich
I created a new account using WHM, which I've done hundreds of times before, and Apache promptly crashed and wouldn't restart. It turns out that a bunch of invalid entries for the new domain got written to the end of the httpd.conf file, preventing Apache from starting.
I manually edited httpd.comf amd deleted the invalid entries, succesffuly started Apache, backed up the working httpd.conf, logged into WHM, and deleted the account. Then I performed a DNS cleanup and successfuly re-created it with no problems.
I've never had this happen when using WHM before. Anyone else aware of any recent bugs that would cause this, or was it perhaps a momentary network fart?
-Rich