#昊鼎王五：如何安装蓝鲸智云v3.1.7社区版本之002安装主要产品？
安装“蓝鲸智云”社区版-记录2-安装主要产品
#Q.前提知识：
本文基于《昊鼎王五：如何安装蓝鲸智云v3.1.7社区版本之安装基础模块？》
https://blog.csdn.net/haoding205/article/details/82697765
本篇安装蓝鲸智云v3.1.7社区版本之002安装主要产品
#1.安装
##1.1.执行安装命令
[root@hd103 install]# ./bk_install bk_products
[192.168.1.103]20180412-094932 21 install cmdb has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 install job has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 install paas has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 install bkdata has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 install fta has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 install gse has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 install license has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 install bkarchiva has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 initdata gse has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 initdata paas has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 initdata cmdb has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 initdata job has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 initdata fta has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 start license has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 start gse has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 21 start cmdb has been performed without FATAL stat... done
[192.168.1.103]20180412-094932 425 start job on host: 192.168.1.103
job already started(PID=8012)
[192.168.1.103]20180412-094933 425 start open_paas on host: 192.168.1.103
initdata for bkdata
[192.168.1.103]20180412-094934 278 init database for bkdata from sql file:
[192.168.1.103]20180412-094934 283 found sql script: /data/src/bkdata/support-files/sql/init_databus.sql
[192.168.1.103]20180412-094936 289 load sql script done
[192.168.1.103]20180412-094936 283 found sql script: /data/src/bkdata/support-files/sql/init_monitor.sql
[192.168.1.103]20180412-094941 289 load sql script done
[192.168.1.103]20180412-094941 299 init database for done
Operations to perform:
Apply all migrations: trt
Running migrations:
Rendering model states... DONE
Applying trt.0001_initial... OK
Applying trt.0002_auto_20170407_1653... OK
.
----------------------------------------------------------------------
Ran 1 test in 1.078s
OK
=================set reserved dataid=================
blueking APP ID: 3
update reserved dataids DONE
[192.168.1.101]20180412-094949 1829 create new topic: connect-offsets.etl with partitions:5,replication factor:2
WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
Created topic "connect-offsets.etl".
[192.168.1.101]20180412-094951 1829 create new topic: connect-configs.etl with partitions:1,replication factor:2
WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
Created topic "connect-configs.etl".
[192.168.1.101]20180412-094952 1829 create new topic: connect-status.etl with partitions:5,replication factor:2
WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
Created topic "connect-status.etl".
[192.168.1.101]20180412-094954 1829 create new topic: connect-offsets.jdbc with partitions:5,replication factor:2
WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
Created topic "connect-offsets.jdbc".
[192.168.1.101]20180412-094955 1829 create new topic: connect-configs.jdbc with partitions:1,replication factor:2
WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
Created topic "connect-configs.jdbc".
[192.168.1.101]20180412-094957 1829 create new topic: connect-status.jdbc with partitions:5,replication factor:2
WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
Created topic "connect-status.jdbc".
[192.168.1.101]20180412-094959 1829 create new topic: connect-offsets.es with partitions:5,replication factor:2
WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
Created topic "connect-offsets.es".
[192.168.1.101]20180412-095000 1829 create new topic: connect-configs.es with partitions:1,replication factor:2
WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
Created topic "connect-configs.es".
[192.168.1.101]20180412-095002 1829 create new topic: connect-status.es with partitions:5,replication factor:2
WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
Created topic "connect-status.es".
[192.168.1.103]20180412-095005 425 start bkdata on host: 192.168.1.101
[192.168.1.103]20180412-095017 425 start fta on host: 192.168.1.101
starting supervisor...
___ ___
/\__\ /\ \
/:/ _/_ ___ /::\ \
/:/ /\__\ /\__\ /:/\:\ \
/:/ /:/ / /:/ / /:/ /::\ \
/:/_/:/ / /:/__/ /:/_/:/\:\__\
\:\/:/ / /::\ \ \:\/:/ \/__/
\::/__/ /:/\:\ \ \::/__/
\:\ \ \/__\:\ \ \:\ \
\:\__\ \:\__\ \:\__\
\/__/ \/__/ \/__/
starting fta...
[started].
[192.168.1.103]20180412-095103 425 start bkarchiva on host: 192.168.1.103
starting bkarchiva
[192.168.1.102] license: 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: RUNNING
[192.168.1.103] cmdb-nginx: RUNNING
[192.168.1.103] job: RUNNING
---------------------------------------------------------------------------------------------------------
[192.168.1.103] open_paas appengine RUNNING pid 31583, uptime 0:01:53
[192.168.1.103] open_paas esb RUNNING pid 31582, uptime 0:01:53
[192.168.1.103] open_paas login RUNNING pid 31581, uptime 0:01:53
[192.168.1.103] open_paas paas RUNNING pid 31580, uptime 0:01:53
---------------------------------------------------------------------------------------------------------
[192.168.1.101] monitor monitor-common:jobserver RUNNING pid 12930, uptime 0:01:27
[192.168.1.101] monitor monitor-common:logging RUNNING pid 12931, uptime 0:01:27
[192.168.1.101] monitor monitor-common:polling RUNNING pid 12932, uptime 0:01:27
[192.168.1.101] monitor monitor-common:scheduler RUNNING pid 12933, uptime 0:01:27
[192.168.1.101] monitor monitor-dectector:detect RUNNING pid 12934, uptime 0:01:27
[192.168.1.101] monitor monitor-dectector:detect_cron RUNNING pid 12935, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:collect0 RUNNING pid 12927, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:collect1 RUNNING pid 12928, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:converge0 RUNNING pid 12918, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:converge1 RUNNING pid 12919, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:converge2 RUNNING pid 12920, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:converge3 RUNNING pid 12921, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:converge4 RUNNING pid 12917, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:job RUNNING pid 12922, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:poll_alarm RUNNING pid 12915, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:poll_gse_base_alarm RUNNING pid 12914, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:poll_gse_custom_out_str RUNNING pid 12929, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:poll_jungle_alert RUNNING pid 12916, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:solution0 RUNNING pid 12925, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:solution1 RUNNING pid 12926, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:solution2 RUNNING pid 12923, uptime 0:01:27
[192.168.1.101] monitor monitor-kernel:solution3 RUNNING pid 12924, uptime 0:01:27
[192.168.1.101] dataapi dataapi RUNNING pid 13265, uptime 0:01:22
[192.168.1.101] databus databus_es RUNNING pid 16018, uptime 0:00:05
[192.168.1.101] databus databus_etl RUNNING pid 16019, uptime 0:00:05
[192.168.1.101] databus databus_jdbc RUNNING pid 16017, uptime 0:00:05
[192.168.1.101] fta common:apiserver RUNNING pid 13828, uptime 0:01:24
[192.168.1.101] fta common:jobserver RUNNING pid 13825, uptime 0:01:24
[192.168.1.101] fta common:logging RUNNING pid 13830, uptime 0:01:24
[192.168.1.101] fta common:polling0 RUNNING pid 13827, uptime 0:01:24
[192.168.1.101] fta common:polling1 RUNNING pid 13826, uptime 0:01:24
[192.168.1.101] fta common:qos RUNNING pid 13821, uptime 0:01:24
[192.168.1.101] fta common:scheduler0 RUNNING pid 13824, uptime 0:01:24
[192.168.1.101] fta common:scheduler1 RUNNING pid 13823, uptime 0:01:24
[192.168.1.101] fta common:scheduler2 RUNNING pid 13822, uptime 0:01:24
[192.168.1.101] fta common:webserver RUNNING pid 13829, uptime 0:01:24
[192.168.1.101] fta fta:collect0 RUNNING pid 13818, uptime 0:01:24
[192.168.1.101] fta fta:collect1 RUNNING pid 13814, uptime 0:01:24
[192.168.1.101] fta fta:collect2 RUNNING pid 13816, uptime 0:01:24
[192.168.1.101] fta fta:collect3 RUNNING pid 13817, uptime 0:01:24
[192.168.1.101] fta fta:converge0 RUNNING pid 13807, uptime 0:01:24
[192.168.1.101] fta fta:converge1 RUNNING pid 13810, uptime 0:01:24
[192.168.1.101] fta fta:converge2 RUNNING pid 13809, uptime 0:01:24
[192.168.1.101] fta fta:converge3 RUNNING pid 13819, uptime 0:01:24
[192.168.1.101] fta fta:job RUNNING pid 13813, uptime 0:01:24
[192.168.1.101] fta fta:match_alarm0 RUNNING pid 13811, uptime 0:01:24
[192.168.1.101] fta fta:match_alarm1 RUNNING pid 13820, uptime 0:01:24
[192.168.1.101] fta fta:match_alarm2 RUNNING pid 13815, uptime 0:01:24
[192.168.1.101] fta fta:match_alarm3 RUNNING pid 13812, uptime 0:01:24
[192.168.1.101] fta fta:poll_alarm RUNNING pid 13806, uptime 0:01:24
[192.168.1.101] fta fta:solution RUNNING pid 13808, uptime 0:01:24
[192.168.1.103] bkarchiva: RUNNING
[root@hd103 install]#
#2.配置域名解析：
192.168.1.101 jobs.hd68.com
192.168.1.101 paas.hd68.com
192.168.1.101 cmdb.hd68.com
[root@hd101 ~]# ip a
em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 90:b1:1c:93:ab:29 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.101/24 brd 192.168.1.255 scope global em1
valid_lft forever preferred_lft forever
inet6 fe80::92b1:1cff:fe93:ab29/64 scope link
valid_lft forever preferred_lft forever
[root@hd101 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 hd101
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.101 jobs.hd68.com
192.168.1.101 paas.hd68.com
192.168.1.101 cmdb.hd68.com
192.168.1.101 kafka_1
192.168.1.102 kafka_2
192.168.1.103 kafka_3
192.168.1.101 zk_1
192.168.1.102 zk_2
192.168.1.103 zk_3
[root@hd101 ~]#
[root@hd102 ~]# ip a
1:p1p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether c8:1f:66:27:02:cd brd ff:ff:ff:ff:ff:ff
inet 192.168.1.102/24 brd 192.168.1.255 scope global p1p1
valid_lft forever preferred_lft forever
inet6 fe80::ca1f:66ff:fe27:2cd/64 scope link
valid_lft forever preferred_lft forever
[root@hd102 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 hd102
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.101 jobs.hd68.com
192.168.1.101 paas.hd68.com
192.168.1.101 cmdb.hd68.com
192.168.1.101 kafka_1
192.168.1.102 kafka_2
192.168.1.103 kafka_3
192.168.1.101 zk_1
192.168.1.102 zk_2
192.168.1.103 zk_3
[root@hd102 ~]#
[root@hd103 ~]# ip a
1: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether b8:ca:3a:7c:24:df brd ff:ff:ff:ff:ff:ff
inet 192.168.1.103/24 brd 192.168.1.255 scope global em1
valid_lft forever preferred_lft forever
inet6 fe80::baca:3aff:fe7c:24df/64 scope link
valid_lft forever preferred_lft forever
[root@hd103 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 hd103
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.101 jobs.hd68.com
192.168.1.101 paas.hd68.com
192.168.1.101 cmdb.hd68.com
192.168.1.101 kafka_1
192.168.1.102 kafka_2
192.168.1.103 kafka_3
192.168.1.101 zk_1
192.168.1.102 zk_2
192.168.1.103 zk_3
[root@hd103 ~]#
#3.验证访问
##3.1.访问
问：访问cmdb，job 默认账号密码是多少啊？
答： /data/install/globals.env 这配置文件中有显示
默认账号密码是：
admin
blueking
此时，可以通过浏览器打开蓝鲸了。cmdb，paas 都应该能访问才算是正常
#4.其他帮助信息
##4.1.关于域名写错后的改正
在/etc/hosts里面的jobs.hd68.com少些了一个s，等到所有安装完毕了，才发现，结果paas.hd68.com和cmdb.hd68.com都能访问，但是jobs.hd68.com访问时报错“账号密码”,这个怎么解决啊？
答：先查看/etc/hosts和/data/install/global.env 这两个文件，global.env配置的正确就可以了，host的可以修改。
再根据上述的解答，再按照“更新域名的维护方案”，操作一遍：http://bbs.bk.tencent.com/forum.php?mod=viewthread&tid=505
果然是能够访问了：http://jobs.hd68.com/?main&appId=2
好了，聪明如你，知道了安装蓝鲸智云v3.1.7社区版本之002安装主要产品，是不是很欢喜 _
还有其他问题的可以在评论区留言或者扫码加博主获取资源或者提问。
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
