500 Internal Server Error after MAMP upgrade from 5.5 to 6
Posted: Wed Jan 20, 2021 4:09 am
Since upgrading from MAMP 5.5 to 6.0.1 I am having intermittent "Internal Server Error" responses with a 500 return code.
These seem to be when the server has a lot of work to do so after clearing the cache for example or clearing the compiled content, when I refresh the same page then it completes without error. I have checked the apache, PHP and MySQL logs and there are no errors corresponding with the times the issues occur.
I have my php.ini set to use "unlimited" memory (memory_limit = -1) so that is not the limitation, but it feels like I am hitting some other limitation which is causing an issue without throwing an error, has anybody else come across this or know of a way to increase the logging in MAMP so I can debug this issue, because at the moment I am stumped.
For reference I am running on Mac Catalina 10.15.7 and the site I am running is a Magento 2.3 build running on PHP 7.2.33 with Apache.
Loom video showing the issue, 500 on first attempt, page loads successfully on second attempt, the same can pretty much be repeated on all pages across the site after a cache clean.
These seem to be when the server has a lot of work to do so after clearing the cache for example or clearing the compiled content, when I refresh the same page then it completes without error. I have checked the apache, PHP and MySQL logs and there are no errors corresponding with the times the issues occur.
I have my php.ini set to use "unlimited" memory (memory_limit = -1) so that is not the limitation, but it feels like I am hitting some other limitation which is causing an issue without throwing an error, has anybody else come across this or know of a way to increase the logging in MAMP so I can debug this issue, because at the moment I am stumped.
For reference I am running on Mac Catalina 10.15.7 and the site I am running is a Magento 2.3 build running on PHP 7.2.33 with Apache.
Loom video showing the issue, 500 on first attempt, page loads successfully on second attempt, the same can pretty much be repeated on all pages across the site after a cache clean.