Dispatcher failing when code is deployed via cloud manager

[annkitaaggarwal]

Hi All,

We have recently setup cloud manager for deployment process, but it is failing for below error.

 Failed to access /dispatcher/invalidate.cache on dispatcher with private ip 10.43.32.25, 404 Not found, make sure 'flush' host is enabled, check configurations in /etc/httpd/conf.dispatcher.d/enabled_farms. File (e.g. 001_ams_publish_flush_farm.any) should be present in enabled_farms directory.

I am not sure what to change and why it is failing.

Thanks

[arunpatidar]

Hi @annkitaaggarwal 
Can you please check if file 001_ams_publish_flush_farm.any  present in enabled_farms directory.

enable_farms must contains the symlink

e.g.

symlink from ../available_farms/001_ams_publish_flush_farm.any

[annkitaaggarwal]

I have file with name 000_publish_flush_farm.any . Does the name makes any difference.

[arunpatidar]

Yes, you have to make sure, you create symlink 000_publish_flush_farm.any enabled_farms directory from ../available_farms/000_publish_flush_farm.any

[Jagadeesh_Prakash]

@annkitaaggarwal 

Navigate to the /etc/httpd/conf.dispatcher.d/enabled_farms directory on your Apache server and verify that the appropriate configuration file for your content delivery instance exists. The file should have a name like 001_ams_publish_flush_farm.any.

Open the configuration file (e.g., 001_ams_publish_flush_farm.any) and check if the /dispatcher/invalidate.cache URL is configured correctly. Ensure that it points to the appropriate dispatcher instance and farm.

/dispatcher/invalidate.cache {
/hostname "publish-server"
/port "80"
/flush "true"
}

First of all did you try validating the dispatcher files in your local? If not follow below URL

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/local-development-env...

[annkitaaggarwal]

Config seems to be correct, i will try once in my local today

[kautuk_sahni]

@annkitaaggarwal Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

[annkitaaggarwal]

I am still looking out for answers

[Jörg_Hoh · Accepted solution]

in the course of the deployment, the dispatcher cache invalidation is also tried. It seems that you locked down the cache invalidation in a way, so it's not working in AEM CS.

the dispatcher cache invalidation is done via "localhost", that means your flush and vhost farm need to be working on that hostname. (You can check the latest archetype for a working definition.)

[annkitaaggarwal]

that seems to be the problem, i will check with latest archetype and see