Bumped by HostGator

[hypertoast]

I have an account with HostGator for hosting. Yesterday, I got a Cron report of ResellerClub saying that it failed to update the renewal dates.

 

I pushed it on HostGator, and they said that the script was using "too many resources" and that they will not permit the same unless i get a dedicated server or VPS.

 

I am wondering whether other users have faced similar issues from their host providers and what have they done to circumvent the same?

 

Also, does the script really use so much usage to cause a flag to be raised?

 

Please advise.

[bear]

I'm not using a provider, I run my own boxes, and there have been times it's exceeded 5 minutes connecting to Enom for me with that script, so I'm sure it's the probably cause. Chances are fairly good the script was simply taking a long time to complete because of slow connections to the Resellerclub interface, not a failing of WHMCS. It's not likely resources, but time running that flagged it.

[MediaPlayStudios]

I'm not using a provider either I run my own DC and we have customers that use WHMCS all the time. And I would say that we have about 70 or so customers per box that we use for Shared & Reseller Hosting that uses WHMCS and it's never caused an issue before.

 

But then again it's all in how providers setup there servers allot of time systems admins put so many restraints on a system they cause more problems then they solve

[hypertoast]

HostGator says it has used close to 30% CPU... I did monitor the same, and I got the similar results. I am not sure what is going wrong.

 

Is there anyway to run the script in batches?

 

Thank you.

[simplybe]

It does use a fair amount of cpu and memory when using enomsync. I only run it once per week on a low end dedicated box. try running it at a different time when the server may not be as busy.