How can I cancel a stuck log processing task?

How can I cancel a stuck log processing task?

Scenario 1: Task is taking too much time

If you want to cancel a task because it taking too much time, you'll need to kill the log processing engine. You can do this on Unix by killing the "urchin" process and on Windows using the Process Manager.

NOTE: Do not simply delete the profile and recreate it. Although it no longer appears on the scheduler page, the task will remain stuck and the scheduler will remain blocked.

Scenario 2: System has crashed/rebooted unexpectedly

In this scenario, the task was running satisfactorily but the system was rebooted or crashed without the proper exit signals to the log processing engine and scheduler. This leaves the database entries for tasks in an inconsistent state. When the system boots up, the scheduler and log processing engine will not pick up that profile and the admin interface will erroneously show that the profile is running. If you attempt to schedule the same profile again, you'll get a message saying that the task is already queued/running.

In this case, the solution is to simply wait for 60 minutes. The master scheduler removes from the database all tasks that have not been updated in last the 60 minutes. Once the task has been removed, the admin schedule page will show the task status as "Error" and you'll be able to reschedule the profile.