Henning and Matteo,
As promised, I did more research and called my hosting service (godaddy) They were very helpful, and traced down the problem so the the CLI CRON would run automatically and not return that message.
What they did was to change the path that godaddy was executing from to EXPLICITLY specify that it was PHP 53 instead of 5.2 I asked why that had to be specified, and they said its because their server runs both 5.2 and 5.3 scripts, so I had to pass on the exact path.
It was passed on as follows from the CRON JOB manager at godaddy: /web/cgi-bin/php5_3 "$HOME/html/moodle/admin/cli/cron.php"
instead of the previous: /web/cgi-bin/php5 "$HOME/html/moodle/admin/cli/cron.php"
Once I ran the script this way, it executed with MANY statements sent to me in the CRON daemon report at my email address. I then went to Godaddy and watched several processes running in teh background, initiated by this CRON job.
After that, I re-ran my backup report, and now I am getting this:
Last execution log
The two that report as "
Unfinished" are the two courses in my Moodle. The STEM is the
Front Page backup.
Do you notice the strange dates on the unfinished courses? I have never yet gotten a correct backup in these courses, and I am at a standstill as to why it is happening. Do you know any way to wipe out the execution log and start over from scratch. These dates never change, so something bad has happened to the original backup and I think they need to be reset, but I don't know how. Can you give me some help here please?
Thank you for pointing me in the right direction. I think if I get this worked out, I will have the whole thing fixed!