Yes, the cron service is running. I restarted it a few times to be certain my entries were taking. It's processing other crons (even other items listed in the root cron) just fine, according to the log. It just won't process the one I add.

Staff Member

The "bad_alloc" error message typically indicates a lack of available memory. Check to see if any VPS resource limits were reached if this is a VPS, or check to ensure enough memory is available at the time this cron job runs.

The "bad_alloc" error message typically indicates a lack of available memory. Check to see if any VPS resource limits were reached if this is a VPS, or check to ensure enough memory is available at the time this cron job runs.

Thank you.

Click to expand...

Hi Michael,

Sorry for the delay. Got called out of the country and had very limited Internet access. It's actually a dedicated box with almost 30G of free RAM. That's the really strange part. Running the script from SSH does not cause the issue...it's only when I run it from the CRON. I can run it from the command line literally right before or after the CRON executes, and there are no problems at all. But running it via cron gets the error.