Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
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.
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 dtServiceConfirm 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) onlyTenant 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 Slony1. 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 Databaseshttps://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/21003723. Restore master DatabasePlease follow the steps below to restore mater Database on TA2 to TA1* Backing Up and Restoring Databaseshttps://docs.vmware.com/en/VMware-Horizon-DaaS/services/horizondaas.spmanual800/GUID-21AE458D-1E49-4D43-A72C-D3CF69F606FB.html4. Initialize slonyPlease follow the steps below to re-initialize Slony* Reinitialize Slonyhttps://docs.vmware.com/en/VMware-Horizon-DaaS/services/horizondaas.spmanual800/GUID-D85773AC-0B73-43AB-B52F-48958E9D9E85.html5. Check TA1/TA2 node status and each Database statusConfirm tenant status by accessing [appliances] -> [browse appliances] on Service ProviderConfirm Database status by following step 1.