Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

AEM dispatcher 6.5 farm files became empty

Avatar

Community Advisor

Hi,

 

We faced an issue in AEM 6.5 (AMS), where entire content in dispatcher farm files was blank automatically and farm files were empty. we had to restore them with help from Adobe team
Anyone has info on why this happens and what would be the root cause for this


Amanath Ullah
1 Accepted Solution

Avatar

Correct answer by
Community Advisor and Adobe Champion

If this is AMS and you are sure that your code didn't introduce the blank file and you verified there wasn't any deployment around the dates where the issues arise, you can open a support ticket so AMS can help you to check on their end if something happened. 



Esteban Bustamante

View solution in original post

4 Replies

Avatar

Employee

It can't be automatically. someone did it mistakenly. someone might be using shell window to edit the farm file and by mistake deleted everything.

OR

your cloud manager deployment code is having blank farm file that is getting replaced while deploying the code.

 

Avatar

Community Advisor

I would suggest to check the repo logs to see if the farm files under available folder were modified or removed.

Alternatively, check for any script that might be running on the dispatcher module. We have a NodeJS script which generated vhost and farm files dynamically and has the necessary rm permissions.

As @Nishant-Singh suggested this does not happen automatically so you might want to audit your deployment process once

Avatar

Correct answer by
Community Advisor and Adobe Champion

If this is AMS and you are sure that your code didn't introduce the blank file and you verified there wasn't any deployment around the dates where the issues arise, you can open a support ticket so AMS can help you to check on their end if something happened. 



Esteban Bustamante

Avatar

Community Advisor

This was an issue from Adobe end 
Thanks all


Amanath Ullah