Cron Not Running Properly When Running Manually

[gutterboy]

Trying to run the cron manually via the blesta admin, it used to run fine, but now it doesn't seem to. I have two unsent invoices and when I run it it just outputs the following data:

Attempting to run all tasks for Gimko.
All tasks have been completed.
Attempting to run all system tasks.
All system tasks have been completed.

...and the two invoices remain unsent.

 

Does it have some rule about not running too quickly again or something? Why isn't it running?

[gutterboy]

Probably, as that will terminate Blesta if it takes longer than ... such... such.

 

Hmmmmm...... ok. Just wondering as I thought Blesta may have done some trickery to get around it.

[Michael]

Hmmmmm...... ok. Just wondering as I thought Blesta may have done some trickery to get around it.

Blesta's a PHP Script, it can't control the server settings / php.ini settings unless modifications to a custom.ini or .htaccess rules.

[gutterboy]

If I wanted to set a larger time out for the cron only, what script do I need to edit to do that? index.php?

[Michael]

If I wanted to set a larger time out for the cron only, what script do I need to edit to do that? index.php?

 

Don't believe you can, it's one value.

[gutterboy]

Don't believe you can, it's one value.

 

No you can, I do it with scripts all the time.

[Michael]

No you can, I do it with scripts all the time.

 

Then you don't need my help as you should know how to do it.

[gutterboy]

Then you don't need my help as you should know how to do it.

 

Well I was just asking what the correct script to do it in was...... seems like it runs off of the index.php file in the root dir?

[Cody]

Well I was just asking what the correct script to do it in was...... seems like it runs off of the index.php file in the root dir?

 

Set the max execution time in your php.ini file. On most machines, there is not max execution time in CLI mode, so if you're running cron using something like /usr/bin/php instead of wget, then timeout is not the issue here.

[gutterboy]

Ok, looks like timeout was the issue. Increased it to 240 and from the tests I have done when running the cron manually it now fully completes.

 

Though it would be good if the script flushed the output buffer along the way as each task is done rather than spit it all out at completion.