public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 04:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #361 from btat/pr-352

Browse Source 
Apply 280e1bf1 (PR #352) to version 2.6 docs
This commit is contained in:
Billy Tat
2023-01-06 15:44:50 -08:00
committed by GitHub
parent 743dd5e1f3 2443738598
commit e3f43e64df
2 changed files with 25 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/troubleshooting/other-troubleshooting-tips/logging.md
+2
View File
@@ -2,6 +2,8 @@
title: Logging
---
## Log levels
The following log levels are used in Rancher:
| Name | Description |
versioned_docs/version-2.6/troubleshooting/other-troubleshooting-tips/logging.md
+23
View File
@@ -2,6 +2,8 @@
title: Logging
---
## Log levels
The following log levels are used in Rancher:
| Name | Description |
@@ -51,3 +53,24 @@ $ docker logs -f <container_id>
$ docker exec -ti <container_id> loglevel --set info
OK
```
## Rancher machine debug logs
If you need to troubleshoot the creation of objects in your infrastructure provider of choice, `rancher-machine`
debug logs might be helpful to you.
It's possible to enable debug logs for `rancher-machine` by setting environment variables when launching Rancher.
The `CATTLE_WHITELIST_ENVVARS` environment variable allows users to whitelist specific environment variables to be
passed down to `rancher-machine` during provisioning.
The `MACHINE_DEBUG` variable enables debug logs in `rancher-machine`.
Thus, by setting `MACHINE_DEBUG=true` and adding `MACHINE_DEBUG` to the default list of variables in
`CATTLE_WHITELIST_ENVVARS` (e.g. `CATTLE_WHITELIST_ENVVARS=HTTP_PROXY,HTTPS_PROXY,NO_PROXY,MACHINE_DEBUG`) it is
possible to enable debug logs in `rancher-machine` when provisioning RKE1, RKE2 and k3s clusters.
:::caution
Just like the `trace` log level above, `rancher-machine` debug logs can contain sensitive information.
:::