Maximum execution time of 60 seconds exceeded & Allowed memory size of bytes exhausted

[sanjaykesari28]

Preconditions and environment

Hello Team, We are using magento version - 2.4.5-p1 and 2.10 version of smile elasticsuite. In new relic log, we are getting below error continuously. Please help to fix this issue

Error class: E_ERROR Transaction name: unknown Error message Maximum execution time of 60 seconds exceeded URL host: www.jaspal.com URL Path: /en/catalogsearch/result/index/ Stack Trace in GuzzleHttp\Ring\Client\CurlFactory::GuzzleHttp\Ring\Client{closure} called at ? (?) in curl_exec called at /app/fpkici6hpuyvi/vendor/ezimuel/ringphp/src/Client/CurlHandler.php (89) in GuzzleHttp\Ring\Client\CurlHandler::_invokeAsArray called at /app/fpkici6hpuyvi/vendor/ezimuel/ringphp/src/Client/CurlHandler.php (68) in GuzzleHttp\Ring\Client\CurlHandler::__invoke called at /app/fpkici6hpuyvi/vendor/ezimuel/ringphp/src/Client/Middleware.php (30) in GuzzleHttp\Ring\Client\Middleware::GuzzleHttp\Ring\Client{closure} called at /app/fpkici6hpuyvi/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php (265) in Elasticsearch\Connections\Connection::Elasticsearch\Connections{closure} called at /app/fpkici6hpuyvi/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php (241) in Elasticsearch\Connections\Connection::performRequest called at /app/fpkici6hpuyvi/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Transport.php (110) in Elasticsearch\Transport::performRequest called at /app/fpkici6hpuyvi/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Namespaces/AbstractNamespace.php (63) in Elasticsearch\Namespaces\AbstractNamespace::performRequest called at /app/fpkici6hpuyvi/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Namespaces/IndicesNamespace.php (79) in Elasticsearch\Namespaces\IndicesNamespace::analyze called at /app/fpkici6hpuyvi/vendor/smile/elasticsuite/src/module-elasticsuite-core/Client/Client.php (199) in Smile\ElasticsuiteCore\Client\Client::analyze called at /app/fpkici6hpuyvi/vendor/smile/elasticsuite/src/module-elasticsuite-thesaurus/Model/Index.php (229) in Smile\ElasticsuiteThesaurus\Model\Index::getSynonymRewrites called at /app/fpkici6hpuyvi/vendor/smile/elasticsuite/src/module-elasticsuite-thesaurus/Model/Index.php (135) in Smile\ElasticsuiteThesaurus\Model\Index::computeQueryRewrites called at /app/fpkici6hpuyvi/vendor/smile/elasticsuite/src/module-elasticsuite-thesaurus/Model/Index.php (110) in Smile\ElasticsuiteThesaurus\Model\Index::getQueryRewrites called at /app/fpkici6hpuyvi/vendor/smile/elasticsuite/src/module-elasticsuite-thesaurus/Plugin/QueryRewrite.php (131) in Smile\ElasticsuiteThesaurus\Plugin\QueryRewrite::getWeightedRewrites called at /app/fpkici6hpuyvi/vendor/smile/elasticsuite/src/module-elasticsuite-thesaurus/Plugin/QueryRewrite.php (88) in Smile\ElasticsuiteThesaurus\Plugin\QueryRewrite::aroundCreate called at /app/fpkici6hpuyvi/vendor/magento/framework/Interception/Interceptor.php (135) in Smile\ElasticsuiteCore\Search\Request\Query\Fulltext\QueryBuilder\Interceptor::Magento\Framework\Interception{closure} called at /app/fpkici6hpuyvi/vendor/magento/framework/Interception/Interceptor.php (153) in Smile\ElasticsuiteCore\Search\Request\Query\Fulltext\QueryBuilder\Interceptor::___callPlugins called at /app/fpkici6hpuyvi/generated/code/Smile/ElasticsuiteCore/Search/Request/Query/Fulltext/QueryBuilder/Interceptor.php (23) in Smile\ElasticsuiteCore\Search\Request\Query\Fulltext\QueryBuilder\Interceptor::create called at /app/fpkici6hpuyvi/vendor/smile/elasticsuite/src/module-elasticsuite-core/Search/Request/Query/Builder.php (119) in Smile\ElasticsuiteCore\Search\Request\Query\Builder::createFulltextQuery called at /app/fpkici6hpuyvi/vendor/smile/elasticsuite/src/module-elasticsuite-core/Search/Request/Query/Builder.php (84)

Steps to reproduce

We are getting this error into new relic report

Expected result

Please help to fix this issue

Actual result

Please help to fix this issue

Additional information

No response

Release note

No response

Triage and priority

• [X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [X] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @sanjaykesari28. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hi @sanjaykesari28 , Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop instance as per System requirements installed and the issue is not reproducible. Connection to new relic is successful and no errors observed in both new relic logs and Magento logs. Smile elasticsuite is a 3rd party intergration. Kindly check if the issue caused due to 3rd party modules and recheck the issue on Magento 2.4-develop instance as per Magento system requirements and provide missing steps if any if the issue is still reproducible. Thank you.

[sanjaykesari28]

Hello Support, Thanks for update. Kindly find the below screenshot, we could see more no.of errors getting triggered from 24th Dec 2022 for the transaction unknown and catalogsearch/result/index

[engcom-November]

Hi @sanjaykesari28 Thank you for the response. Verified the issue again on Magento 2.4-develop instance by performing additional operations ex: Reindexing, cache flush, graphql operations, placing order etc but above mentioned error is not reproducible in the logs. Kindly recheck the issue on Magento 2.4-develop instance and provide missing steps if any if the issue is still reproducible.

[sanjaykesari28]

Hello Support,

Thanks for update. As we are using cloud edition so we can not test this fresh magento setup. We have already shared our newrelic setup screenshot and in screenshot we can see this error is coming. May be this issue is occurring due to large catalog size. Please suggest if we can fix this error in our magento setup by increase php max execution time OR any other php/mysql global variable value. We really need to fix this ASAP. Quick reply would be appreciated. Thanks

[engcom-November]

Hi @sanjaykesari28 ,

Thank you for the response. For the error ""PHP Fatal error: "Maximum execution time of 60 seconds exceeded in…", you can update the maximum execution time by setting a custom max_execution_time value in your php.ini file and redeploying. Kindly refer the Magento devdocs - Common PHP Fatal Errors and solutions with example solutions that may help resolve your issue. For the error: "Fatal error: Allowed memory size of .. bytes exhausted..", try running the following commands or refer the devdocs for PHP settings.

php bin/magento setup:upgrade php bin/magento setup:static-content:deploy php bin/magento setup:di:compile php bin/magento cache:flush php bin/magento cache:clean

/To Run Command Forcefully / php -f bin/magento

/To run command with memory limit 4G/ php -d memory_limit=4G bin/magento

/To run command with max memory limit / php -d memory_limit=-1 bin/magento

Thank you.

[engcom-November]

Hi @sanjaykesari28 , We are closing this issue as there has been no latest update on the same. Kindly reopen / create new issue if you are still facing any issues. Thank you.