Dispatcher deployment failed for WKND project | Community
Skip to main content
N
nbg62
Level 4
October 19, 2022
Solved

Dispatcher deployment failed for WKND project

  • October 19, 2022
  • 2 replies
  • 1425 views

I'm deploying latest weekend project to cloud, deployment fails for dispatcher with :

 

 

2022/10/19 14:49:36 The following errors were found in the httpd config:
/tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/wknd.vhost: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_vhosts/wknd.vhost
2022/10/19 14:49:36 Dispatcher configuration validation failed:
/tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/wknd.farm: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_farms/wknd.farm
2022/10/19 14:49:36 Dispatcher configuration validation failed:
/tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/wknd.vhost: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_vhosts/wknd.vhost
/tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/wknd.farm: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_farms/wknd.farm
The command '/bin/sh -c AZCOPY="/usr/bin/azcopy" VALIDATOR_BINARY="/usr/bin/dispatcher-configuration-validator" HTTPD_BINARY="/usr/sbin/httpd" DISPATCHER_CONFIGURATION_LOCATION=$dispatcherConfigurationLocation DISPATCHER_CONFIGURATION_DESTINATION=$dispatcherConfigurationDestination DISPATCHER_IMAGE=$dispatcherImage RUN_MODE=$runmode ./validateDispatcherConfiguration.sh' returned a non-zero code: 2
2022/10/19 14:49:36 Container failed during run: validate-dispatcher. No retries remaining.
failed to run step ID: validate-dispatcher: exit status 2

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 aanchal-sikka

Hello @nbg62 

 

The AEMaaCS dispatcher follows structure similar to aem-project-archetype/src/main/archetype/dispatcher.cloud at develop · adobe/aem-project-archetype (github.com)

  • each enabled_vhost is symlink to available_vhost
  • each enabled_farms is symlink to available_farms

 

Please check following:

- Are the files created under enabled_vhost & enabled_farms  symlinks?

- If not, either you can create symlinks or add  opt-in/USE_SOURCES_DIRECTLY to use Flexible mode of dispatcher

 

Details about flexible and legacy mode are available on : https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/disp-overview.html?lang=en#validation-debug

2 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
October 19, 2022

If you are deploying the local version of dispatcher it will not work because of missing symlink

2022/10/19 14:49:36 The following errors were found in the httpd config:
/tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/wknd.vhost: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_vhosts/wknd.vhost
2022/10/19 14:49:36 Dispatcher configuration validation failed:
/tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/wknd.farm: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_farms/wknd.farm
2022/10/19 14:49:36 Dispatcher configuration validation failed:
/tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/wknd.vhost: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_vhosts/wknd.vhost
/tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/wknd.farm: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_farms/wknd.farm

 

Please check

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/dispatcher-symlinks-configurations/td-p/463308 

https://www.albinsblog.com/2020/12/aem-dispatcher-configurations-symlinks.html#.Y1AuJuxBz0o 

 

 

 

Arun Patidar
    N
    nbg62Author
    Level 4
    October 20, 2022

    Thank you Arun,

     

    Not sure what you mean by local dispatcher, I pull wknd code from git and push it to Cloud instance for deployment.

      aanchal-sikka
      Community Advisor
      aanchal-sikkaCommunity AdvisorAccepted solution
      Community Advisor
      September 5, 2023

      Hello @nbg62 

       

      The AEMaaCS dispatcher follows structure similar to aem-project-archetype/src/main/archetype/dispatcher.cloud at develop · adobe/aem-project-archetype (github.com)

      • each enabled_vhost is symlink to available_vhost
      • each enabled_farms is symlink to available_farms

       

      Please check following:

      - Are the files created under enabled_vhost & enabled_farms  symlinks?

      - If not, either you can create symlinks or add  opt-in/USE_SOURCES_DIRECTLY to use Flexible mode of dispatcher

       

      Details about flexible and legacy mode are available on : https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/content-delivery/disp-overview.html?lang=en#validation-debug

      Aanchal Sikka
        Terms & ConditionsAccessibility statement

        Loading footer...