Re: Problem with cron jobs

On Wed, 3 May 2006 at 13:55, Michael Yount wrote about "Re: Problem with...":

> The trigger program handles one domain at a time, and one list at a time, 
> starting with GLOBAL.  If the tokens for a particular list are not expiring, 
> you need to figure out what tasks run at the same time as that list's token 
> update, for that domain and every domain that appears earlier in the list of 
> domains at your site.

In what order does the trigger program go thru the domains?

> One easy step would be to use the "showtokens ALL" command to find the first 
> domain that shows old tokens.  Chances are that the trigger problem is caused 
> by that domain or the previous domain.

If I ran "mj_trigger -t token" manually every day, and that *does* manage 
to clear out tokens, then why wouldn't the hourly or lock cron jobs 
(put in during installation) be able to? Is there something different 
that's happening here?

> Are you running mj_trigger with the "-v 700" switch to get full debugging 
> information?

I ran it with 1000 a few months ago, and after skimming thru hundreds of 
lines of logs, I couldn't find anything relevant.

Thanks,

-- 
Brock Rozen                                        [email protected]