Slice Posted October 16, 2009 Share Posted October 16, 2009 Yep, it's all good now. 0 Quote Link to comment Share on other sites More sharing options...
Strats Posted October 16, 2009 Author Share Posted October 16, 2009 Yes, seems resolved now. 0 Quote Link to comment Share on other sites More sharing options...
simplybe Posted October 16, 2009 Share Posted October 16, 2009 It sounds like the bunch of you guys got poorly configured servers, as we had issues with eNom as well and it didn't take WHMCS or anything down. What specs are your server? In my case the apache usage with whmcs is enough to to bring the server to a crawl until the process is killed: Core2 Duo 2.8GHz 2gb ram Server has been online over a year and whmcs is the only script I have seen so far that causes this. A more powerful server would be able to handle it better but whmcs is still at fault here. Something needs to change in how whmcs handles the call to enom. thanks 0 Quote Link to comment Share on other sites More sharing options...
HostingBegins Posted October 17, 2009 Share Posted October 17, 2009 Had the same problem Quad Core 2.5GHz - Total of 8 Processor Intel® Xeon® CPU 4gb Ram I have never seen this before on any of my servers. But I am sure Matt is coming up with something to avoid this problem again. I also run AWBS with another business, and we had no access to domains yesterday, but did not AWBS did not course any server problems at all. Thanks Rich 0 Quote Link to comment Share on other sites More sharing options...
simplybe Posted October 17, 2009 Share Posted October 17, 2009 no i never had no problems with awbs when enom had been down, stopped using it though about 6 months ago in favour of whmcs. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.