Live walkthrough finding: with pools[0].url pointed at an unresolvable host, the rig is 100% not mining (xmrig loops on DNS error: "temporary failure" every ~5s) — yet:
sudo ./rigforge.sh doctor prints all critical checks passed (it checks HugePages, MSR, governor, service-active… no pool-connectivity check exists at all);sudo ./rigforge.sh apply with the broken hostname reports [INFO] Applied config and restarted xmrig. with no warning (URL validation is format-only).
The one-stop health command and the config-apply path are both blind to the rig's actual purpose. Two cheap closes: doctor gains a "pool reachable / last accepted share age" check (read xmrig's own summary: connection state + last share timestamp — no new probe needed), and apply prints a warning when the freshly-applied pool fails a quick resolve/connect test (warn, not refuse — the pool may be legitimately down at apply time).
Live walkthrough finding: with
pools[0].urlpointed at an unresolvable host, the rig is 100% not mining (xmrig loops onDNS error: "temporary failure"every ~5s) — yet:sudo ./rigforge.sh doctorprints all critical checks passed (it checks HugePages, MSR, governor, service-active… no pool-connectivity check exists at all);sudo ./rigforge.sh applywith the broken hostname reports[INFO] Applied config and restarted xmrig.with no warning (URL validation is format-only).The one-stop health command and the config-apply path are both blind to the rig's actual purpose. Two cheap closes: doctor gains a "pool reachable / last accepted share age" check (read xmrig's own summary: connection state + last share timestamp — no new probe needed), and apply prints a warning when the freshly-applied pool fails a quick resolve/connect test (warn, not refuse — the pool may be legitimately down at apply time).