Upgrade V13.5.0 to V14.2.3, planned to execute Configuration verifier, but got below error and can’t proceed further. [INFO] [talledLocalContainer] Deploying [/site/target/site.war] to context /site … [WARNING] [talledLocalContainer] org.codehaus.cargo.container.ContainerException: Failed to deplo…

Hi All, Is this resolved? I am experiencing the same issue when starting the tomcat container with mvn -P cargo.run,verify-configuration [WARNING] [talledLocalContainer] ERROR: transport error 202: bind failed: Address already in use [WARNING] [talledLocalContainer] ERROR: JDWP Transport dt_socke…

Okay, I have resolved it locally, I was running the cargo profile with port 9080 so as to be able to run two bloomreach instances, after changing the port to 8080 it worked.

Configuration Verifier error for V14 upgrade

Experience Manager (PaaS/OnPrem)

jasper.floor April 4, 2023, 1:49pm 4

This sounds like

https://issues.onehippo.com/browse/CMS-14528

Though that should be fixed for 13.4.11, 14.7.0.

Topic		Replies	Views
Configuration verifier is not working Experience Manager (PaaS/OnPrem)	1	182	April 1, 2024
Not able to change default port Experience Manager (PaaS/OnPrem)	4	2295	September 26, 2019
Unable to run project https://documentation.bloomreach.com/14/trails/getting-started/running-a-project.html Experience Manager (PaaS/OnPrem)	6	825	October 8, 2021
Two bloomreach local Experience Manager (PaaS/OnPrem)	11	517	April 14, 2023
Error after upgrading 14.7.13 Experience Manager (PaaS/OnPrem)	6	538	March 9, 2023

Configuration Verifier error for V14 upgrade

Related topics