hosting account suspened because of cron job

[cgchris99]

Here is the message I received from my host
-------------------------------------------------------------------------------------------
Our system automatically suspends due to abuse on resources and found this to be the reason why:

Top Process %CPU 81.0 /usr/bin/php /home/xyz/public_html/cron.php
Top Process %CPU 77.0 /usr/bin/php /home/xyzpublic_html/cron.php
Top Process %CPU 43.0 /usr/bin/php /home/xyz/public_html/cron.php
-------------------------------------------------------------------------------------------

I was simply testing the sugarcrm system. The only process it was setup for was to get email messages and put them in the database.

It should not take that much resource to do this process. In fact since it was only for testing, half the time there were not email messages to get.

Any thoughts?

[Superman]

Set larger interval for checking inbound emails and refreshing jobs

[cgchris99]

The cron job was already set to run only every 10 minutes.

[sugarchris]

What version of Sugar were you testing?

[cgchris99]

I believe it is v4.1

[sugarchris]

anything from your sugarcrm.log files indicating a problem?

also, make sure you are on 4.0.1a. 4.0's scheduler has some serious issues. 4.0.1a has the latest and most stable Scheduler code. please upgrade if you're not on 4.0.1a.

and then let me know if you're still having this 90% cpu issue.

[Superman]

4.0's scheduler has some serious issues.

can you sound this issues?

[sugarchris]

The Schedulers issues are located in particular versions/combinations of PHP with IIS or versions of Apache. If they are working for you with 4.0 code, then you should not worry - there were no security issues associated with the bugs. However there are serious performance gains to be had by upgrading to 4.0.1a, so I highly recommend doing so even if you currently have no problems.

If you want more details, do a search at http://bugs.sugarcrm.com for the Scheduler bugs. All of those bugs marked pending or closed are fixes in the 4.0.1a code.

[Superman]

Thank you for feedback!