2014-06-11 18:01:36 +00:00
|
|
|
---
|
2020-04-07 18:55:19 +00:00
|
|
|
layout: docs
|
|
|
|
|
page_title: 'Commands: Reload'
|
2020-04-07 23:56:08 +00:00
|
|
|
sidebar_title: 'reload'
|
2020-04-07 18:55:19 +00:00
|
|
|
sidebar_current: docs-commands-reload
|
|
|
|
|
description: The `reload` command triggers a reload of configuration files for the agent.
|
2014-06-11 18:01:36 +00:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Consul Reload
|
|
|
|
|
|
|
|
|
|
Command: `consul reload`
|
|
|
|
|
|
2014-10-19 23:40:10 +00:00
|
|
|
The `reload` command triggers a reload of configuration files for the agent.
|
2014-06-11 18:01:36 +00:00
|
|
|
|
|
|
|
|
The `SIGHUP` signal is usually used to trigger a reload of configurations,
|
|
|
|
|
but in some cases it may be more convenient to trigger the CLI instead.
|
|
|
|
|
|
|
|
|
|
This command operates the same as the signal, meaning that it will trigger
|
|
|
|
|
a reload, but does not wait for the reload to complete. Any errors with the
|
|
|
|
|
reload will be present in the agent logs and not in the output of this command.
|
|
|
|
|
|
2014-11-26 03:03:14 +00:00
|
|
|
**NOTE**
|
|
|
|
|
|
|
|
|
|
Not all configuration options are reloadable. See the
|
2020-04-09 23:46:54 +00:00
|
|
|
[Reloadable Configuration](/docs/agent/options#reloadable-configuration)
|
2014-11-26 03:03:14 +00:00
|
|
|
section on the agent options page for details on which options are supported.
|
|
|
|
|
|
2014-06-11 18:01:36 +00:00
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
Usage: `consul reload`
|
|
|
|
|
|
2017-02-10 00:32:22 +00:00
|
|
|
#### API Options
|
2014-06-11 18:01:36 +00:00
|
|
|
|
2020-04-07 18:55:19 +00:00
|
|
|
@include 'http_api_options_client.mdx'
|
