如何当ssh不是默认22端口时安装蓝鲸的CMDB?

如何当ssh不是默认22端口时安装蓝鲸的CMDB?

如何安装蓝鲸的cmdb?

q.前提知识:

本文基于《如何当ssh不是默认22端口时安装蓝鲸的PAAS》
https://blog.csdn.net/haoding205/article/details/82758099

1.引子:

在上文中,我们知道,快速部署蓝鲸的方法,比如在安装CMDB时的命令是:

cd /data/install
./bk_install cmdb  # 安装 cmdb 及其依赖服务   # 该步骤完成后, 可以打开 cmdb, 看到蓝鲸业务及示例业务

会不会有报错呢?让我们拭目以待:

2.安装过程记录

[root@paas-1 install]# ./bk_install cmdb
[192.168.1.103]20180919-151110 28   install nginx has been performed without FATAL stat...  skip
[192.168.1.103]20180919-151110 28   install redis has been performed without FATAL stat...  skip

         install mongodb(allproject) on host: 192.168.1.102         

[192.168.1.102]20180919-151113 516   create directories ...
[192.168.1.102]20180919-151113 204   >> rsync -a /data/src/service/mongodb /data/bkce/service/
[192.168.1.102]20180919-151115 44   render configuration file:
[192.168.1.102]20180919-151115 64   expr: find /data/src/service/support-files/templates -name "*mongodb*"
[192.168.1.102]20180919-151115 67   templates file: #etc#mongodb.yaml
[192.168.1.102]20180919-151115 78   target file: /data/bkce//etc/mongodb.yaml
[192.168.1.103]20180919-151115 276   install mongodb(allproject) done

           install gse(allproject) on host: 192.168.1.103           


                        installing gse module                        
[192.168.1.103]20180919-151118 204   >> rsync -a --exclude support-files --delete /data/src/gse /data/bkce/
[192.168.1.103]20180919-151133 204   >> rsync -a /data/src/cert /data/bkce/
[192.168.1.103]20180919-151133 1389   render gse configurations
[192.168.1.103]20180919-151133 44   render configuration file:
[192.168.1.103]20180919-151133 64   expr: find /data/src/gse/support-files/templates -name "*#*"
[192.168.1.103]20180919-151133 67   templates file: agent_win_x86#conf#procinfo.json
(此处省略100000字)
[192.168.1.103]20180919-151423 122   start to make migration for gse ...
[192.168.1.103]20180919-151423 130   on-migrate ... /data/bkce/gse/server/bin/on_migrate

[192.168.1.103]20180919-151423 51   init gse zk base path
[192.168.1.103]20180919-151423 57   init redis zk config
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   455    0   455    0     0    581      0 --:--:-- --:--:-- --:--:--   583
[192.168.1.103]20180919-151424 84   get bk_biz_id 2
[192.168.1.103]20180919-151424 99   parse dataid result: redis,
[192.168.1.103]20180919-151424 122   init redis dataid zk config
[192.168.1.103]20180919-151424 120   migrate gse(server) done
[192.168.1.103]20180919-151425 78   starting gse(ALL) on host: 192.168.1.103

[192.168.1.103]20180919-151427|225	192.168.1.103  -- gse node on /data/bkce/gse/server: server
[192.168.1.103]20180919-151427|134	start gse_dba ...Done
[192.168.1.103]20180919-151427|134	start gse_data ...Done
[192.168.1.103]20180919-151427|134	start gse_task ...Done
[192.168.1.103]20180919-151428|134	start gse_api ...Done
[192.168.1.103]20180919-151428|134	start gse_btsvr ...Done
[192.168.1.103]20180919-151428|134	start gse_opts ...Done
[192.168.1.103]20180919-151428|134	start gse_ops ...Done
[192.168.1.103]20180919-151428|134	start gse_alarm ...Done

[192.168.1.101] nginx: RUNNING

[192.168.1.103] redis: RUNNING

[192.168.1.101] zk: RUNNING

[192.168.1.102] zk: RUNNING

[192.168.1.103] zk: RUNNING

[192.168.1.102] mongod: RUNNING

[192.168.1.103] gse_alarm: RUNNING
[192.168.1.103] gse_ops: RUNNING
[192.168.1.103] gse_opts: RUNNING
[192.168.1.103] gse_api: RUNNING
[192.168.1.103] gse_btsvr: RUNNING
[192.168.1.103] gse_data: RUNNING
[192.168.1.103] gse_dba: RUNNING
[192.168.1.103] gse_task: RUNNING

[192.168.1.103] cmdb-nginx: RUNNING
[192.168.1.103] server      cmdb_adminserver                 RUNNING   pid 16427, uptime 0:00:51
[192.168.1.103] server      cmdb_apiserver                   RUNNING   pid 16416, uptime 0:00:51
[192.168.1.103] server      cmdb_auditcontoller              RUNNING   pid 16412, uptime 0:00:51
[192.168.1.103] server      cmdb_datacollection              RUNNING   pid 16426, uptime 0:00:51
[192.168.1.103] server      cmdb_eventserver                 RUNNING   pid 16417, uptime 0:00:51
[192.168.1.103] server      cmdb_hostcontroller              RUNNING   pid 16406, uptime 0:00:51
[192.168.1.103] server      cmdb_hostserver                  RUNNING   pid 16407, uptime 0:00:51
[192.168.1.103] server      cmdb_objectcontroller            RUNNING   pid 16409, uptime 0:00:51
[192.168.1.103] server      cmdb_proccontroller              RUNNING   pid 16428, uptime 0:00:51
[192.168.1.103] server      cmdb_procserver                  RUNNING   pid 16411, uptime 0:00:51
[192.168.1.103] server      cmdb_toposerver                  RUNNING   pid 16408, uptime 0:00:51
[192.168.1.103] server      cmdb_webserver                   RUNNING   pid 16410, uptime 0:00:51

如果以上步骤没有报错, 你现在可以通过 http://cmdb.abc.com:80 访问配置平台,

[root@paas-1 install]# 

如下图:
如何当ssh不是默认22端口时安装蓝鲸的CMDB?_第1张图片

3.验证安装成功的界面

3.1登录cmdb首页界面

如何当ssh不是默认22端口时安装蓝鲸的CMDB?_第2张图片

3.2进程管理界面

如何当ssh不是默认22端口时安装蓝鲸的CMDB?_第3张图片

4.结论

安装蓝鲸的cmdb成功,那为什么没有报关于SSH端口22的错误呢?因为这个坑在上一个篇章“安装paas”就趟过去了,所以此篇章就没有报错了。

5.其他参考

http://docs.bk.tencent.com/bkce_install_guide/setup/quick_install.html

好了,聪明如你,知道了如何当ssh不是默认22端口时安装蓝鲸的cmdb,是不是很欢喜 _

还有其他问题的可以在评论区留言或者扫码加博主获取资源或者提问。
如何当ssh不是默认22端口时安装蓝鲸的CMDB?_第4张图片

你可能感兴趣的:(蓝鲸智云)