Run the ERDAICC diagnostic shell (if available) or query the system tables:
-- For PostgreSQL-based ERDAICC backends
SELECT error_code, COUNT(*) FROM erdaicc_audit_log
WHERE timestamp > NOW() - INTERVAL '1 hour'
AND message LIKE '%ERDAICC%'
GROUP BY error_code ORDER BY 2 DESC;
Look for recurring E-422 (metadata mismatch) or E-429 (lock timeout). If the same error repeats after the "fixed" message, auto-repair is failing. erdaicc fixed
Example: erdaicc(fix): fixed null pointer when parsing config [blank line] Parsing returned nil for missing "timeout" field, causing a panic in erdaicc's Init(). Add safe lookup with default and unit tests to cover missing-field cases. [blank line] Fixes: #1234 Run the ERDAICC diagnostic shell (if available) or
We’ve also added a new GET /_health/erdaicc endpoint that returns the current chain correction status. It will output "status": "fixed" (yes, really) when everything is nominal. Look for recurring E-422 (metadata mismatch) or E-429
To ensure that the erdaicc fixed log entry is genuine and not a mask for deeper issues, implement these ongoing practices:
On Unix-like systems, if the /tmp or /var/erdaicc partition runs out of inodes (not just space), the compiler cannot create temporary lock files, leading to the error.
The error often appears when the service account running the compiler lacks write or modify permissions on temporary directories or shared memory segments.