According to the logs, SetCronJob didn't run cron jobs from 2:10 AM to 2:46 AM, and from 2:51 AM to 8:58 AM, Feb 9, 2010.
SetCronJob didn't run cron jobs even when main server was up because of database corruption.
Secondary server didn't run cron jobs when main server was down, and I had solved its problem: the HP denied access through IP/~username.
From 8:59 AM, Feb 9, 2010, SetCronJob is ok and start running all cron jobs.
Please accept my apologize for the convenience this caused.
Nguyen An Thuan.