Unable to synchronize all media files because sync process run only of 5 minutes.

[dverkade]

Preconditions

1. Magento 2.3.5-p2
2. Have around 30.000 images and 75 GB of images data stored in Magento
3. Ticket Unable to synchronize all media files because sync process run only of 5 minutes. #29138 is related but was closed.

Steps to reproduce

1. Login into Magento admin
2. Go to Stores > Settings > Configuration
3. Expand 'Advanced' section and choose 'system'
4. Select 'Storage Configuration for Media' and choose 'Database' from the "Media Storage' dropdown
5. Click the synchronise button

Expected result

1. Media synchronises to the database

Actual result

1. Timeout occurs after 5 minutes.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

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

[m2-assistant]

Hi @dverkade. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[dverkade]

Issues should not be closed automatically. Posting comment to keep it active.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[dverkade]

Issues should not automatically close. Posting this comment to keep it active.

[m2-assistant]

Hi @engcom-Bravo. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[magento-engcom-team]

@engcom-Bravo Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

@m2-community-project[bot] Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

@m2-community-project[bot] Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-42618 were created

Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[xtremevision]

It is happening also on v 2.4.6 with 1.55Gb of images uploading to R2 CloudFlare. I simply press the button to synchronize, watch the log file and see files uploading, everything is running fine - but at some point the exception log throw an error and the ajax sync status disappears. The error is:

[2023-06-26T00:02:17.567277+00:00] main.CRITICAL: Magento\Framework\Exception\LocalizedException: The timeout limit for response from synchronize process was reached. in htdocs/vendor/magento/module-media-storage/Controller/Adminhtml/System/Config/System/Storage/Status.php:86
Stack trace:
#0 htdocs/vendor/magento/framework/Interception/Interceptor.php(58): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status->execute()
#1 htdocs/vendor/magento/framework/Interception/Interceptor.php(138): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status\Interceptor->___callParent()
#2 htdocs/vendor/magento/framework/Interception/Interceptor.php(153): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status\Interceptor->Magento\Framework\Interception\{closure}()
#3 htdocs/generated/code/Magento/MediaStorage/Controller/Adminhtml/System/Config/System/Storage/Status/Interceptor.php(23): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status\Interceptor->___callPlugins()
#4 htdocs/vendor/magento/framework/App/Action/Action.php(111): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status\Interceptor->execute()
#5 htdocs/vendor/magento/module-backend/App/AbstractAction.php(151): Magento\Framework\App\Action\Action->dispatch()
#6 htdocs/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Backend\App\AbstractAction->dispatch()
#7 htdocs/vendor/magento/framework/Interception/Interceptor.php(138): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status\Interceptor->___callParent()
#8 htdocs/vendor/magento/module-backend/App/Action/Plugin/Authentication.php(145): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status\Interceptor->Magento\Framework\Interception\{closure}()
#9 htdocs/vendor/magento/framework/Interception/Interceptor.php(135): Magento\Backend\App\Action\Plugin\Authentication->aroundDispatch()
#10 htdocs/vendor/magento/framework/Interception/Interceptor.php(153): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status\Interceptor->Magento\Framework\Interception\{closure}()
#11 htdocs/generated/code/Magento/MediaStorage/Controller/Adminhtml/System/Config/System/Storage/Status/Interceptor.php(32): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status\Interceptor->___callPlugins()
#12 htdocs/vendor/magento/framework/App/FrontController.php(245): Magento\MediaStorage\Controller\Adminhtml\System\Config\System\Storage\Status\Interceptor->dispatch()
#13 htdocs/vendor/magento/framework/App/FrontController.php(212): Magento\Framework\App\FrontController->getActionResponse()
#14 htdocs/vendor/magento/framework/App/FrontController.php(147): Magento\Framework\App\FrontController->processRequest()
#15 htdocs/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Framework\App\FrontController->dispatch()
#16 htdocs/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\App\FrontController\Interceptor->___callParent()
#17 htdocs/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}()
#18 htdocs/generated/code/Magento/Framework/App/FrontController/Interceptor.php(23): Magento\Framework\App\FrontController\Interceptor->___callPlugins()
#19 htdocs/vendor/magento/framework/App/Http.php(116): Magento\Framework\App\FrontController\Interceptor->dispatch()
#20 htdocs/vendor/magento/framework/App/Bootstrap.php(264): Magento\Framework\App\Http->launch()
#21 htdocs/pub/index.php(30): Magento\Framework\App\Bootstrap->run()
#22 {main} {"exception":"[object] (Magento\\Framework\\Exception\\LocalizedException(code: 0): The timeout limit for response from synchronize process was reached. at htdocs/vendor/magento/module-media-storage/Controller/Adminhtml/System/Config/System/Storage/Status.php:86)"} []

Using php 8.1 and Magento 2.4.6 CE.

[engcom-Bravo]

Hi @dverkade,

Thanks for your reporting and collaboration.

As per the Magento devdocs https://experienceleague.adobe.com/en/docs/commerce-admin/config/advanced/system#storage-configuration-for-media The database media storage method has been deprecated as of Adobe Commerce and Magento Open Source

Hence we are closing this issue.

Thanks.