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 Broker crashes after upgrade to 9.6 when running the trying to add a domain via the brcontrol add_dm command (75106)

Last Updated: 2/11/2020Categories: How toTotal Views: 5667Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Smarts Broker crashes after upgrade to 9.6 when running the trying to add a domain via the brcontrol add_dm command

Purpose

To provide steps on how resolve the issue.,

Cause

Possible causes:
1.   The SMHOME directory in the ic-serviced file did not get updated, or
2.   The serviced.db is corrupted during the upgrade process
3.    The brokerping password is not matched in both the serverConnect.conf and brokerConnect.conf across the domain installs.

Resolution

First steps is to find and review the ic-serviced file

cd /etc/init.d/
Open the ic-serviced file
Find the SMHOME line

This needs to point to your current 9.6 SAM smarts folder, ie:

SMHOME=/opt/SAM/SAM96/SAM/smarts

If this does not match you will need to do the following.

./ic-serviced stop
Edit the ic-serviced file
Update the SMHOME line to match the path to your 9.6 SAM/smarts folder.
Save the file, then start the ic-serviced service
./ic-serviced start

If this does not resolve or the SMHOME path is correct then the issue is caused by serviced.db corruption.

If this is the case,

From the <basedir>SAM/smarts/bin

Run the sm_service show --cmdline and copy all the all of the output from this command to a text file

Because you will need to reinstall the services again if the SMHOME folder is set to the 9.6 Smarts SAM installation folder as shown below, and you need to rename the serviced.db

Shut down all smarts services that are running as a precaution to avoid any issues.

./ic-serviced stop
navigate to your  /var/smarts directory,
rename the sm_serviced.db
cd /etc/init.d/
./ic-serviced start

Reinstall the services that you copied into the text file.

This should resolve the issue with the broker and the add_dm command.

If there are not any issues found with regard to the steps above:

Please check the brokerping password in the serverConnect.conf and brokerConnect.conf files in all installations with regard to the broker and the domain(s) involved in which the broker is crashing using the add_dm command,
Use sm_edit to properly change and encrypt the password to match the broker install.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
由于证书的 v3 关键扩展部分出现错误，将 vRealize Automation 默认 SSL 证书替换为 Microsoft CA 签名证书失败 (76089)

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

KB
•
任意のノードで Docker サービスを再起動すると、サービスの状態が健全でなく、デプロイが失敗する (75183)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant