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

Graceful Shutdown and Power On of a VMware Identity Manager PostgreSQL cluster (78815)

Last Updated: 1/4/2024Categories: Best PracticesTotal Views: 14697Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Purpose

How to Shut down, Power On or Reboot a VMware Identity Manager deployed through VMware Aria Suite Lifecycle (formerly vRealize Suite LifeCycle Manager).

Note: This article is applicable for VMware Identity Manager deployed through Aria Suite Lifecycle.
for product version Aria Suite Lifecycle 8.x & VMware Identity Manager 3.x.

Resolution

When using Aria Suite Lifecycle 8.1 or later, please utilize the product UI. View this resource for details: Day 2 Operations for Global Environment in vRealize Suite Lifecycle Manager.

Workaround

For versions earlier than 8.1, please take the following steps:

Steps for a Single node VMware Identity Manager

Graceful shut down of all services in VMware Identity Manager

Graceful power on of all services in VMware Identity Manager

Steps for Clustered VMware Identity Manager

Graceful shut down of all services in VMware Identity Manager

Graceful power on of all services in VMware Identity Manager

Single node VMware Identity Manager

Graceful Shut down of all services in VMware Identity Manager:

Navigate to the top-right corner of the VMware Identity Manager admin console.

Ensure that the appliance health status of the VMware Identity Manager is Green.

URL: https://<VMware Identity Manager Hostname>/SAAS/admin/app/page#!/systemDiagnostic
Note: Where <VMware Identity Manager Hostname> is the Complete FQDN of the VMware Identity Manager appliance.

SSH to VMware Identity Manager node as root

Run the command to stop the Horizon and Elastic search services:

service horizon-workspace stop

vIDM versions 3.x - 3.3.6
service elasticsearch stop

vIDM versions 3.3.7 and above
/etc/init.d/opensearch stop

Note: After each command to verify the status of the service, use the command:                                  service <service-name> status

Power off the VMware Identity Manager node, if required.

Graceful power on of all services in VMware Identity Manager

If the VMware Identity Manager node(s) are powered off, then power on all the node(s) in the vCenter.

After the VMware Identity Manager node is powered on, the services starts up automatically. However, if step #1 was not performed, to gracefully bring up the VMware Identity Manager services follow the below steps.

SSH to VMware Identity Manager node as Root

Run the command to start the Horizon and Elasticsearch services:

vIDM versions 3.x - 3.3.6

service horizon-workspace start
service elasticsearch start

Note: Use service <service-name> status to check the status of the service.

vIDM versions 3.3.7 and above

service horizon-workspace start
/etc/init.d/opensearch start
/etc/init.d/opensearch status

Clustered VMware Identity Manager

Graceful Shut down of all services in VMware Identity Manager:

Navigate to top right corner of the VMware Identity Manager admin console.

Ensure appliance health status of the VMware Identity Manager is Green.

URL:

https://VMwareIdentityManagerHostname/SAAS/admin/app/page#!/systemDiagnostic

Note: where VMwareIdentityManagerHostname is the FQDN of the VMware Identity Manager appliance.

To get the current cluster health status, run the following API:

API:

curl -H "Authorization: Basic token" -k https://AriaSuiteLifecyclehostname/lcm/authzn/api/vidmcluserhealth

API Help:
AriaSuiteLifecyclehostname: The hostname / IP of Aria Suite Lifecycle appliance managing the vIDM cluster.
token: Run the following command to get the Base64 encoded value of username:password. Here the username is admin@local, and password is admin@local user's password.

echo -n 'admin@local:password' | base64

Note: On VCF mode replace admin@local with vcfadmin@local and its respective password.
Note: The API will trigger a request to re-calculate the cluster health which post completion would again generate a notification on the current overall status in Aria Suite Lifecycle. Ensure the health notification for the postgres cluster in Aria Suite Lifecycle is green. if not, please see Troubleshooting VMware Identity Manager postgres cluster deployed through vRealize Suite Lifecycle Manager to remediate cluster health, which is necessary to ensure the postgres is restored to healthy state after gracefully bringing it back.

To find the pgpool master, run the below command on any of the VMware Identity Manager nodes:

su - root -c "echo -e 'password'|/usr/local/bin/pcp_watchdog_info -p 9898 -h localhost -U pgpool"

Command parameters:
-h : The host against which the command would be run, here its 'localhost'.
-p : Port on which pgpool accepts connections, which is 9898
-U : The Pgpool health check and replication delay check user, which is pgpool

Expected result:
3 YES <Host1>:9999 Linux <Host1> <Host1>
<Host1>:9999 Linux <Host1> <Host1> 9999 9000 4 MASTER
<Host2>:9999 Linux <Host2> <Host2> 9999 9000 7 STANDBY
<Host3>:9999 Linux <Host3> <Host3> 9999 9000 7 STANDBY

Note: In the above expected result, the node marked as MASTER, is the pgpool master and other nodes would be pgpool standby nodes.If pgpool master node cannot be found, see Troubleshooting VMware Identity Manager postgres cluster deployed through vRealize Suite Lifecycle Manager to remediate VMware Identity Manager cluster.

On the pgpool master found in step #4.To find out the postgres primary node, run the command:

