Initialize Slony for a Desktop Manager or Organization

You can initialize slony on the Maintenance page in the Service Center user interface.

To initialize slony for an organization, run each of the command below as root on each appliance in the organization.

Note: When you reinitialize slony for the EDB, you must reinitialize slony for the AVDB as well.

Procedure

In /usr/local/desktone/scripts, run the slony-status script for the organization. The example below is for organization 1000. For appliances on Horizon DaaS versions earlier than 9.0.0 (or Horizon Cloud 19.3), you can skip this step.
```
slony-status 1000
```
If there is a slony issue, a message displays confirming that.
Stop dtService on all nodes:
```
service dtService stop
```
Stop slon daemons (kill daemons on target nodes):
```
killall slon
```
Run this command on the target database (FDB, EDB, or AVDB):
```
psql -Uadmin fdb -p 6432
drop schema _slony cascade;
```
Note: Drop the schema only for the affected database pair.
If you stopped dtService on the Primary service provider node for re-initialization of the FDB on the service provider appliances, then start the service again on the primary service provider node:
```
service dtService start
```

Start slon daemons as follows.

For the service provider org, start the daemon for the FDB:
```
/usr/local/desktone/scripts/start_slon_fdb.sh
```

For the tenant org, start the daemons for all databases:

/usr/local/desktone/scripts/start_slon_fdb.sh 
/usr/local/desktone/scripts/start_slon_edb.sh 
/usr/local/desktone/scripts/start_slon_avdb.sh

Verify the slony process:
```
ps -aux | grep slon
```
In /usr/local/desktone/scripts, run the slony-status script for the organization. The example below is for organization 1000. For appliances on Horizon DaaS versions earlier than 9.0.0 (or Horizon Cloud 19.3), you can skip this step.
```
slony-status 1000
```
The last message printed indicates which appliance is the replication primary. You need to select the IP address for this appliance in the Master IP menu below.
In the Service Center, select appliances > maintenance.
In the Slony Operations section of the page, use the Organization id drop-down menu to select the Org ID of the appliance to which the init slony will be performed.
The DB instance name and Master IP menus appear.
Note: The Master IP menu does not appear for appliances on Horizon DaaS versions earlier than 9.0.0 (or Horizon Cloud 19.3).
Use the DB instance name menu to select the name of the database instance (Fabric, Element, or Appvolumes) for init slony.
If you selected Element or Appvolumes, the Element ID menu appears.
If you selected Element or Appvolumes above, use the Element ID drop-down menu to select the ID of the Desktop Manager to list as New Master IP for the init slony operation. If you selected Fabric above, skip this step.
Use the Master IP menu to select the appropriate IP address for the DB primary. For appliances on Horizon DaaS versions earlier than 9.0.0 ( or Horizon Cloud 19.3), skip this step.
Click Init Slony.
If you have performed a slony reinit on the avdb of a tenant appliance, then restart the wem-diagnose-service:
```
service diagnose restart
```
Note: This is not required for an avdb slony reinit on a desktop manager only appliance.