crons无缘无故地停下来

Question

Well this isn't true, I'm sure there's a reason, but I can't find it!!

I have a script that can take around 10 minutes to execute. It does a lot of communicating with an api on a service that we have that use. It pulls a bit of a fingerprint of everything every 24 hours. So what it's doing is pretty aside from the point. the probm I'm finding is the script stops executing somewhat randomly!!

I can't find any errors that would cause my script to stop executing, even with

//for debugging
error_reporting(E_ALL);
ini_set('display_errors', '1');

on for debugging, it's all clean. I've also used

set_time_limit(0);

so that it shouldn't ever time out.

With that said, I'm not sure how to get any more debug info to figure out what it's stopping. I can say that the script should NOT be hitting any memory limits or anything. I mean that should throw an error, and I've gone through and cleaned this script up as much as I can see to clean it up.

So my Question is: What are common causes for a cron ending when it shouldn't? How can I debug this more effectively?

Answer 1

What are common causes for a cron ending when it shouldn't?

The most common in my experience is that the cron user has different permissions or different environment variables than the way that you're executing it from the command line.

Make your cronned program dump its environment to a temporary file and see if it's what you expect.