Find an error by its reference
This task is for service-desk staff and administrators. An Exponential error page shows a reference such as
ERR-0123456789; the same reference is in the log line, so a report from a citizen leads straight to the cause.
Guide: Finding an error by its reference.
Contents
Before you start
- The reference from the report (ask the citizen for it and the time; a screenshot helps).
setup/logs, or shell access.
In the administration
- Setup > Log files.
- Search for the reference (the search accepts an error reference) across the kernel logs, with rotations if the report is older.
- Open the line: the viewer shows the message, file and line, and the other lines of the same request, linked to the audit records of the same minute.
- Copy permalink for the ticket.
On the shell
./console exp:logs --reference=ERR-0123456789It says where the reference is and prints the lines of its request. Exit 0 found, 1 not found.
Next steps
| Line says | Do |
|---|---|
| a template or code error | developer ticket with the permalink |
| a database error | Database unreachable |
| a missing file or permission | Check file and directory permissions |
| not found at all | the report may be from another server or engine; search there, or with --rotations for older logs |
Reply to the citizen without technical detail; personal data in the report stays in your ticket system.
Related pages
- Read the error digest
- The log viewer
- Site down
- When something goes wrong (help)
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.