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

VoyenceControl: Failed to install VoyenceControl Core Setup (359749)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 1685Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Failed to install VoyenceControl Core Setup.

ERROR in server.postmaster:

2009-04-02 10:31:19.565 PST - SessionId: - TransId: - LOG:  could not translate host name "localhost", service "5435" to address: Temporary failure in name resolution
2009-04-02 10:31:19.565 PST - SessionId: - TransId: - WARNING:  could not create listen socket for "localhost"
2009-04-02 10:31:19.565 PST - SessionId: - TransId: - FATAL:  could not create any TCP/IP sockets

ERROR in core_debug.log for APPSERVER POST operation:

APPSERVER_POST_ERR=psql: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5435?
psql: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5435?

APPSERVER_POST_EXIT=2

ERROR in core_debu.log for DATABASE POST operation:

DATABASE_POST_ERR=/opt/voyence/db/controldb/.bash_profile: line 14: /etc/controldb.conf: No such file or directory

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the -A option the
next time you run initdb.
error reading information on service controldb: No such file or directory
rm: cannot remove `/etc/init.d/controldb': No such file or directory
dropdb: could not connect to database postgres: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5435?
WARN: Unable to drop database voyencedb
dropuser: could not connect to database postgres: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5435?
WARN: Unable to drop database user voyence
createuser: could not connect to database postgres: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5435?
ERROR: Unable to create database user voyence
ERROR: Unable to install the database schema

DATABASE_POST_EXIT=1

controldb service fails to start:

Starting controldb service: could not start server
[FAILED]

Cause

/etc/hosts is missing the localhost entry.

Resolution

To resolve this issue, you will need to add the localhost entry to the /etc/hosts file, and then uninstall/reinstall VoyenceControl:

Open the /etc/hosts file for editing:

Ensure that the file has an entry for localhost:

127.0.0.1        localhost.localdomain        localhost

Save your changes and exit.

Uninstall VoyenceControl.

Reinstall VoyenceControl.

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