Error while doing code build deployment using pipeline in Cloud Manager | Community
Skip to main content
New Participant
August 13, 2020
Solved

Error while doing code build deployment using pipeline in Cloud Manager

  • August 13, 2020
  • 6 replies
  • 4739 views

Hi,

code build is getting failed while Build Image. can anyone please help to fix this issue 

 

below the error 

 

+ wget -O /tmp/dispatcher/dispatcher-configuration.zip 'https://cm0pl0va80stor0prd.file.core.windows.net/cdbd4994-837a-4d0e-8af4-d6b433b2e3c9/build/aem-guides-wknd.dispatcher.cloud-0.0.5-SNAPSHOT.zip?sig=T3MYHFUwpLO503qEoNAvyAbQOOThiSKJh0eHRoV5zO8%3D&se=2020-09-10T16%3A19%3A06Z&sv=2018-03-28&rsct=application%2Foctet-stream&rscd=attachment%3B%20filename%3Dbuild%2Faem-guides-wknd.dispatcher.cloud-0.0.5-SNAPSHOT.zip&sp=r&sr=f'
--2020-08-13 16:20:37-- https://cm0pl0va80stor0prd.file.core.windows.net/cdbd4994-837a-4d0e-8af4-d6b433b2e3c9/build/aem-guides-wknd.dispatcher.cloud-0.0.5-SNAPSHOT.zip?sig=T3MYHFUwpLO503qEoNAvyAbQOOThiSKJh0eHRoV5zO8%3D&se=2020-09-10T16%3A19%3A06Z&sv=2018-03-28&rsct=application%2Foctet-stream&rscd=attachment%3B%20filename%3Dbuild%2Faem-guides-wknd.dispatcher.cloud-0.0.5-SNAPSHOT.zip&sp=r&sr=f
Resolving cm0pl0va80stor0prd.file.core.windows.net (cm0pl0va80stor0prd.file.core.windows.net)... 52.239.153.8
Connecting to cm0pl0va80stor0prd.file.core.windows.net (cm0pl0va80stor0prd.file.core.windows.net)|52.239.153.8|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16149 (16K) [application/octet-stream]
Saving to: ‘/tmp/dispatcher/dispatcher-configuration.zip’

0K .......... ..... 100% 25.8M=0.001s

2020-08-13 16:20:37 (25.8 MB/s) - ‘/tmp/dispatcher/dispatcher-configuration.zip’ saved [16149/16149]

+ validate_configuration /tmp/dispatcher/dispatcher-configuration.zip
+ local zippedConfiguration=/tmp/dispatcher/dispatcher-configuration.zip
+ /usr/bin/dispatcher-configuration-validator full /tmp/dispatcher/dispatcher-configuration.zip
Cloud manager validator 2.0.21
2020/08/13 16:20:37 Apache configuration uses non-whitelisted directives:
conf.d/enabled_vhosts/wknd.vhost:1: ../available_vhosts/wknd.vhost
2020/08/13 16:20:37 Dispatcher configuration validation failed:
conf.dispatcher.d/enabled_farms/default.farm:1: extra characters following label "/default.farm" are ignored
The command '/bin/sh -c AZCOPY="/usr/bin/azcopy" VALIDATOR_BINARY="/usr/bin/dispatcher-configuration-validator" DISPATCHER_CONFIGURATION_LOCATION=$dispatcherConfigurationLocation DISPATCHER_CONFIGURATION_DESTINATION=$dispatcherConfigurationDestination RUN_MODE=$runmode ./validateDispatcherConfiguration.sh' returned a non-zero code: 2
2020/08/13 16:20:38 Container failed during run: build. No retries remaining.
failed to run step ID: build: exit status 2

Run ID: ca2fhf failed after 1m26s. Error: failed during run, err: exit status 1

 

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 jamesr11032597

Try focusing on what the error message says:

2020/08/13 16:20:37 Dispatcher configuration validation failed:
conf.dispatcher.d/enabled_farms/default.farm:1: extra characters following label "/default.farm" are ignored

This suggests you have an error on the first line in the above file, or potentially the file that references the above file.

6 replies

New Participant
July 15, 2022

Create symlinks for the available vhost in your Dispatcher/conf.d folder and it will build the correct image and deployed. 

 

To create a symlink from windows machine use gitbash as administrator and elevated system. 

New Participant
November 3, 2020

@sonuk85184451 we too faced with such an issue. For us it seems was related to broken symlinks.

/dispatcher/src/conf.d/enabled_vhosts/default.vhost is a symlink to /dispatcher/src/conf.d/available_vhosts/default.vhost
the same
/dispatcher/src/conf.dispatcher.d/enabled_farms/default.farm is a symlink to /dispatcher/src/conf.dispatcher.d/available_farms/default.farm

 

After working with the code in Windows we've found that symlinks became broken. Quick fix for us - copy content from origin available_vhosts/available_farms to enabled_vhosts/available_farms (so we have real content instead of reference to another files). Not sure if this is a good solution, but it helped. Btw, not clear how such a symlinks should work in Windows.

Nikhil-Kumar
New Participant
August 17, 2020

@sonuk85184451,

Got to this path conf.dispatcher.d/enabled_farms/default.farm and try to debug for solution at this location.

jamesr11032597Accepted solution
New Participant
August 13, 2020

Try focusing on what the error message says:

2020/08/13 16:20:37 Dispatcher configuration validation failed:
conf.dispatcher.d/enabled_farms/default.farm:1: extra characters following label "/default.farm" are ignored

This suggests you have an error on the first line in the above file, or potentially the file that references the above file.

New Participant
August 14, 2020
@jamesr11032597 - thanks but i have made any new changes , just using WKND Github project which get build successfully in local environment
joerghoh
Employee
August 13, 2020

That's unfortunate, and you should definitely raise a ticket with Support.

In parallel you could give it another try.

 

I constantly pray to pay attention to the details of the error message, and now I fooled myself 🙂

SundeepKatepally
New Participant
August 13, 2020

Never used pipeline in cloud manager.

But as per the error log. , what i understood is there is some issue in the apache configuration i.e. in the typical AMS dispatcher structure you need to inclide all the available vhosts as part of enabled vhosts.

 

New Participant
August 14, 2020
@sundeepkatepally - thanks but i have made any new changes , just using WKND Github project which get build successfully in local environment