Migration dispatcher issues 6.5 to cloud

Question

Migrating from 6.5 to cloud and ran Analyzer for dispatcher module and committed suggested changes  Used below command and added missing immutable files as welldocker_immutability_check.cmd srcAble to deploy dispatcher in local docker instance successfully, but when we try to deploy using adobe webtier dispatcher pipeline getting below error  Cloud manager validator 2.0.89
2025/09/24 04:01:01 The following warnings were found: 
  Did not find ServerAlias '*.adobeaemcloud.net' in any vhost file
  Did not find ServerAlias '*.adobeaemcloud.com' in any vhost file
  
2025/09/24 04:01:01 The following suggestions are proposed: 
  /tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/companybrand.vhost: file is not a symlink, all files inside "enabled_vhosts" and "enabled_farms" should be symlinks
  /tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/companybrand.farm: file is not a symlink, all files inside "enabled_vhosts" and "enabled_farms" should be symlinks
  
2025/09/24 04:01:01 The following errors were found in the httpd config: 
  /tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/companybrand.vhost: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_vhosts/custombrand.vhost
2025/09/24 04:01:01 Dispatcher configuration validation failed:
2025/09/24 04:01:01 /tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/companybrand.farm: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_farms/companybrand.farm
2025/09/24 04:01:01 Invalid symlinks found:
2025/09/24 04:01:01   /tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/companybrand.vhost: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_vhosts/companybrand.vhost
  /tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/companybrand.farm: appears to be a windows (pseudo) symlink but this OS does not support these. Please commit a correct symlink: ../available_farms/companybrand.farm
ERROR: '11 TEST_FAILURE dispatcher validator failed'
    at validate_configuration(/usr/local/bin/validate-static.sh:127)
    at runValidation(/usr/local/bin/validate-static.sh:189)
    at status.track(/usr/local/bin/lib-status.bash:261)
    at main(/usr/local/bin/validate-static.sh:192)
Reporting error to: '/mnt/shared/status-validation'
ERROR: '11 TEST_FAILURE ERROR: '11 TEST_FAILURE dispatcher validator failed'
    at validate_configuration(/usr/local/bin/validate-static.sh:127)
    at runValidation(/usr/local/bin/validate-static.sh:189)
    at status.track(/usr/local/bin/lib-status.bash:261)
    at main(/usr/local/bin/validate-static.sh:192)'
    at reportError(/usr/local/bin/lib-status.bash:127)
    at validate_configuration(/usr/local/bin/validate-static.sh:127)
    at runValidation(/usr/local/bin/validate-static.sh:189)
    at status.track(/usr/local/bin/lib-status.bash:261)
    at main(/usr/local/bin/validate-static.sh:192)
Status file exists: '/mnt/shared/status-validation' assuming it is already saved in earlier step.
ERROR: '11 SCRIPT_ERROR Script command failed (see stack trace)'
    at status.internal.handleError(/usr/local/bin/lib-status.bash:269)
    at status.track(/usr/local/bin/lib-status.bash:269)
    at main(/usr/local/bin/validate-static.sh:192)
Status file exists: '/mnt/shared/status-validation' assuming it is already saved in earlier step.
    at status.internal.handleExit(/usr/local/bin/lib-status.bash:56) exited with code '11'

giuseppebaglio · Accepted Answer

@vishnura5, it is failing validation due to invalid symlinks. Cloud Manager requires that all files in /conf.d/enabled_vhosts and /conf.dispatcher.d/enabled_farms must be actual UNIX symlinks (e.g., created via ln -s).
Windows “symlinks” (or copies with .symlink extension or “pseudo” symlinks) are not recognized by Linux-based validation in Adobe’s pipeline.

So, delete any Windows-created links and re-create actual UNIX symlinks (not copies) using Git Bash, Linux terminal, or a WSL shell.

Example:

# In your dispatcher config repo root
cd conf.d/enabled_vhosts
rm companybrand.vhost           # Remove the bogus/copy/pseudo symlink
ln -s ../available_vhosts/companybrand.vhost companybrand.vhost

cd ../../conf.dispatcher.d/enabled_farms
rm companybrand.farm
ln -s ../available_farms/companybrand.farm companybrand.farm

arunpatidar · Answer

Hi @vishnura5

Please check below fpr folder structure and how to create symlinks

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/validation-debug#flexible-mode-file-structure

Sign up

Login with SSO

Login to the community

Login with SSO