Process: 22507 ExecStart=/home/prometheus/prometheus/prometheus -config.file=/home/prometheus/prometheus/prometheus.yml =/app/prometheus/data (code=exited, status=2)ĭec 02 11:12:33 systemd: Unit rvice entered failed state.ĭec 02 11:12:33 systemd: rvice failed.ĭec 02 11:12:33 systemd: rvice holdoff time over, scheduling restart.ĭec 02 11:12:33 systemd: start request repeated too quickly for rviceĭec 02 11:12:33 systemd: Failed to start Prometheus Server.ĭec 02 11:12:33 systemd: rvice ~]$ Loaded: loaded (/etc/systemd/system/rvice enabled vendor preset: disabled)Īctive: failed (Result: start-limit) since Mon 11:12:33 UTC 4s ago When I check if prometheus is running I get this: ~]$ sudo systemctl status prometheus # The job name is added as a label job= to any timeseries scraped from this config. # A scrape configuration containing exactly one endpoint to scrape: # Load rules once and periodically evaluate them according to the global evaluation_interval. # scrape_timeout is set to the global default (10s). Default is every 1 minute.Įvaluation_interval: 15s # Evaluate rules every 15 seconds. Scrape_interval: 15s # Set the scrape interval to every 15 seconds. But if you are using docker desktop as your production env, then you need to reconsider some of your life choices.I installed prometheus on Amazon linux 2 instance and Here is my configurations I use in the user data: cat /etc/systemd/system/rviceĮxecStart=/home/prometheus/prometheus/prometheus -config.file=/home/prometheus/prometheus/prometheus.yml =/app/prometheus/dataĬat /home/prometheus/prometheus/prometheus.yml Prometheus should work fine on your production clusters. But on the bright side, this is a docker desktop issue. It means this is a workaround and not a solution. If you are using the prometheus-node-exporter chart directly, then you can install it with -set hostRootFsMount.enabled=false BUTīear in mind that by disabling mount propagation node-exporter won't be able to collect all data needed for grafana dashboards and for alerts. I am using kube-prometheus-stack chart in my case, and it contains the dependency of node exporter with the name prometheus-node-exporter, thus the first line of the yaml contains prometheus-node-exporter, and it can be different if the name of the dependency is different for the chart you are using. Helm install prom prometheus-community/kube-prometheus-stack -set =false You can turn off the hostRootFsMount, of course, by using the kubectl patch as suggested by Ali's answer, or you can use helm install prom prometheus-community/kube-prometheus-stack -f node-exporter-workaround.yaml Bind propagation is an advanced topic and many users never need to configure it. It is only configurable for bind mounts, and only on Linux host machines. Now, take a look at the docker documentation::īind propagation defaults to rprivate for both bind mounts and volumes. # None, HostToContainer, and Bidirectional. # are propagated to the container or node, respectively. # Defines how new mounts in existing mounts on the node or in the container Take a look at the values.yaml from prometheus-node-exporter # Mount the node's root file system (/) at /host/root in the container Only people using Kubernetes on the docker desktop should be the ones facing the issue. This is not an issue of node exporter or helm chart or Kubernetes or docker but a limitation of docker desktop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |