====== CPU spikes because task handler service reports it is already started ======

===== Problem Description =====
CPU spikes because the task handler service continuously try to start and logs the following error messages:

<code>
ERROR: Pidfile (C:\ProgramData\Lundalogik\LIME Pro Server\Task Handler\task-handler.pid) already exists.
Seems we're already running? (pid: 2064)
ERROR: Pidfile (C:\ProgramData\Lundalogik\LIME Pro Server\Task Handler\task-handler.pid) already exists.
Seems we're already running? (pid: 2064)
ERROR: Pidfile (C:\ProgramData\Lundalogik\LIME Pro Server\Task Handler\task-handler.pid) already exists.
Seems we're already running? (pid: 2064)
</code>

===== Solution =====
We recommended a upgrade to solve this issue, but there also is a manual patch available.

==== Upgrade ====
Upgrade to latest [[releases:pro:start|Lime CRM Server]].

==== Manual Patch ====

  - Open Registry Editor on the Lime server.
    - Go to key:<code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lime-task-handler\Parameters</code>Change AppParameters from:<code>worker -A lime_task.worker -n taskhandler1@%h -l warning --pidfile "C:\ProgramData\Lundalogik\LIME Pro Server\Task Handler\task-handler.pid" -P gevent --concurrency 2</code>To:<code>worker -A lime_task.worker -n taskhandler1@%h -l warning --pidfile= -P gevent --concurrency 2</code>{{:kb:regedit-task-handler-app-parameters.jpg?direct|}}
     - Go to key:<code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lime-task-scheduler\Parameters</code>Change AppParameters from (**remember that the install path might differ!**):<code>beat -A lime_task.worker --pidfile "C:\ProgramData\Lundalogik\LIME Pro Server\Task Handler\task-scheduler.pid" -s "C:\ProgramData\Lundalogik\LIME Pro Server\Task Handler\celerybeat-schedule" -l warning</code>To:<code>beat -A lime_task.worker --pidfile= -s "C:\ProgramData\Lundalogik\LIME Pro Server\Task Handler\celerybeat-schedule" -l warning</code>
  -   Restart Lime Task Service
  -   Restart Lime Task Scheduler