Deploy script fails waiting on VMware Aria Automation Orchestrator 8.x services to start
book
Article ID: 326157
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
Symptoms:
/opt/scripts/deploy.sh times out while waiting on VMware Aria Automation Orchestrator (formerly VMware vRealize Orchestrator) 8.x services to start.
When inspecting vco-app-id pod status with command kubectl -n prelude get pods Automation Orchestrator services are reported unhealthy with 2 out of 3 containers deployed; running tail against the /data/vco/usr/lib/vco/app-server/logs/catalina.log file shows that the server hangs at the step below:
xx-xxx-20xx 16:03:24.980 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/usr/lib/vco/app-server/deploy/vco.war]
xx-xxx-20xx 16:03:28.497 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
The server will not start until all scripting logs in data/vco/usr/lib/vco/app-server/logs/ are not indexed. If there are too many logs or large scripting logs, the indexation can take too long (more than an hour) before the server is up and running.