[Bug] Cron jobs failing due to stale server references and stopped service dependencies

Status Open
Reported on v2.1.210
Maintainer reply None cached
Activity 0 comments · opened Jul 20, 2026

Bug Description
we were not engaging any cybersecurity topic. we are working on the homelab and sorting ips and chron jobs. I'm not sure what cybersecurity thing we could have been doing. This is the last few things claude was doing:

Found a second broken job with a clear timeline — git-backup-websites worked fine on 07-17 and 07-18, then broke last night (07-19) when its target directory vanished from srvr01 mid-migration. And update-core-memory (runs every 30 min, feeds the always-loaded core_memory.md) is hitting Radarr/Sonarr/qBittorrent on localhost — all of which are now stopped containers.

Ran 6 shell commands

This is a real, dated data-protection gap: tcl-crm backups stopped on July 16 — 4 days with zero backups of a healthcare business's CRM data. Let me look at the rest of update-core-memory to decide where it belongs, then fix all four srvr01 jobs properly (relocate to where the data now actually lives, not just patch an IP).

Ran 1 shell command

Rather than patch IPs piecemeal, I'll relocate these four jobs to apps01 (where the data and services actually live now) and retire the dead entries on srvr01. Starting with the git ownership issue blocking the website backup.

Ran 3 shell commands

Good — those are just file-mode changes from the migration copy (644→755), zero content diff. I'll tell git to ignore file-mode changes so it doesn't generate noise commits, confirm a clean tree, then set up the real fix.

Made 3 scratchpad edits +63, ran 3 shell commands

Confirmed correct. Now the update-core-memory rewrite — pointed at apps01 (the live app host) instead of srvr01, with the DC health check made more robust (direct Kerberos check instead of a single domain-member's testjoin).

Environment Info

  • Platform: linux
  • Terminal: vte-based
  • Version: 2.1.210
  • Feedback ID: 8d3b052c-7c26-4460-9c54-58b27623ad8f

Errors

[]

View original on GitHub ↗