Pratik Mankawde a24db2e995 docs: Document the [telemetry] TLS path readability check ...

Bring the three documentation surfaces in line with the new parse-time check:

- The @throws clause on makeTelemetrySetup now names the third failure
  condition and records that an empty path is skipped.
- cfg/xrpld-example.cfg states, under all three TLS keys, that with enabled=1
  and use_tls=1 a path that does not exist or cannot be read stops startup. The
  tls_ca_cert wording still says that empty selects the system CA store, since
  only a path that is set is checked.
- The runbook troubleshooting entry gains a third bullet for the "cannot be
  read" message, whose remedy is the path or its permissions rather than the
  certificate and key pairing.

Documentation only; no behaviour change.

2026-08-21 12:29:35 +01:00

..

validators-example.txt

…

xrpld-example.cfg

docs: Document the [telemetry] TLS path readability check

2026-08-21 12:29:35 +01:00