search

d2iq-archive / mesos-dns

DNS-based service discovery for Mesos.
https://mesosphere.github.com/mesos-dns
Apache License 2.0
483 stars 137 forks source link

mesos-dns is not working #540

Closed govindbhardwaj closed 5 years ago

govindbhardwaj commented 5 years ago

I am having following logs when try journalctl -u dcos-mesos-dns -b. Please help me resolve it.

Jun 01 18:35:38 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service holdoff time over, scheduling restart.
Jun 01 18:35:38 HEPC-UHDH-VM32 systemd[1]: Stopped Mesos DNS: domain name based service discovery.
Jun 01 18:35:38 HEPC-UHDH-VM32 systemd[1]: Failed to load environment files: No such file or directory
Jun 01 18:35:38 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service failed to run 'start-pre' task: No such file or directory
Jun 01 18:35:38 HEPC-UHDH-VM32 systemd[1]: Failed to start Mesos DNS: domain name based service discovery.
Jun 01 18:35:38 HEPC-UHDH-VM32 systemd[1]: Unit dcos-mesos-dns.service entered failed state.
Jun 01 18:35:38 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service failed.
Jun 01 18:35:43 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service holdoff time over, scheduling restart.
Jun 01 18:35:43 HEPC-UHDH-VM32 systemd[1]: Stopped Mesos DNS: domain name based service discovery.
Jun 01 18:35:43 HEPC-UHDH-VM32 systemd[1]: Failed to load environment files: No such file or directory
Jun 01 18:35:43 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service failed to run 'start-pre' task: No such file or directory
Jun 01 18:35:43 HEPC-UHDH-VM32 systemd[1]: Failed to start Mesos DNS: domain name based service discovery.
Jun 01 18:35:43 HEPC-UHDH-VM32 systemd[1]: Unit dcos-mesos-dns.service entered failed state.
Jun 01 18:35:43 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service failed.
Jun 01 18:35:48 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service holdoff time over, scheduling restart.
Jun 01 18:35:48 HEPC-UHDH-VM32 systemd[1]: Stopped Mesos DNS: domain name based service discovery.
Jun 01 18:35:48 HEPC-UHDH-VM32 systemd[1]: Failed to load environment files: No such file or directory
Jun 01 18:35:48 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service failed to run 'start-pre' task: No such file or directory
Jun 01 18:35:48 HEPC-UHDH-VM32 systemd[1]: Failed to start Mesos DNS: domain name based service discovery.
Jun 01 18:35:48 HEPC-UHDH-VM32 systemd[1]: Unit dcos-mesos-dns.service entered failed state.
Jun 01 18:35:48 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service failed.
Jun 01 18:35:53 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service holdoff time over, scheduling restart.
Jun 01 18:35:53 HEPC-UHDH-VM32 systemd[1]: Stopped Mesos DNS: domain name based service discovery.
Jun 01 18:35:53 HEPC-UHDH-VM32 systemd[1]: Failed to load environment files: No such file or directory
Jun 01 18:35:53 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service failed to run 'start-pre' task: No such file or directory
Jun 01 18:35:53 HEPC-UHDH-VM32 systemd[1]: Failed to start Mesos DNS: domain name based service discovery.
Jun 01 18:35:53 HEPC-UHDH-VM32 systemd[1]: Unit dcos-mesos-dns.service entered failed state.
Jun 01 18:35:53 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service failed.
Jun 01 18:35:58 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service holdoff time over, scheduling restart.
Jun 01 18:35:58 HEPC-UHDH-VM32 systemd[1]: Stopped Mesos DNS: domain name based service discovery.
Jun 01 18:35:58 HEPC-UHDH-VM32 systemd[1]: Failed to load environment files: No such file or directory
Jun 01 18:35:58 HEPC-UHDH-VM32 systemd[1]: dcos-mesos-dns.service failed to run 'start-pre' task: No such file or directory
Jun 01 18:35:58 HEPC-UHDH-VM32 systemd[1]: Failed to start Mesos DNS: domain name based service discovery.

DCOS version I am using, 1.10 open-source on production environment. There are one master and one private agent node. On DCOS dashboard the node health is showing N/A but showing CPU consumption of the node.

govindbhardwaj commented 5 years ago

Using my dns resolver in config.yaml solved the issue.