Administering the Command Center Web Server
The gpccws web server binary and web application files are installed in the
bin directory of your Greenplum Command Center installation.
Starting the Command Center Web Server runs the gpccws web server, starts the metrics collection agents on the segment servers, and starts a listener on the Command Center rpc port.
You can run the
gpcc command as the gpadmin user on the master host (recommended) or on the standby host. Starting Command Center on the standby host is not recommended because it can cause heavy network traffic between the Command Center agent on the master host and the backend on the standby host.
To ensure the
gpcc command is on your path, source the
gpcc_path.sh file in the Command Center installation directory or add it to the startup script for your command shell. See Setting the Greenplum Command Center Environment for instructions.
The Greenplum Database
MASTER_DATA_DIRECTORY environment variable must be set when you run the
gpcc command. This environment variable is usually set in the gpadmin user’s shell initialization script (
/home/gpadmin/.bashrc, for example). If you run
MASTER_DATA_DIRECTORY set, the
gpmetrics directory could be created in the current directory instead of in the Greenplum Database data directory, which can cause problems if you start
gpcc later with
MASTER_DATA_DIRECTORY set correctly.
gpcc command uses the gpmon role to connect to Greenplum Database. It looks for the gpmon password in the
PGPASSWORD environment variable or in the
.pgpass file in the gpadmin user’s home directory. You can instead append the
-W flag to the
gpcc commands below to have
gpcc prompt you to enter the password.
To start Greenplum Command Center
Log on to the master host or the standby host.
To log on to the standby from the master host:
$ ssh <standby-host>
Source the Command Center environmental script.
$ source /usr/local/greenplum-cc-<version>/gpcc_path.sh
Start the Command Center web server and the metrics collection agents.
$ gpcc start Starting the gpcc agents and webserver… 2019/05/07 01:51:03 Agent successfully started on 5/5 hosts 2019/05/07 01:51:03 View Greenplum Command Center at http://mdw:28090
To stop Greenplum Command Center
$ gpcc stop 2019/05/07 01:51:55 GPCC webserver and metrics collection agents have been stopped. Use gpcc start to start them again
To check the Greenplum Command Center status
$ gpcc status 2019/05/07 01:50:13 GPCC webserver: running 2019/05/07 01:50:14 GPCC agents: 5/5 agents running
gpcc reference page for full syntax for the
The web server configuration file is stored in
$GPCC_HOME/conf/app.conf. The parameters in this configuration file are set when you install Greenplum Command Center. The installer copies the Command Center installation directory, including this configuration file, to every Greenplum Database host.
See the Web Server Parameters section of Configuration File Reference for a description of the parameters in this file.
You can see a summary of the current configuration using the
gpcc --settings command.
$ gpcc --settings Install path: /usr/local Display Name: gpcc GPCC port: 28080 Kerberos: enabled Kerberos webserver name: mdw Kerberos gpdb name: gpadmin Kerberos mode: gpmon_only Kerberos path: /home/gpadmin/gpcc-kerberos.keytab SSL: disabled
If you modify the file on one host you should copy it to every other host. Be sure to restart the web server after you change the configuration. Rather than modifying the configuration directly, you can just stop Command Center and re-run the
gpccinstall-<version> installation command. This ensures the configuration is consistent on all hosts.
You can use the
gpcc krbenable command to add Kerberos authentication to the Command Center configuration. See Enabling Authentication with Kerberos for details about setting up Kerberos on the Command Center host. The
gpcc krbenable command prompts for the Kerberos principal names and artifacts and updates the configuration.
gpcc krbdisable command removes Kerberos parameters from the Command Center configuration.
Web server access and error log messages are written to
If you experience errors viewing the Greenplum Command Center Console, refer to this file for more information.
To prevent the web server log from growing to excessive size, you can set up log file rotation using