RCTD 404: What You Need to Know

1. The team edited /etc/rctd/storage_mounts.conf.
2. Changed base_path = /mnt/san01/videos to base_path = /mnt/nas02/media.
3. Reloaded the RCTD daemon: sudo kill -HUP $(pidof rctd)
4. The daemon rescanned the new location and resolved all 404 errors within 3 minutes.

Evidence to collect

1. Exact request that triggered the 404 (HTTP method, full URL, query string, headers).
2. Server logs (access and error logs) for the timestamp of the request.
3. Application logs for the rctd component around the same time.
4. Configuration files: routing/ingress, proxy, virtual hosts, API gateway, and service registry.
5. Deployment status of rctd service (process, container, pod status).
6. DNS records and TLS/SSL hostnames used.
7. Recent changes or deployments that could have affected paths or routing.

Solution C: Fixing Permission Issues

If the file exists but RCTD cannot read it: