Reloading configuration files

GET /reload

This endpoint reloads the Smart Beat Manager configuration files without restarting the service. When the request is executed, Smart Beat Manager:

1. Recreates the application archives.
2. Recalculates the data in the app and binary archives.
3. Recalculates the archive checksums.
4. Updates the configuration files.

Request requirements

The curl command can be run by any operating system user who has access to the curl utility and a network connection to the Smart Beat Manager REST API. root privileges and execution as the sbm system user are not required.

The -u option specifies a Smart Monitor account for HTTP Basic Authentication, not an operating system user. Use a user with full access to Smart Beat Manager:

• the admin user
• a user with the all_access role
• a user with a role that includes the cluster:admin/sm/sbm/all_access cluster permission

The cluster:admin/sm/sbm/read_only permission provides read-only access and cannot be used to reload the configuration. For more information, see Verifying Smart Beat Manager permissions.

Replace <SBM_HOST> with the address of the host where the Smart Beat Manager REST API is available on port 7769. This address may be the same as the Smart Monitor Web host address only if both services are installed on the same host or requests are forwarded to Smart Beat Manager.

Reloading the configuration through the API without restarting the service

After modifying the configuration files, run the following request:

curl -k -XGET https://<SBM_HOST>:7769/reload -u admin
curl -k -XGET https://<SBM_HOST>:7769/reload -u admin

The command prompts for the admin user password interactively. You can specify another user with full access to Smart Beat Manager instead of admin. After the request completes successfully, you do not need to restart the Smart Beat Manager service with systemctl.

TLS Certificate Verification

The -k option disables verification of the server's TLS certificate. If the certificate is signed by a trusted certificate authority, omit -k. If you use your own certificate authority, specify its certificate with the --cacert <CA_CERT_PATH> option.

The command prompts for the admin user password interactively. Instead of admin, you can specify another user with full access to Smart Beat Manager. After the request completes successfully, you do not need to restart the Smart Beat Manager service using systemctl.

TLS certificate verification

The -k option disables server TLS certificate verification. Do not use -k if the certificate is signed by a trusted certificate authority. For a private certificate authority, provide its certificate using the --cacert <CA_CERT_PATH> option.

Header parameters

Name	Type	Description
Authorization	string	Base64-encoded username and password used to authenticate with Smart Beat Manager
Name	Type	Description
-------------	------	------------------------------------------------------------------
Authorization	string	Base64-encoded login and password for Smart Beat Manager authorization

Response

A message confirming that the configuration was reloaded successfully, or an error.

Status	Error message	Description
400	Server reloads now	The server is already reloading data. Retry the request in a few seconds.

Examples

Example response:

Success reread config: smartBeatManager
Success reread config: serverclasses
Success reread config: apps