How does ct_runstatus affect the Urchin scheduler

How does ct_runstatus affect the Urchin scheduler?

Here’s specifically how ct_runstatus affects Urchin’s processing:

Suppose we have two profiles:

 

“sad.com” with ct_runstatus=3 “happy.com” with ct_runstatus=2

 

These actions will be successful:

 

/path/to/urchin/bin/urchin -p happy.com /path/to/urchin/bin/urchin -p sad.com * manually running happy.com through the web admin interface

 

These actions will be unsuccessful:

 

* manually running sad.com through the web admin interface * any scheduled profiles

 

So, to get things working in the long-run with automated processing, I recommend that you ensure that ct_runstatus=3 is nowhere present in the profiles. Your script didn’t come through in your last message so I can’t identify exactly why that failed. Doing so before or after using udb-sanitizer shouldn’t matter.