luxolus/open-consul
2
0
Fork 0
Code Issues 1 Pull requests Packages Releases Wiki Activity

Update check script exit code explanation (#3882)

Browse source 
Change misleading formulation which might imply, that any non-zero code is enough to mark check as failing.
(https://www.consul.io/docs/agent/checks.html#check-scripts)
This commit is contained in:
Tomáš Bedřich 2018-02-11 15:30:40 +01:00 committed by Preetha
parent 7100161f64
commit 054b06a876
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
website/source/intro/getting-started/checks.html.md
View file

@ -45,13 +45,14 @@ vagrant@n2:~$ echo '{"service": {"name": "web", "tags": ["rails"], "port": 80,
The first definition adds a host-level check named "ping". This check runs
on a 30 second interval, invoking `ping -c1 google.com`. On a `script`-based
health check, the check runs as the same user that started the Consul process.
If the command exits with a non-zero exit code, then the node will be flagged
unhealthy. This is the contract for any `script`-based health check.
If the command exits with an exit code >= 2, then the check will be flagged as
failing and the service will be considered unhealthy. This is the contract
for any `script`-based health check.
The second command modifies the service named `web`, adding a check that sends a
request every 10 seconds via curl to verify that the web server is accessible.
As with the host-level health check, if the script exits with a non-zero exit code,
the service will be flagged unhealthy.
As with the host-level health check, if the script exits with an exit code >= 2,
the check will be flagged as failing and the service will be considered unhealthy.
Now, restart the second agent, reload it with `consul reload`, or send it a `SIGHUP` signal. You should see the
following log lines: