This article explains how to check the access.log
and related logs to troubleshoot 503 and 500 errors, which can be caused by traffic or insufficient server resources. Viewing the access.log
and related logs can provide information on what may be causing problems related to Adobe Commerce on cloud infrastructure.
To view logs for these server errors, check the access.log
on the web server, e.g., <ip address>
<timestamp>
<request uri>
<response code>
<referer url>
To check related logs:
grep -r "\" [50[0-9]" /path/to/access.log
If the error has occurred in the past run the following command in the CLI (Pro architecture only): zgrep "\" 50[0-9]" /path/to/access.log.<rotation ID>.gz
exception.log
and error.log
or the equivalent rotated log (logs that are automatically rotated and compressed when they reach a certain file size) for the same timestamp to locate the potential error and see what might have been occurring to have caused it. Note: To check the exception.log
and error.log
run the above commands in the CLI but replace access.log
with exception.log
or error.log
.