yeah, I was also thinking that the 6 AM script running too long could interfere with the 1PM script starting - but shouldn't cron throw an error then ? (IIRC Ubuntu server drops those in the root mailbox)
Hunch: the 6PM script sets a lock on certain resources (eg files, or maybe database tables), the 1 PM jobs fails because the resources are still in use and it can not access them; by the next day the locks are released or have timed out so the 6AM job starts again just fine.
The timings from the COg's wrapper should indicate whether this is the case. ...
Bookmarks