After 2.2.6 upgrade reports generates enormous .tar file in tmp/analytics folder in root

[Jilco]

Preconditions

1. Magento 2.2.6
2. Ngingx
3. Redis

Steps to reproduce

1. Upgrade to 2.2.6
2. Switch on reports (or don't switch of if you already switched it on in earlier version)

Expected result

1. I don't realy know, i think the files are needed for advance reports

Actual result

1. In the /tmp/analytics folder in de root of the webserver an huge (1.7 Gb) .tar (~tmp-1537867209.3073tar.tar) file is generated every 24 hours (happend 2 times now after upgrade and exact the same time). Because it is in the tmp folder of the root/webserver Nginx cant make new sessions and the site goes down.

When i look in the .tar (i downloaded it) i see a lot of the same files and the same size. Maybe generating the file goes in a loop somewhere?

[magento-engcom-team]

Hi @Jilco. 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-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@Jilco do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[Jilco]

@magento-engcom-team give me 2.2.6 instance

[magento-engcom-team]

Hi @Jilco. Thank you for your request. I'm working on Magento 2.2.6 instance for you

[magento-engcom-team]

Hi @Jilco, here is your Magento instance.
Admin access: https://i-18243-2-2-6.engcom.dev.magento.com/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[Jilco]

Settings in the profided instance are the same as in my situation, but i can't see what happens when generation the report files

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

HI @Jilco seems like this bug is acknowledged -> #11543

[Jilco]

Thanks! But this is not related, system backup is switched off in my environment

…

________________________________ Van: engcom-backlog-nazar <notifications@github.com> Verzonden: woensdag 26 september 2018 09:20 Aan: magento/magento2 CC: Jilco; Mention Onderwerp: Re: [magento/magento2] After 2.2.6 upgrade reports generates enormous .tar file in tmp/analytics folder in root (#18243) HI @Jilco<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.202132.xyz%2FJilco&data=02%7C01%7C%7C90c08bdfa93a48907bad08d623809749%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636735432524690309&sdata=%2B0RhrjvU5sB%2F7PS5FUA9m10d4rrc%2BGkrJvwTu2U%2FneE%3D&reserved=0> seems like this bug is acknowledged -> #11543<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.202132.xyz%2Fmagento%2Fmagento2%2Fissues%2F11543&data=02%7C01%7C%7C90c08bdfa93a48907bad08d623809749%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636735432524690309&sdata=iLQGJYllfICXYriN%2FWjUqAY4T1b9DLXFQq6%2FAgxjyKw%3D&reserved=0> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.202132.xyz%2Fmagento%2Fmagento2%2Fissues%2F18243%23issuecomment-424611780&data=02%7C01%7C%7C90c08bdfa93a48907bad08d623809749%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636735432524690309&sdata=fNBTHIZlzChmC%2Fz%2B%2BOoGLzRk3HvKAiOwNIyh3zmAOk4%3D&reserved=0>, or mute the thread<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.202132.xyz%2Fnotifications%2Funsubscribe-auth%2FAWoMGpw46lMrnK1R6LnQPcPvNEniALuTks5ueyrTgaJpZM4W5L7t&data=02%7C01%7C%7C90c08bdfa93a48907bad08d623809749%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636735432524690309&sdata=lRUKky0oB4Pgb3xixn4XIioFNzxqKkvmpvBv1kxTeE8%3D&reserved=0>.

[snyderm]

This issue is 2.2.6 specific, and appears to be generated by magento advanced analytics. This issue did not occur in 2.3.

@Jilco As a temporary solution try disable advanced reporting.