User Tools
support:general_resolutions
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| support:general_resolutions [2021/05/19 09:59] – created aryan | support:general_resolutions [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== General Resolutions ====== | ||
| + | General resolutions are a category of general tips/tricks or observations and how to resolve them ranging from server service tips to deployment hacks. The goal is to provide a findable category of problems which have been encountered before and can be resolved | ||
| + | |||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== DNS won't resolve ===== | ||
| + | |||
| + | If on a server when executing the ```dig``` command you receive | ||
| + | |||
| + | < | ||
| + | scotty@heimdall: | ||
| + | |||
| + | ; <<>> | ||
| + | ;; global options: +cmd | ||
| + | ;; connection timed out; no servers could be reached | ||
| + | </ | ||
| + | |||
| + | Check the **systemd-resolved.service** as if this isn't running the DNS will not be resolved. | ||
| + | |||
| + | < | ||
| + | |||
| + | | ||
| + | | ||
| + | Docs: man: | ||
| + | | ||
| + | | ||
| + | | ||
| + | Main PID: 31511 (systemd-resolve) | ||
| + | | ||
| + | Tasks: 1 (limit: 4915) | ||
| + | | ||
| + | | ||
| + | |||
| + | |||
| + | </ | ||
| + | |||
| + | |||
| + | ===== Prometheus Logs Missing ===== | ||
| + | |||
| + | As of 2.x Prometheus no longer writes log files to the expected / | ||
| + | |||
| + | For example to access the prometheus logs we use | ||
| + | < | ||
| + | sudo journalctl -u prometheus -f | ||
| + | </ | ||
| + | |||
| + | To access an exporter stdout for troubleshooting you would use | ||
| + | < | ||