Funnelback system services
- Funnelback daemon service (funnelback-daemon)
- Jetty web server (funnelback-jetty-webserver)
- Funnelback graph service (funnelback-graph)
- Redis (funnelback-redis)
- Service configuration
- Service troubleshooting
- Starting and stopping services
- See also
|This feature is not available to users of the Squiz Experience Cloud version of Funnelback.|
The installer sets up various OS services needed for Funnelback to function properly. On Windows these services can be administered via the Windows Administrative Tools / Services control panel, whereas on Linux each service has a corresponding
This service is an umbrella for various subservices. The list of services to start can be configured in global.cfg using
daemon.services. Available subservices are:
GenerateCertificates: Generates SSL certificates needed by Squiz 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 Neo4j which is used to provide knowledge graph services for Funnelback.
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.
Funnelback utilises the system mail service to handle delivery of email notification.
Under Linux, the built-in sendmail service is used.
Under Windows, BLAT is used to configure Funnelback to use an existing SMTP server. See: Changing the email server on Windows
Each service can be configured through its configuration file in
These service files are generated by
$SEARCH_HOME/bin/setup/start_funnelback_on_boot.pl. 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
$SEARCH_HOME/bin/setup/service-templates/. Modifications made in these templates will be kept when
start_funnelback_on_boot.pl is run, but these files are overwritten during an upgrade.
There are a number of settings that can be configured relating to the Jetty web server.
SSL certificate installation
Memory defaults which are written to the service files can be adjusted by adding or updating the relevant settings within the
global.cfg. The default values can be viewed in the
Jetty web server:
Values for these settings are in the form accepted by Java’s
-Xmx option (e.g. 128m).
Please note that after changing these settings, the service files must be regenerated and reinstalled by running
Each service produces two log files, in
$SEARCH_HOME/log/ which are rotated:
<service>-wrapper.logfile containing the log of the service wrapper process (in charge of monitoring and restarting the actual service)
<service>.logfile with the messages from the actual service.
Funnelback services are managed using the host operating system’s service management interface.
Linux services are managed using
init.dscripts and started, stopped and restarted using the
Windows services are managed using the services control panel.