[support] cron stuck on a node. how to find which one

[Earnie Boyd]

Quoting Brett Evanson <brettev at gmail.com>:

> I have the memory at 64 MB and the execution time at 240. It times out way
> before 240 seconds, making me think it is getting stuck on something and
> kicking out early.
>

That's cool.

>
> Does admin/logs/watchdog give a clue?
>
> Look at your server log files for php errors such as memory exhausted.
> What is your php memory_limit set to?  Try increasing it [1].  The more
> modules the more memory needed.  The more php errors that occur the
> more memory is needed (at least that is what I'm discovering on a WAMP
> service).
>
> [1] In .htaccess [2] add ``php_value memory_limit 64M''.  Change 64M to
> 128M or 256M as needed.
> [2] You can also change the php.ini file if you desire.
>

You still need to check the log files.  Try decreasing the time 
execution and increasing the number of times cron executes.  The longer 
it runs the more memory it might use.

Earnie -- http://for-my-kids.com/
-- http://give-me-an-offer.com/