Restarting the DNS Integrity Gateway - Platform - BlueCat Gateway - 18.6.1

Gateway Installation Guide
prodname
BlueCat Gateway
version_custom
18.6.1

When the DNS Integrity Gateway is running, run the python dns_integrity_gateway.py run command from the Linux client to restart the DNS Integrity Gateway container.

Restarting the DNS Integrity Gateway container removes the container and creates a new one from the DNS Integrity Gateway image. Remove the DNS Integrity Gateway container if you are encountering issues with the DNS Integrity Gateway or something has gone wrong. Your custom workflows are preserved as they exist outside of the DNS Integrity Gateway container.

  1. Log in to the Linux client as an administratorroot/sudo.
  2. Run the dns_integrity_gateway.py run command along with the uid parameter you set when you first installed the DNS Integrity Gateway. You are prompted that the DNS Integrity Gateway container already exists and if you would like to remove it. 
    python dns_integrity_gateway.py run --uid <number>

----------------------
STARTING BLUECAT DNS INTEGRITY GATEWAY
--------------------------------------
BLUECAT_DNS_INTEGRITY_GATEWAY: /home/user/dns_integrity_gateway
BAM: 192.0.2.10
BLUECAT_DNS_INTEGRITY_GATEWAY_IMAGE: portal_img:18.6.1-XXX
VERSION:18.6.1-XXX
-----------------------------------
Checking if BlueCat DNS Integrity Gateway container already exists.
  3. At the prompt, type <Y/y> to remove the existing container (if available). Removing the container will not affect your workflows. If you type <N/n> the installation will halt. 
    The BlueCat DNS Integrity Gateway container already exists, do you want to remove it? [Y/N]y
Removing BlueCat DNS Integrity Gateway container!
Setting flask container permissions to dns_integrity_gateway dirs
You can attach to the portal using the following command: 'docker attach portal'
BlueCat DNS Integrity Gateway container is now running!

The DNS Integrity Gateway restarts. The user interface will be temporarily unavailable and any workflows actively running an operation will be terminated. All active users must log back in.

  • OPTIONAL: If necessary, attach the DNS Integrity Gateway container to the DNS Integrity Gateway if you need to run commands within the DNS Integrity Gateway container.
    docker attach portal
    Note: Attach to the DNS Integrity Gateway container if you would like to set the server's FQDN to suppress the apache2 message. However, your change may not persist if you restart the DNS Integrity Gateway at a later time.
    Tip: You can also restart DNS Integrity Gateway using the following commands:
    • docker exec portal service apache2 restart (can be run from any directory)
    • docker attach portal
service apache2 restart
      (The first command attaches to the DNS Integrity Gateway container then the second command tells the Apache Server to restart.