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

Smarts NCM: How to read and understand the installation logs (305135)

Last Updated: 5/29/2020Categories: How toTotal Views: 2376Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

To be able to read and understand installation logs

Installation logs in detail

The installation logs are generated once the installer exits cleanly. If you break out of an installer by killing the process or pressing ctrl-break, it will not generate any logs.

The <component>_install.log file contains a chronological list of events. If you encounter an install error, the best thing is to search this log for "ERROR". This is a good starting point. If you see errors concerning "Wine", ignore these as wine errors are not fatal. Typically, you will need more information then what is provided in the <component>_install.log log.

The <component>_debug.log file contains an alphabetic list of variables stored in memory while the installer is running. All output within the installer is stored in variables, like APPSERVER_PRE_OUT, which is the application server's module pre-install standard output. The standard error output is stored in APPSERVER_PRE_ERR, and the exit code is stored in APPSERVER_PRE_EXIT for example. It's important to keep in mind that the debug log is not in chronological order.

The best way to find errors in the debug log is to search for lines containing EXIT=(not zero), meaning that you are looking for the exit codes for the modules which are not zero (success). This is easy to do in Vi or Vim by searching for "EXIT=[^0]". It's also important to note the order that the modules get installed, since an earlier error can cause later errors. The first error is typically the one to go after. The order of the modules is:

COMMON, CORE, DASLLANG, DATABASE, APPSERVER, SYSADMIN

For each of those, you will have a _PRE (pre-install) and _POST (post-install) section. For each of those, you will have _OUT (stdout), _ERR (stderr), and _EXIT (exit code). The general flow for each module is:

Run pre-install script

Lay down files

Set file permissions

Run post-install script

Each module has its own perl script which handles the pre, post, preun, and postun operations. Those scripts are located in [Product Directory]/conf/setup. The script name corresponds to the module name (ex: AppServer.pl).

Once you determine the module that threw the error, you can look through the stdout and stderr portions to determine the failure point in the module perl script.
The upgrade logs are the same as the install logs.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant