Thanks, updated the environment. It now shows the expected log you was hoping for but didn’t fix the issue :\
When i try to restart gaia service i’m prompted still with the dependency error. And yes this instance was after first boot. I created a new instance to test your theory. The environment did pick up the info but i still received the same issue as below
darko@KWAMEs-MacBook-Air ~ % nmap -Pn 100.26.238.19 -p 22,80,443
Starting Nmap 7.80 ( https://nmap.org ) at 2020-06-23 16:02 EDT
Nmap scan report for ec2-100-26-238-19.compute-1.amazonaws.com (100.26.238.19)
Host is up (0.037s latency).
PORT STATE SERVICE
22/tcp open ssh
80/tcp closed http
443/tcp closed https
core@ip-172-31-61-77 ~ $ sudo systemctl status check-dns.service
● check-dns.service - Check DNS Record Service
Loaded: loaded (/etc/systemd/system/check-dns.service; disabled; vendor preset: disabled)
Active: inactive (dead) since Tue 2020-06-23 19:52:43 UTC; 4min 46s ago
Condition: start condition failed at Tue 2020-06-23 19:56:55 UTC; 35s ago
└─ ConditionPathExists=!/tmp/dns_checked was not met
Process: 25908 ExecStart=/bin/bash /gaia/scripts/check-dns.sh (code=exited, status=0/SUCCESS)
Main PID: 25908 (code=exited, status=0/SUCCESS)
Jun 23 19:52:43 ip-172-31-61-77 systemd[1]: Starting Check DNS Record Service…
Jun 23 19:52:43 ip-172-31-61-77 bash[25908]: Current epoch: 1592941963
Jun 23 19:52:43 ip-172-31-61-77 bash[25908]: End epoch: 1592942564
Jun 23 19:52:43 ip-172-31-61-77 bash[25908]: [ blockstackgaia.ga IN A 100.26.238.19 ] Matched 100.26.238.19
Jun 23 19:52:43 ip-172-31-61-77 systemd[1]: check-dns.service: Succeeded.
Jun 23 19:52:43 ip-172-31-61-77 systemd[1]: Started Check DNS Record Service.
Jun 23 19:53:48 ip-172-31-61-77 systemd[1]: Condition check resulted in Check DNS Record Service being skipped.
Jun 23 19:54:48 ip-172-31-61-77 systemd[1]: Condition check resulted in Check DNS Record Service being skipped.
Jun 23 19:55:54 ip-172-31-61-77 systemd[1]: Condition check resulted in Check DNS Record Service being skipped.
Jun 23 19:56:55 ip-172-31-61-77 systemd[1]: Condition check resulted in Check DNS Record Service being skipped.
core@ip-172-31-61-77 ~ $ sudo systemctl status letsencrypt-init.service
● letsencrypt-init.service - LetsEncrypt Init Service
Loaded: loaded (/etc/systemd/system/letsencrypt-init.service; disabled; vendor preset: disabled)
Active: inactive (dead) since Tue 2020-06-23 02:59:36 UTC; 17h ago
Condition: start condition failed at Tue 2020-06-23 20:00:02 UTC; 2s ago
└─ ConditionPathExists=!/tmp/letsencrypt.init was not met
Process: 631 ExecStart=/bin/bash -x /gaia/scripts/letsencrypt-init.sh (code=exited, status=0/SUCCESS)
Main PID: 631 (code=exited, status=0/SUCCESS)
Jun 23 19:50:29 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.
Jun 23 19:51:30 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.
Jun 23 19:52:31 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.
Jun 23 19:53:33 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.
Jun 23 19:54:34 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.
Jun 23 19:55:54 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.
Jun 23 19:56:55 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.
Jun 23 19:57:58 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.
Jun 23 19:59:00 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.
Jun 23 20:00:02 ip-172-31-61-77 systemd[1]: Condition check resulted in LetsEncrypt Init Service being skipped.