Difference between revisions of "FAILED TickerTaskUpdate"
From Roaring Penguin
(Created page with "===Symptom=== <Hostname> FAILED TickerTaskUpdatexxxx <https://spamtrap.infowest.com/canit/manual/adminguide/pro/adminguide-proap12.php#RPS-ag-sanity-TickerTaskXXX> Task has no...") |
(→Remedy) |
||
| Line 19: | Line 19: | ||
where NameOfTask is one of the below without the prefix TickerTask. | where NameOfTask is one of the below without the prefix TickerTask. | ||
| − | + | * TickerTaskUpdateDNSBLPrefix | |
| − | + | * TickerTaskUpdateFromRPTN | |
| − | + | * TickerTaskUpdateGeo | |
| − | + | * TickerTaskUpdatePhishingLinks | |
| − | + | * TickerTaskUpdatePhishingList | |
| − | + | * TickerTaskUpdateRulesets | |
The rest will run as regularly scheduled and you should not see any more warnings. | The rest will run as regularly scheduled and you should not see any more warnings. | ||
Revision as of 10:36, 7 July 2016
Symptom
<Hostname> FAILED TickerTaskUpdatexxxx <https://spamtrap.infowest.com/canit/manual/adminguide/pro/adminguide-proap12.php#RPS-ag-sanity-TickerTaskXXX> Task has not run since yyyy
Remedy
This is typically the result of the canitd update task having stalled. To test, on the command line enter:
ps aux | grep canitd
A response line something like the following will usually indicate the stalled process:
1280 defang 20 0 168m 26m 4328 R 100.3 0.7 6241:12 canitd: GetUpdate
To resolve, restart CanIt and then manually scheduled an RPTN update and everything seems to be fine going forward.
To restart Canit from the command line enter:
/etc/init.d/canit-system restart
Then to schedule tasks:
/usr/share/canit/scripts/run-ticker-task.pl NameOfTask
where NameOfTask is one of the below without the prefix TickerTask.
- TickerTaskUpdateDNSBLPrefix
- TickerTaskUpdateFromRPTN
- TickerTaskUpdateGeo
- TickerTaskUpdatePhishingLinks
- TickerTaskUpdatePhishingList
- TickerTaskUpdateRulesets
The rest will run as regularly scheduled and you should not see any more warnings.
