ethix Posted October 3, 2011 Share Posted October 3, 2011 A basic overview of this issue is. After about 6 months of no issues I now get the following error when an account is created. Module Command Error(Curl Error) Operation timed out after 150000 milliseconds with 0 bytes received - code: 28 It does not seem to worry what remote server is involved so I "presume" it is related to the server where WHMCS is installed. I have tried turning off firewalls, whitelisting IP's etc with no improvement. The actual account gets created but WHMCS does not know about it so no email gets sent to the client with login details. Any help appreciated. Thanks 0 Quote Link to comment Share on other sites More sharing options...
ethix Posted October 3, 2011 Author Share Posted October 3, 2011 Un ticking Tick to use SSL Mode for Connections made no difference. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager WHMCS John Posted October 3, 2011 WHMCS Support Manager Share Posted October 3, 2011 This suggests your server is taking longer than 150 seconds to create the account, if you create an account directly on the server and time it is that the case? If so WHMCS times out and stops waiting for a response from the server, in which case you'll need to optimise the account creation process to take less than 150 seconds. 0 Quote Link to comment Share on other sites More sharing options...
ethix Posted October 3, 2011 Author Share Posted October 3, 2011 Yep. You are correct I just created an account manually and it took 5:23 (minutes:seconds) The load on the server was Load Averages: 0.06 0.13 0.09 It spent most of the creation time on Running post creation scripts (/usr/local/cpanel/scripts/legacypostwwwacct, /usr/local/cpanel/scripts/postwwwacct, /usr/local/cpanel/scripts/postwwwacctuser) So that gives me somewhere to start looking. 0 Quote Link to comment Share on other sites More sharing options...
ethix Posted October 3, 2011 Author Share Posted October 3, 2011 Near 6am here, so I hope this makes sense. For me the issue was. I have a DNS cluster. One of the datacentres was blocking one of the DNS in the cluster. The end effect was two servers were having issues communicating and cPanel was waiting that long that WHMCS ended up timing out. 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.