Skip to main content

Deploying a Split Installation of Faddom

Written by Itamar Rotem

Faddom can run on two servers in situations where resources are limited. This means that one runs the Tomcat (web UI) and one runs PostgreSQL (database). To ease this process, Faddom has a script that makes this process simple.

For Windows Server deployments, see Deploying a split installation of Faddom on Windows [link placeholder].

Prerequisites

  1. Communication between the two OVAs on ports 22 and 5432

  2. At least 50% disk space free on both disks. You can check the space by connecting via SSH and running df -h. If you need to increase the disk space you can follow our guide How to increase the size of the database disk on the Faddom virtual appliance?

Procedure

  1. Connect via SSH to the UI server (the existing Faddom instance) and run

    sudo /etc/illuminit/migrateDatabase.sh
  2. Follow the instructions on screen with the following parameters -

    1. Choose localserver

    2. Enter the username which by default is faddom and password

    3. Choose remotehost which is the server that will host the database

    4. Enter the IP address of the new server and faddom and the IP address of the database server

    5. Enter the password you set during the import process.

    6. Let the migration run. Once done, connect to the UI and connect your datasources.

A successful migration will have an output that looks like the below

Troubleshooting

Sudo authentication fails on the DB OVA

The migration script runs over a non-interactive SSH session, which requires passwordless sudo on the DB OVA. If the script fails with "incorrect password attempt" or "no password was provided", follow these steps.

Step by step:

  1. Verify the sudoers file exists and has the correct content:

cat /etc/sudoers.d/faddom

Expected output:

Defaults:faddom !requiretty faddom ALL=(ALL) NOPASSWD:ALL
  1. If the file is missing or incorrect, apply the fix as root:

su - echo 'Defaults:faddom !requiretty' > /etc/sudoers.d/faddom echo 'faddom ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers.d/faddom chmod 440 /etc/sudoers.d/faddom
  1. Verify the fix:

sudo -u faddom sudo whoami

Expected output: root

Important: Don't re-run the migration script until step 3 returns root.


If you experience any issues or need assistance, contact support@faddom.com.

Did this answer your question?