Page History

...

• A recommended or supported distribution (see Operating Systems) with at least 4 CPU cores, 16 GB RAM and 300 GB disk space.
• The filesystems for /opt/panagenda/pgdata, /opt/panagenda/appdata and /opt/panagenda/logs are mounted, and Docker waits for them at boot (see Partitioning).
• Docker Engine and the Docker Compose plugin are installed, running and enabled at boot.
• Ports 80 and 443 are free.
• The server address users will open is registered in DNS and points to the host, and the host has the correct time zone (see Network).
• The host resolves the common names of your Domino servers, for example MailServer01 (see Domino Name Resolution / DNS).
• You can log in to the host via SSH with root rights, and copy files to it (for example with scp or WinSCP).
• For the online installer: the host reaches docker.panagenda.com over HTTPS.

...

Before the installation starts, the installer asks for the server address: the name users type in their browser to open iDNA and its Metabase reports. iDNA also uses it in the links of Metabase emails and in iDNA alert emails.

...

• "this installer must be run as root or with sudo": run the installer in a root shell (sudo -i) or with sudo.
• "the following required tools are missing": install the tools the message names and start the installer again. On Ubuntu, fdisk is a package of its own (apt install fdisk).
• "required port(s) … are already in use": another service, for example Apache or nginx, uses port 80 or 443. Find it with ss -tlnp 'sport = :80' or ss -tlnp 'sport = :443', stop or reconfigure it, and start the installer again.
• SELinux error about semanage or restorecon: install the package policycoreutils-python-utils and start the installer again.
• "exec format error" when the containers start: the host has an ARM processor. iDNA requires x86_64.
• iDNA cannot reach a Domino server by its name: check the name resolution inside iDNA. The first command must show the IP address of the Domino server, the second shows the search domains iDNA uses, the third checks the Notes port:

  Code Block
  language bash
  docker exec panagenda_idna getent hosts MailServer01 docker exec panagenda_idna cat /etc/resolv.conf docker exec panagenda_idna nc -zv -w 5 MailServer01 1352

  If the name resolves on the host but not inside iDNA, compare the search domains with those of the host. On RHEL and AlmaLinux, also check whether the name is only in the host's /etc/hosts, which iDNA does not see there (see Domino Name Resolution / DNS). After you change the DNS settings of the host, run ifa restart; if that does not help, restart the host.
• iDNA cannot reach Domino servers or other systems: the internal Docker network may collide with a network in your environment. Run ifa diagnose-network; if it reports a collision, change PANAGENDA_COMPOSE_NETWORK_SUBNET (see Configuration File). The check cannot see networks the host has no route to; ask your network team if in doubt.
• Links in Metabase or in emails do not open, or Metabase shows another address than users type: the server address is a name or IP address that users cannot reach. Run ifa hostname and choose the name your users use.
• iDNA shows no data after a reboot: a filesystem for the iDNA directories was not mounted when Docker started. Run ifa down, mount the filesystems, run ifa start, and add the setting that makes Docker wait for them (see Partitioning).

...