Otter Documentation

Service

The Otter Service is key component of Otter's architecture, and is what actually runs your plans using the execution engine. It's a standard Windows Service Application, and may be managed and configured using the Windows Service Manager or sc.exe as you see fit.

Managing the Service from the Otter Web Application

In addition to stopping and starting the Otter Service, you can see the service's live logs; this may be helpful when diagnosing problems or working with Inedo's support team to track down unexpected behavior or bugs.

Otter Administration Services

You can also manually trigger the task runners that the service would otherwise routinely execute. This should only be needed in debugging purposes, as the Web Application will trigger them in response to certain actions (such as editing a plan), and they are always executed on service start.

  • ServerCheckerTimedExecuter - this runs every hour, performs a lightweight handshake on each remote agent, and upgrades the agent as needed
  • JobDispatcherTimedExecuter - this runs every minute, checks for scheduled jobs, and executes those jobs as needed
  • RoutineConfigurationTimedExecuter - this runs every hour (you can change this with RoutineConfigurationExecutionThrottle in All Settings), and executes configuration plans for all severs
  • UpdateCheckerTimedExecuter - this runs every six hours (you disable this with Updates.PerformUpdateChecks in All Settings), and communicates with inedo.com for an updated version of the sofftware

Otter Service Configuration

By default, the Otter Service is named INEDOOTTERSVC, runs under the NetworkService account, and is granted Read, Write, ListDirectory privileges to the following paths:

  • ExecutionTempPath
  • ExtensionsPath
  • ExtensionsTempPath

If you choose to configure this as a custom domain account, it will be important to grant these same privileges.