Funnelback Services

The installer sets up various OS services needed for Funnelback to function properly. On Windows these services can be administered via the Administrative Tools / Services control panel, whereas on Linux each service has a corresponding /etc/init.d/ script.

Please find below a short description of each service.


This service is an umbrella for various subservices. The list of services to start can be configured in global.cfg using Available subservices are:- FilterService: Provides an HTTP interface to the text filtering system. Required for TRIMPush collections

  • GenerateCertificates: Generates SSL certificates needed by Matrix collections
  • RemoveStaleLocks: Remove collection update locks left over after an unexpected system reboot.
  • TRIMWatcher: Watch any changes in TRIM records to re-gather them as soon as possible. Required for advanced TRIMPush collections with a TRIM event processor.
  • WebDavService: Provides a WebDAV interface to the Funnelback installation folder, to support transferring files in multiple query processors configurations.


This service runs the embedded webserver (Jetty) that provides the administration interface as well as the search results interface and most Funnelback API services.


This service runs Redis, a third party key-value store. Redis is used to store information about collection update progress and status, and is required for the administration interface to function properly.

Service configuration

Each service can be configured through its configuration file in $SEARCH_HOME/services/<service>.service.

These service files are generated by $SEARCH_HOME/bin/setup/ This script is run once during the Funnelback installation to generate the service files, and register the services on the OS. If you run this script again, the services files will be re-generated and overwritten. Each service file is based on a template used by, from $SEARCH_HOME/bin/setup/service-templates/. Modifications made in these templates will be kept when is run, but these files are overwritten during an upgrade.

Service troubleshooting

Each service produces 2 log files, in $SEARCH_HOME/log/:

  • A <service>-wrapper.log file containing the log of the service wrapper process (in charge of monitoring and restarting the actual service)
  • A <service>.log file with the messages from the actual service.