su - postgres -c "echo -e 'password'|psql -h localhost -p 9999 -U pgpool postgres -c \"show pool_nodes\""

Command parameters :
-h : The host against which the command would be run, here it would be 'localhost' .
-p : The port on which Pgpool accepts connections, here its 9999
-U : The Pgpool user, which is pgpool
-c : The command to run, which is 'show pool_nodes'

Expected result:

node_id | hostname | port | status | lb_weight | role | select_cnt | load_balance_node | replication_delay | last_status_change

---------+---------------+------+--------+-----------+---------+------------+-------------------+-------------------+---------------------
0       | Host1    | 5432 | up     | 0.333333 | primary | 0 | false | 0 | 2019-10-14 06:05:42
1       | Host2    | 5432 | up     | 0.333333 | standby | 0 | false | 0 | 2019-10-14 06:05:42
2       | Host3    | 5432 | up     | 0.333333 | standby | 0 | true | 0 | 2019-10-14 06:05:42
(3 rows)

Note: In the above response, the node marked as primary in the 'role' column would be the primary postgres and other nodes would be standby postgres nodes. On an ideal scenario, there must be atleast one postgres primary node.If none of the nodes are marked primary in 'role' column, see Troubleshooting VMware Identity Manager postgres cluster deployed through vRealize Suite Lifecycle Manager to remediate VMware Identity Manager cluster and repeat this step to find the postgres primary node.

Ensure that the master and the delegateIP are added to the /etc/hosts file
The entries need to be outside of the VAMI_BEGIN and VAMI_END block
This needs to be done for all the hosts on the cluster.

To bring down the Postgres cluster gracefully:

Stop Horizon Service on the two standby postgres nodes using the command:

service horizon-workspace stop

Stop Horizon Service on the primary postgres node using the command:

service horizon-workspace stop

Stop Elasticsearch Service on the two standby postgres nodes using the command:

vIDM versions 3.x - 3.3.6
service elasticsearch stop

vIDM versions 3.3.7 and above
/etc/init.d/opensearch stop

Stop Elasticsearch Service on the primary postgres node using the command:

vIDM versions 3.x - 3.3.6
service elasticsearch stop

vIDM versions 3.3.7 and above
/etc/init.d/opensearch stop

Stop Pgpool Service on the two postgres standby nodes using the command:

service pgService stop

Stop Pgpool Service on the postgres master node using the command:

service pgService stop

Stop vPostgres on the two standby postgres nodes using the command:

service vpostgres stop

Stop vPostgres on primary postgres node using the command:

service vpostgres stop

Note : After each command verify the service is stopped, run the below command:

service <service-name> status

Once all the services is stopped in step #6, all the VMware Identity Manager node services are gracefully powered-off. Now all nodes could be powered-off if required, in vCenter.

Graceful power on of all services in VMware Identity Manager:

If all VMware Identity Manager node(s) are powered off, then power on all the node(s) in the vCenter.

After the VMware Identity Manager node is powered on, the services automatically come up. However, if step #1 was not performed, to gracefully bring up the VMware Identity Manager services follow the below steps, after performing an SSH to the VMware Identity Manager nodes as a root user in the following manner:

Start the following services on the primary postgres server

service vpostgres start
service pgService start
service horizon-workspace start

vIDM versions 3.x - 3.3.6
service elasticsearch start

vIDM versions 3.3.7 and above
/etc/init.d/opensearch start

Note: After each command verify the status of the service by running the command:
service <service-name> status

Start the following services on the two standby postgres nodes

service vpostgres start

service pgService start
service horizon-workspace start

vIDM versions 3.x - 3.3.6
service elasticsearch start

vIDM versions 3.3.7 and above
/etc/init.d/opensearch start

Note: After each command verify the status of the service by running the command:

service <service-name> status

In case, the VMware Identity Manager node(s) were powered on as mentioned in Step #1, the delegate IP (Database IP) on the primary postgres node would be lost. To re-assign, follow step #4 as mentioned in the KB 75080.

Run the command as mentioned in Step # 4 and 5 under "Cluster Graceful shut down of all services in VMware Identity Manager" section and make sure all the nodes are marked up. If any nodes are marked down, bring them up by performing the action mentioned in step #5 of the KB 75080.

Related Information

Please review these resources for additional details:

vRealize Suite Lifecycle Manager Installation, Upgrade, and Management

Troubleshooting VMware Identity Manager postgres cluster deployed through vRealize Suite Lifecycle Manager

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
ドメイン ユーザーが vRealize Log Insight 8.x でアラート クエリをフィルタリングできない (78784)

KB
•
vCenter Server 5.x をインストールしようとすると、次のエラーで失敗する：設定で vCenter Server ディレクトリ サービスのインスタンスを作成できません (2006850)

KB
•
在升级到 vRealize Log Insight 8.x 之后，主机名将恢复为 "localhost" (78761)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Identity Manager

VMware Aria Suite Lifecycle

Related Versions:

VMware vRealize Suite Lifecycle Manager 8.x

VMware Identity Manager 3.3.x

VMware Identity Manager 3.0

VMware Aria Suite Lifecycle 8.x

Take Our Survey

Support Assistant