TMP folder is full

[aliaksandr_hvoz]

Hello

I encountered a problem in that the temporary folder tmp is filled with temporary files but is not cleared automatically. The folder size is 20 gigabytes and these files fill all the space, this prevents the publication of content on publish nodes.

Files have names like this:

/tmp/fleioutilscopy1750063702511928162.tmp

What could be the reason?

Thank you in advance.

[VikasChaudhary_]

Hi @aliaksandr_hvoz ,

This usually happens when your application is creating these temp files, but you have not taken care of removing these files yourself. AEM takes care of the OOTB functionality and clears off the tmp files thus created. But if you are creating these files in your implementation, then you have to clear the same by yourself. It could be generation of custom email template, creating a JSON file for posting it to 3rd party APIs. Can you check if any such code exists in your implementation?

-Vikas Chaudhary

[aliaksandr_hvoz]

These files were deleted automatically, but after January 1st this no longer happens.

[arunpatidar]

Hi @aliaksandr_hvoz 
Could you please check https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/could-not-build-package-qu... 

[kautuk_sahni]

@aliaksandr_hvoz were you able to sort this up? 

[PrasannaMo]

Hi @kautuk_sahni @arunpatidar 

Thanks for your continued support on AEL community...

I also facing same issue, and in my case it is the Daily Maintainance Job that is causing this issue. I have 2 tasks in my Daily Maintenance job created long back, as below,

1. Revision Cleanup.

2. LuceneBinaries Cleanup.

The first task results in successful completion, but the second task takes(LuceneBinaries Cleanup) too long to complete, almost an hour.

While it is executing, I observe exactly 6 temporary files getting generated in /tmp folder each of 18gb. My /tmp folder size is 100gb, seems like the job needs more than 100gb space to complete. Because it does not get, the job results into failure without given /tmp files getting cleaned-up.

Could you please suggest what could be the issue?

I just speculate/suspect, if there is any kind of files/nodes under /var/audit e.g. /var/audit/com.day.cq.wcm.core.page OR /var/audit/com.day.cq.dam OR /var/audit/com.day.cq.replication needs to be cleaned/purged through nay OOTP AEM utility? 

KR,

Prasanna

[arunpatidar]

Hi @PrasannaMo 

It could be that the indexing is calculated again on whole repository and store in the tmp folder because the cleanup process identifies and removes unused or obsolete binaries from the repository.

It involves the following steps:

• Marking Phase: During this phase, the system scans the repository to mark all the binaries that are still in use. This is done by traversing the index data and identifying the binaries referenced by the current index.
• Sweep Phase: In this phase, the system removes all binaries that were not marked as in use. This ensures that only the obsolete binaries are deleted, freeing up storage space without affecting the current index data.

I would suggest to check with Adobe by opening a case with them.

[PrasannaMo]

Hi @arunpatidar 

Thanks for your response. I see the LuceneBinaries Cleanup task in the daily maintenance succeeds. But we have 2 issues

1. It consumes /tmp folder to store the .tmp files and occupies almost 100% space.

2. It completes successfully after running for few hours, but the .tmp files doesn't get deleted automatically.

I have raised an Adobe support ticket though.

KR,

Prasanna