[Bug] Ansible Systemd is running continously even after finished #53
Unanswered
NanoCode012
asked this question in
Q&A
Replies: 1 comment 2 replies
-
There are a few problems:
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, sorry to bother you again. I have found something interesting. I have upgraded my account to PayG and noticed that there were costs from Object Storage. After a while (and some misunderstandings), I finally realized that it came from Requests. It made around 2000 requests per day!
I checked the Ansible scripts and disabled the
backup-to-pihole.{timer|service}
to no avail. It turns out that thecloudblock-ansible-state.{timer|service}
was actually running all this time (for two whole months)! (Downloading the backup.tar.gz from buckets over and over). After runningjournalctl -u cloudblock-ansible-state.service
, I can retrieve the logs below. Unfortunately, it's been so long, so only the recent logs are here.It should be noted that the VM already works (can connect via Wireguard) and the files are already stored in the bucket. As a workaround, I disabled the ansible service script as well. I looked at the source and believe that it should not have ran at all every two minutes, only at boot.
One conjecture I have is that I rebooted the VM once to apply some security updates. Since the service script runs on boot, there could be a chance that it re-ran then met an error causing this infinite loop. If so, I propose changing the service script so that it disables later or find a way to run only once.
journalctl logs (this is repeated every two minutes in logs) Iteration: 24957
Beta Was this translation helpful? Give feedback.
All reactions