# Start EMQX
Start EMQX broker in the background
$ emqx start EMQX Broker v4.0.0 is started successfully!
$ sudo systemctl start emqx EMQX Broker v4.0.0 is started successfully!
$ sudo service emqx start EMQX Broker v4.0.0 is started successfully!
If you are using EMQX Enterprise, you need to import a license to use it. For the import steps, see Start EMQX Enterprise below.
EMQX Broker installed via ZIP archive does not support systemctl and service startup.
# Check the status of EMQX Broker
EMQX Broker starts normally:
$ emqx_ctl status Node 'firstname.lastname@example.org' is started emqx 4.0.0 is running
EMQX Broker failed to start normally:
$ emqx_ctl status Node 'email@example.com' not responding to pings。
After 4.2-rc.1, EMQX has added telemetry, Please learn more before starting.
# Start EMQX Enterprise
EMQX Enterprise needs a license file to start normally. EMQX can skip this step.
# Request a trial license
EMQX Enterprise requires a license file to start normally. EMQX Broker can skip this step.
Apply for a trial license file, then download the license file.
Replace the license file (
etc/emqx.lic) in the default certificate directory. You can also choose to change the read path of the certificate file, modify
etc/emqx.conffile, and make sure that the license file is in the updated read path and EMQX Enterprise has read permission. Then, start EMQX Enterprise. EMQX Enterprise is started in the same way as EMQX Broker.
If the running EMQX Enterprise cluster needs to update the license file, you can use the
emqx_ctl license reload [path of the license file]command to directly update the license file without restarting any nodes. It should be noted that the certificate loaded by the
emqx_ctl license reloadcommand will be applied to the whole EMQX cluster, and it will be saved in EMQX's data directory under the
data/licenses/emqx.lic) in each node. Even if the broker is restarted, this new license file will be loaded and applied.