Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Aria Automation Orchestrator 8.x services to fail to start or the Monitoring client logs are not visible in the GUI (54485)

Last Updated: 10/31/2023Categories: TroubleshootingTotal Views: 23331Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

VMware Aria Automation Orchestrator 8.x (formerly vRealize Orchestrator) and Monitoring client logs are not visible in the GUI.

This is likely to occur on upgrades.

For 7.x versions, the /var/log/vmware/vco/app-server/server.log,you see entries similar to:

[ForkJoinPool-47-worker-1] WARN  {} [StubbornRetrier] Retry 6/6 failed because of: Could not load codec 'Lucene60'.  Did you forget to add lucene-backward-codecs.jar?
[http-nio-127.0.0.1-8280-exec-2] WARN  {} [FileLoggingServiceImpl] Unable to retrieve previous logs:
java.lang.RuntimeException: Cannot succeed after 6 retries.

In some scenarios, VMware Aria Automation Orchestrator 8.x services fail to start.

/opt/scripts/deploy.sh times out while waiting on 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.

Cause

This issue occurs when Log files are indexed with the previous version's Lucene codec. When upgraded, the index is not automatically re-coded with the new Lucene codec.

Resolution

Currently, there is no resolution for this issue. See the Workaround below for further details.

Workaround

VMware Aria Automation Orchestrator 8.x (formerly vRealize Orchestrator)

To temporarily workaround the issue, delete the log indices and restart the Automation Orchestrator service by deleting the pod by its ID.

Prerequisites

You have enough available diskspace to perform file deletion.

Procedure

On each virtual appliance(s) within the cluster run

rm -rf /data/vco/usr/lib/vco/app-server/logs/scripting.log*_lucene*

Note: The file can be in format of scripting.log.Number_lucene. A wildcard asterisk ( * ) may be needed if there are multiple lucene files.

Isolate the pod ID(s) for the Automation Orchestrator service(s)

kubectl get pods -n prelude

Note: The service is in the format of: vco-app-randomID-randomID
Example:

Delete the pod. This can be done from one appliance, but must be performed for each pod if in a 3-node cluster:

kubectl delete pods -n prelude pod_id1
kubectl delete pods -n prelude pod_id2
kubectl delete pods -n prelude pod_id3

VMware vRealize Orchestrator 7.x

To delete the old Lucene index, run the following commands in a SSH session terminal.

Stop vRO 7.x server service:

service vco-server stop

Use the find command to isolate the affected logs:

find /var/log/vco/app-server -iname "*lucene*"

Delete the old indices:

rm -rf /var/log/vco/app-server/scripting.log*_lucene*

Note:  The file can be in format of scripting.log.Number_lucene. A wildcard asterisk ( * ) may be needed if there are multiple lucene files.

Start the vRO 7.x server service:

service vco-server start

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation Orchestrator

Related Versions:

VMware vRealize Orchestrator 8.x

VMware Aria Automation Orchestrator 8.x

Take Our Survey

Support Assistant