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

Unexpected behavior occurs on an Horizon DaaS 8.0.x appliance that has Uptime >= 120 days (78758)

Last Updated: 12/9/2021Categories: InformationalTotal Views: 3602Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

Unexpected behavior occurs on an Horizon DaaS 8.0.x appliance that has been operating for 120 days or more.
You may encounter issues while:

Accessing to AstroUI.

Out of memory error is in the tomcat log (catalina,out, localhost.log, etc.)

Note: This issue is occurs when the exceeding the maximum uptime of 120 days.

Solution

To resolve this issue, Reboot the appliance on or before 120 days.

Note: Make sure the uptime of the appliance is not >= 120 days.

It is also recommended to do following operations before the reboot so that you can reboot the appliances safely:

Stop dtService

Confirm database replication lag is low by using following SQL statements:

run "select * from _slony.sl_status" and check the value of st_lag_num_events is under 9 on each DB(FDB, EDB, AVDB). This means replication lag is low.

run "select * from _slony.sl_failover_targets" and  check node-ids for set_origin and backup_id have different value on each DB.

- If you experience database replication error even doing above before rebooting the appliances please re-initialize slony.
- Please consider to reboot appliances periodically(example: 1 month) if you experience this issue less than 120 days.

Before starting to re-initialize slony, it's important to make sure role of each appliance and database instances on DaaS. Each appliance have one or more database instances running, as follows:

Service provider appliances – Fabric Database (FDB) only

Tenant appliances - Fabric Database (FDB), Element Database (EDB), and App Volumes Database (AVDB)

Desktop manager appliances - Element Database (EDB) and App Volumes Database (AVDB)

Note: If you need to re-initialize slony please follow the guideline below:

When the primary appliance fails, the secondary database is read-only.

If primary SP goes down, it will not be automatically promoted. The primary SP is always primary.

TA1 will be the master after re-initializing slony.

It is strongly recommended to back up a Database on both TA1 and TA2 before re-initializing slony.

Choose appropriate Database backup at restoring phase before re-initialize slony, otherwise pool information can be removed after re-initializing slony.

Steps to re-initialize Slony

1. Confirm master/slave status by running following SQL statements on TA2 node.

psql -U admin fdb -c "select no_comment from _slony.sl_node where no_id=(select set_origin from _slony.sl_set);"
psql -U admin edb -c "select no_comment from _slony.sl_node where no_id=(select set_origin from _slony.sl_set);"
psql -U admin avdb -c "select no_comment from _slony.sl_node where no_id=(select set_origin from _slony.sl_set);"

Example: Following output shows TA1 is master node on each Database(169.254.4.5 is address of TA1)

root@testTA2:~# psql -U admin fdb -c "select no_comment from _slony.sl_node where no_id=(select set_origin from _slony.sl_set);"
Password for user admin:
no_comment
-------------
169.254.4.5
(1 row)

root@testTA2:~# psql -U admin edb -c "select no_comment from _slony.sl_node where no_id=(select set_origin from _slony.sl_set);"
Password for user admin:
no_comment
--------------
169.254.4.5
(1 row)

root@testTA2:~# psql -U admin avdb -c "select no_comment from _slony.sl_node where no_id=(select set_origin from _slony.sl_set);"
Password for user admin:
no_comment
--------------
169.254.4.5
(1 row)
-----

- If one of master Database at least runs on TA2 you need to restore the master Database on TA2 to TA1 by following step 2 and 3.
- If all mater Database run on TA1 you can skip step 3 and re-initialize slony by following step 2 and 4.

2. Back up Database(FDB, EDB, AVDB) on both TA. Please refer to following documents when backing up Databases.

* Backing Up and Restoring Databases
https://docs.vmware.com/en/VMware-Horizon-DaaS/services/horizondaas.spmanual800/GUID-21AE458D-1E49-4D43-A72C-D3CF69F606FB.html

* Backing up the database in VMware Horizon DaaS (2100372)
https://kb.vmware.com/s/article/2100372

3. Restore master Database

Please follow the steps below to restore mater Database on TA2 to TA1

* Backing Up and Restoring Databases
https://docs.vmware.com/en/VMware-Horizon-DaaS/services/horizondaas.spmanual800/GUID-21AE458D-1E49-4D43-A72C-D3CF69F606FB.html

4. Initialize slony

Please follow the steps below to re-initialize Slony

* Reinitialize Slony
https://docs.vmware.com/en/VMware-Horizon-DaaS/services/horizondaas.spmanual800/GUID-D85773AC-0B73-43AB-B52F-48958E9D9E85.html

5. Check TA1/TA2 node status and each Database status

Confirm tenant status by accessing [appliances] -> [browse appliances] on Service Provider
Confirm Database status by following step 1.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE UEM コンソールで Content Gateway を構成する方法 (50115334)

KB
•
Mac OS X を実行する仮想マシンのディスクを拡張した後でゲスト ディスク ユーティリティを使用してパーティションを拡張できない (2069255)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon DaaS

VMware Horizon

Related Versions:

Take Our Survey

Support Assistant