Leaderboard

That error is likely because an httpd.conf rebuild was already in progress. Cpanel locks the file so multiple scripts can't try to edit it at a time, and generally the script that doesn't own the lock tries for 300 seconds and then errors out. Since there are so many virtualhosts on Johnny it definitely takes more than 300 seconds to do a full httpd.conf rebuild. Everything seems to have straightened itself out on its own though. Let us know if your site still isn't working for you after you clear your browser cache and flush your os dns records. It's loading fine for me.

That's because of an ongoing DDoS attack on our server. I've changed a setting on your account to mitigate the effect of the attack your account and it should start working in the next few hours. EDIT: Nevermind...it failed. Because the DNS updated, I'm not sure if httpd.conf will fix itself when it's next rebuilt or not...Lets have Krydos look at this. Changed all instances of [65.19.141.67] -> [64.62.211.131] in myfirstwordpress.heliohost.org Changed all instances of [65.19.141.67] -> [64.62.211.131] in chucachan.ga The system updated “23” entry. Updating httpd.conf....ERROR: Cpanel::Exception::Timeout/(XID shnkpu) The system failed to lock the file “/etc/apache2/conf/httpd.conf” after 301 seconds. at /usr/local/cpanel/Cpanel/Exception/CORE.pm line 336. Cpanel::Exception::create("Timeout", "The system failed to lock the file \x{e2}\x{80}\x{9c}[_1]\x{e2}\x{80}\x{9d} after [quant,_2"..., ARRAY(0x4a41d30)) called at /usr/local/cpanel/Cpanel/Exception.pm line 61 Cpanel::Exception::__ANON__(__CPANEL_HIDDEN__, __CPANEL_HIDDEN__..., ARRAY(0x4a41d30)) called at /usr/local/cpanel/Cpanel/SafeFile.pm line 729 Cpanel::SafeFile::_timeout_exception("/etc/apache2/conf/httpd.conf", 301) called at /usr/local/cpanel/Cpanel/SafeFile.pm line 761 Cpanel::SafeFile::_die_if_file_is_flocked_cuz_already_waited_a_while("/etc/apache2/conf/httpd.conf", 301) called at /usr/local/cpanel/Cpanel/SafeFile.pm line 829 Cpanel::SafeFile::_lock_wait("/etc/apache2/conf/httpd.conf") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 355 Cpanel::SafeFile::_safelock("/etc/apache2/conf/httpd.conf") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 558 Cpanel::SafeFile::_safe_open(undef, 66, "/etc/apache2/conf/httpd.conf", CODE(0x4a41a90), "safesysopen") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 208 eval {...} called at /usr/local/cpanel/Cpanel/SafeFile.pm line 207 Cpanel::SafeFile::safesysopen(undef, "/etc/apache2/conf/httpd.conf", 66, 384) called at /usr/local/cpanel/Cpanel/SafeFile.pm line 121 Cpanel::SafeFile::safesysopen_no_warn_on_fail(undef, "/etc/apache2/conf/httpd.conf", 66, 384) called at /usr/local/cpanel/Cpanel/Transaction/File/Base.pm line 137 Cpanel::Transaction::File::Base::new("Cpanel::Transaction::File::Raw", "path", "/etc/apache2/conf/httpd.conf") called at /usr/local/cpanel/Cpanel/Transaction.pm line 20 eval {...} called at /usr/local/cpanel/Cpanel/Transaction.pm line 20 Cpanel::Transaction::get_httpd_conf() called at /usr/local/cpanel/Cpanel/HttpUtils/Config/Apache.pm line 73 Cpanel::HttpUtils::Config::Apache::new("Cpanel::HttpUtils::Config::Apache") called at /usr/local/cpanel/Whostmgr/Accounts/SiteIP.pm line 256 eval {...} called at /usr/local/cpanel/Whostmgr/Accounts/SiteIP.pm line 256 Whostmgr::Accounts::SiteIP::set("nicu", "65.19.141.67", "64.62.211.131") called at whostmgr/bin/whostmgr2.pl line 8674 main::dochangeip("changeip") called at whostmgr/bin/whostmgr2.pl line 8846 main::changeip("changeip") called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 227 Whostmgr::Dispatch::_do_call("changeip", HASH(0x4a70518), HASH(0x4a406f8)) called at /usr/local/cpanel/Whostmgr/Dispatch.pm line 144 Whostmgr::Dispatch::dispatch("changeip", 1, ARRAY(0x4a798c8)) called at whostmgr/bin/whostmgr2.pl line 979 And a subsequent attempt at changing it again threw error: The remote dns zone is not consistent with the httpd.conf. The current ip in httpd.conf is: 65.19.141.67. The current ip in the dns zone is: 64.62.211.131! 64.62.211.131 will be switched to the new ip as well! The local dns zone is not consistent with the httpd.conf. The current ip in httpd.conf is: 65.19.141.67. The current ip in the dns zone is: 64.62.211.131! 64.62.211.131 will be switched to the new ip as well! Warning, serious database inconsistency. httpd.conf, local dns, and remote dns all have different ideas about what the ip address of this site really is. They will now all be changed to the new ip: 64.62.211.131! changezoneip requires the “sourceip” and “destip” to be different: “64.62.211.131”

There isn't one by default (I just checked, none of my cgi-bin folders have one). You should be able to just delete it. Python 2.7 should be available on all of our servers, but Python 2.7 with Django requires Ricky.