Dispatcher failing when code is deployed via cloud manager | Community
Skip to main content
A
annkitaaggarwal
Level 3
November 29, 2023
Solved

Dispatcher failing when code is deployed via cloud manager

  • November 29, 2023
  • 4 replies
  • 1663 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

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.)

4 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
November 29, 2023

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

Arun Patidar
    A
    annkitaaggarwalAuthor
    Level 3
    December 4, 2023

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

      arunpatidar
      Community Advisor
      arunpatidarCommunity Advisor
      Community Advisor
      December 4, 2023

      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

      Arun Patidar
        Jagadeesh_Prakash
        Community Advisor
        Jagadeesh_PrakashCommunity Advisor
        Community Advisor
        November 29, 2023

        @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-environment-set-up/dispatcher-tools.html?lang=en

         

          A
          annkitaaggarwalAuthor
          Level 3
          December 4, 2023

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

            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            December 4, 2023

            @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.

            Kautuk Sahni
            A
            annkitaaggarwalAuthor
            Level 3
            December 4, 2023

            I am still looking out for answers

              joerghoh
              Adobe Employee
              joerghohAdobe EmployeeAccepted solution
              Adobe Employee
              December 5, 2023

              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.)

                A
                annkitaaggarwalAuthor
                Level 3
                December 5, 2023

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

                  Terms & ConditionsAccessibility statement

                  Loading footer...