2 parser issues

[DBowsky]

Hi, me again.

Got two issues at the moment that are perplexing me:

1. Under the Scheduler: Pop3 checker and inbound Parser are set to run every minute. They are not running, in order to bring in mail I have to manually click "run now." Did I miss a configuration step?

Scratch the second one, I was missing a wildcard in the routing rule.

Thoughts?

Version info: 4.0 RC1 (Build 603)

[dsugita]

Hey there,
The pop3 checker/parser still needs something to hit the page to run it (which is why it works if you click run now), you just need to set up an external scheduled task/cron job: http://wiki.cerberusdemo.com/index.php/Getting_Started#Scheduled_Tasks

[DBowsky]

Thanks, but I am a little confused.

Since Cerberus Helpdesk is inactive when nobody is signed on, in the future we'll want to configure an external cron-job (Linux) or scheduled task (Windows) to ping this URL and make sure our scheduled tasks run without human prompting.

The above implies that the cron-job is for times when no one is logged into the system. I'm not seeing them run while people are logged in.

Also, why is there a setting for how often to run those tasks if you have to configure that externally through cron?

Just asking :)

[Hildy]

A) To run it while someone *is* logged in, just load the /cron page (via the "Simple: automatically run jobs in a browser window" link) and leave it open. The page will refresh every x seconds (30?) and run the scheduled tasks when they're available.

B) I used the word available above because the time settings on your Scheduler page are a maximum frequency, not a minimum frequency. If you have the Parser set to run every 5 minutes, it will only run once every five minutes regardless of how often you hit that cron url. The jobs lock themselves when running, and if you have a lengthy or complicated job, hitting it too frequently will just result in locked-process reports, not running it more frequently.

[DBowsky]

A) To run it while someone *is* logged in, just load the /cron page (via the "Simple: automatically run jobs in a browser window" link) and leave it open. The page will refresh every x seconds (30?) and run the scheduled tasks when they're available.

B) I used the word available above because the time settings on your Scheduler page are a maximum frequency, not a minimum frequency. If you have the Parser set to run every 5 minutes, it will only run once every five minutes regardless of how often you hit that cron url. The jobs lock themselves when running, and if you have a lengthy or complicated job, hitting it too frequently will just result in locked-process reports, not running it more frequently.

So basically if I want "fire and forget" I should just cron-ping the page at an interval that equals my shortest interval on the jobs page.

If that results in something trying to run whilst locked, no messages are lost, correct?

[Hildy]

Yep, that's the best way. If it tries to run while it's still locked, it'll just skip that one and wait til the next time it's called. (Locks do timeout after a set period (I think 15 minutes) in case of a crash while locked.)