Starting and stopping Funnelback services

This feature is not available to users of the Squiz Experience Cloud version of Funnelback.

This outlines how to start, stop and restart Funnelback services such as the Jetty web server, Redis, daemon and graph service.

Note that each service is independent, and restarts may occur in any order. Running collection update operations, however, may update values in the redis service, so restarting redis should be avoided while updates are in progress.


On Centos 7 Funnelback uses systemctl for services. The systemctl command must be run as root and takes two argments - the name of the service and:

  • start to start the service

  • stop to stop the service

  • restart to restart the service

Jetty web server

/bin/systemctl start funnelback-jetty-webserver
/bin/systemctl stop funnelback-jetty-webserver
/bin/systemctl restart funnelback-jetty-webserver

Redis service

/bin/systemctl start funnelback-redis
/bin/systemctl stop funnelback-redis
/bin/systemctl restart funnelback-redis

Daemon service

/bin/systemctl start funnelback-daemon
/bin/systemctl stop funnelback-daemon
/bin/systemctl restart funnelback-daemon

Graph service

/bin/systemctl start funnelback-graph
/bin/systemctl stop funnelback-graph
/bin/systemctl restart funnelback-graph


On Windows Funnelback services can be controlled running the Services snap-in found under administrative tools (typically searching for "services" in windows search will find services tool). Services can only be controlled by an Administrator. A service can be started, stopped or restarted by right clicking on the service and clicking the appropriate option. The following is a list of Funnelback services.

  • funnelback-jetty-webserver: Jetty web server

  • funnelback-redis: Redis

  • funnelback-graph: Funnelback graph

  • funnelback-daemon: Daemon Services