Dispatcher deployment failed on AEM as a Cloud Service | Community
Skip to main content
P
parth3
Level 2
May 28, 2024
Solved

Dispatcher deployment failed on AEM as a Cloud Service

  • May 28, 2024
  • 5 replies
  • 1455 views

I am getting the following error when I try to deploy my AEM project on Cloud Manager. 

The following errors were found in the httpd config: conf.d/available_vhosts/default.vhost:12: included file (conf.d/variables/custom.vars) does not match any known file

I tried running the validator script on the dispatcher locally and I got a few warnings along with this error. I have checked the file names as well as path and everything seems right. Not sure how to fix this error 

 

 

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 gkalyan

@parth3 

I'm not fully sure that it will solve your problem but you can try some debugging steps from this documentation. 

https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/debugging/debugging-aem-as-a-cloud-service/build-and-deployment

5 replies

gkalyan
Community Advisor and Adobe Champion
gkalyanCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
May 28, 2024

@parth3 

I'm not fully sure that it will solve your problem but you can try some debugging steps from this documentation. 

https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/debugging/debugging-aem-as-a-cloud-service/build-and-deployment

    EstebanBustamante
    Community Advisor and Adobe Champion
    EstebanBustamanteCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    May 29, 2024

    Hi, 


    Do you have the file custom.vars? What is its content? Do you see any syntax issues in it?

     

    Esteban Bustamante
      Raja_Reddy
      Community Advisor
      Raja_ReddyCommunity Advisor
      Community Advisor
      May 29, 2024

      Hi @parth3 

      1. Check the file path: Double-check that the file path for custom. vars is correct and that the file exists in the specified location. If the file is not in the correct location, move it to the correct location and try deploying your project again.

      2. Check the file name: Make sure that the file name is spelled correctly and that it matches the name specified in the configuration file. If the file name is incorrect, update the configuration file to use the correct file name.

      3. Check the file permissions: Ensure that the file has the correct permissions set so that it can be read by the Apache HTTP Server. You can check the file permissions by running the command Is -1 in the directory where the file is located.

        joerghoh
        Adobe Employee
        joerghohAdobe Employee
        Adobe Employee
        May 30, 2024

        have you switched on flexible mode?

          kautuk_sahni
          Community Manager
          kautuk_sahniCommunity Manager
          Community Manager
          June 4, 2024

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

          Kautuk Sahni
          Terms & ConditionsAccessibility statement

          Loading footer...