Remote Database Installation Instructions

compared with
Current by Laura Horsky
on Feb 12, 2018 09:02.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
{noformat}
# Answer the remaining questions, and allow the installation of the database components to complete.
#* {color:#ff0000}Note: After install is completed, you may receive "No such file or directory" errors for encrypt.sh and grafbridge-control. This is ok and does not affect the Remote Database installation or functions. We will be removing these steps from the installer for the Remote Database option in future releases to resolve this issue.{color}

{color:#ff0000}Warning: Problem running post-install step. Installation may not complete, or it{color}
{color:#ff0000}may be SERIOUSLY DAMAGED if it does complete.{color}
{color:#ff0000}Error running /usr/local/groundwork/foundation/scripts/encrypt.sh updateapi{color}
{color:#ff0000}\--random: /bin/sh: /usr/local/groundwork/foundation/scripts/encrypt.sh: No such{color}
{color:#ff0000}file or directory{color}
{color:#ff0000}Press \[Enter\] to continue:{color}
{warning:title=Installation Errors}
After install is completed, you may receive "No such file or directory" errors for encrypt.sh and grafbridge-control. This is ok and does not affect the Remote Database installation or functions. We will be removing these steps from the installer for the Remote Database option in future releases to resolve this issue.{warning}

{color:#ff0000}Warning: Problem running post-install step. Installation may not complete, or it{color}
{color:#ff0000}may be SERIOUSLY DAMAGED if it does complete.{color}
{color:#ff0000}Error running /usr/local/groundwork/foundation/scripts/encrypt.sh{color}
{color:#ff0000}updateapireader \--random: /bin/sh:{color}
{color:#ff0000}/usr/local/groundwork/foundation/scripts/encrypt.sh: No such file or directory{color}
{color:#ff0000}Press \[Enter\] to continue:{color}

{color:#ff0000}Warning: Problem running post-install step. Installation may not complete, or it{color}
{color:#ff0000}may be SERIOUSLY DAMAGED if it does complete.{color}
{color:#ff0000}Error running /usr/local/groundwork/grafana/scripts/grafbridge-control{color}
{color:#ff0000}\-no_backups \-tsdb influxdb \-rendering client: /bin/sh:{color}
{color:#ff0000}/usr/local/groundwork/grafana/scripts/grafbridge-control:{color}
{color:#ff0000}/usr/local/groundwork/perl/bin/perl: bad interpreter: No such file or directory{color}
{color:#ff0000}Press \[Enter\] to continue:{color}

{color:#ff0000}Warning: Problem running post-install step. Installation may not complete, or it{color}
{color:#ff0000}may be SERIOUSLY DAMAGED if it does complete.{color}
{color:#ff0000}Error running /usr/local/groundwork/grafana/scripts/grafbridge-control{color}
{color:#ff0000}\-no_backups \-server_name gwmon-3.ntus.com: /bin/sh:{color}
{color:#ff0000}/usr/local/groundwork/grafana/scripts/grafbridge-control:{color}
{color:#ff0000}/usr/local/groundwork/perl/bin/perl: bad interpreter: No such file or directory{color}
{color:#ff0000}Press \[Enter\] to continue:{color}

{color:#ff0000}Warning: Problem running post-install step. Installation may not complete, or it{color}
{color:#ff0000}may be SERIOUSLY DAMAGED if it does complete.{color}
{color:#ff0000}Error running /usr/local/groundwork/grafana/scripts/grafbridge-control{color}
{color:#ff0000}\-no_backups \-add_datasource gwmon-3.ntus.com \-default_datasource \-create_rps{color}
{color:#ff0000}\-import_dashboards: /bin/sh:{color}
{color:#ff0000}/usr/local/groundwork/grafana/scripts/grafbridge-control:{color}
{color:#ff0000}/usr/local/groundwork/perl/bin/perl: bad interpreter: No such file or directory{color}
{color:#ff0000}Press \[Enter\] to continue:{color}

{color:#ff0000}remote database finished{color}
{color:#ff0000}>Press \[Enter\] to continue{color}
# You may have a firewall surrounding your database server. This might be either iptables(8) running on the database server itself, or some external network equipment that serves the same purpose. If such a firewall is in play, you must configure it to allow access to port 5432 on the database server from the GroundWork Monitor server.
{tip:title=Setup for an iptables Firewall}