Starting and Stopping

All Fusion start scripts must be executed by a user who has permissions to read and write to the directories where Fusion is installed.

These scripts don’t need to be run as root (or using sudo), nor should they be. Use a suitable ID, or create a new one, and then ensure that it owns the directory where Fusion resides, such as /opt/fusion (on Unix) or C:\lucidworks\fusion (on Windows).

For information about default ports, see Directories, Files, and Ports in the Deployment Guide.

Start and stop Fusion

Give these commands from the bin directory below the Fusion home directory, for example, /opt/fusion/4.1.x (on Unix) or C:\lucidworks\fusion\4.1.x (on Windows).

Unix Windows

All Fusion services

Start all required services

./fusion start

fusion.cmd start

Run Fusion in the foreground

./fusion run

fusion.cmd run

Display system status

./fusion status

fusion.cmd status

Restart all Fusion services

./fusion restart

fusion.cmd restart

Stop all Fusion services

./fusion stop

fusion.cmd stop

Individual services

Fusion UI service

./admin-ui start

admin-ui.cmd start

API services

./api start

api.cmd start

Classic connectors

./connectors-classic start

connectors-classic.cmd start

RPC connectors

./connectors-rpc start

connectors-rpc.cmd start

Log Shipper

./log-shipper start

log-shipper.cmd start

Proxy service

./proxy start

proxy.cmd start


./solr start

solr.cmd start

Spark Master

./spark-master start

spark-master.cmd start

Spark Worker

./spark-worker start

spark-worker.cmd start

SQL service

./sql start

sql.cmd start

Web Apps service

./webapps start

webapps.cmd start


./zookeeper start

zookeeper.cmd start

Run Fusion in the foreground

To run Fusion or any of its services in the foreground, use the run command-line argument in place of start.

Stop Fusion

To stop Fusion or any of its services, use the stop command-line argument in place of start.