Product | Version |
Pivotal Greenplum (GPDB) | 4.3.x |
Pivotal Greenplum Command Center (GPCC) | |
Others |
gpperfmon_install
[--enable --password <gpmon_password> --port <gpdb_port>]
[--pgpass <path_to_file>]
[--verbose]git
功能大體是:
建立greenplum監控用數據庫(gpperfmon)
建立greenplum監控用數據庫角色(gpmon)
配置greenplum數據庫接受來自perfmon監控的連接文件(pg_hba.conf和.pgpass)
設置postgresql.conf文件,增長啓用監控的參數。(這些參數默認會添加在文件的末尾)
設置pg_hba.conf文件,增長以下信息:
local gpperfmon gpmon md5
host all gpmon 127.0.0.1/28 md5web
gpstop -r
unzip greenplum-db-4.3.11.3-rhel5-x86_64.zipsql
/greenplum-cc-web-3.0.2-LINUX-x86_64.bin數據庫
source /usr/local/greenplum-cc-web/gpcc_path.shide
gpcmdr --setup
gpcmdr --start
問題1工具
During the new installation of Greenplum Command Center (GPCC), an error was encountered:post
[gpadmin@mdw gpseg-1]$ gpcmdr --setup An instance name is used by the Greenplum Command Center as a way to uniquely identify a Greenplum Database that has the monitoring components installed and configured. This name is also used to control specific instances of the Greenplum Command Center web UI. Instance names can contain letters, digits and underscores and are not case sensitive. Please enter a new instance name: > gpcc The web component of the Greenplum Command Center can connect to a monitor database on a remote Greenplum Database. Is the master host for the Greenplum Database remote? Yy|Nn (default=N): > n The display name is shown in the web interface and does not need to be a hostname. What would you like to use for the display name for this instance: > gpcc What port does the Greenplum Database use? (default=5432): > Creating instance schema in GPDB. Please wait ... Failed to setup Command Center instance gpcc: Exception encountered while fetching GPDB version info Connection error for query select version();: FATAL: no pg_hba.conf entry for host "::1", user "gpmon", database "gpperfmon", SSL off [gpadmin@mdw gpseg-1]$
解決fetch
Add the below line to the pg_hba.conf file:this
host gpperfmon gpmon ::1/128 trust
Once the line is added, issue a gpstop -u for the changes to take effect immediately without DB restart.spa
Now retry the command center setup and it should now succeed.
gpstop -u (從新加載配置)
問題2 登陸界面失敗
解決
host gpperfmon gpmon :::/0 trust
gpstop -u (從新加載配置)
注意事項 : 修改配置後使用 -u 參數進行從新加載配置,不能從新啓動,否者gp啓動失敗。卡在啓動界面中。
緣由是在 pg_hba.conf 中添加了
host gpperfmon gpmon :::/0 trust
問題3
擴展節點後監控對新節點沒有跟進
解決方案都是臨時,具體緣由待調查