centos系统安装F23.8

# 建立fuwushe文件目录

[root@fair ]# mkdir /usr/local/fuwushe
[root@fair ]# cd /usr/local/fuwushe

#下载相应的文件到fuwushe目录

[root@fair fuwushe]# wget http://www.fuwushe.org/linux/centos/64/new/install.sh
[root@fair fuwushe]# wget https://f-release.oss-cn-wulanchabu.aliyuncs.com/F23.8_ad0_Linux64.zip

#设置install.sh文件权限

[root@fair fuwushe]# chmod +x install.sh

#执行 install.sh all（install.sh目前有多种用法，参数all是安装所有依赖包和服务社的软件） ，等待至执行完毕，系统即安装成功。

[root@fair fuwushe]# ./install.sh all

#安装执行过程记录

install unzip
已加载插件：fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * base: mirrors.aliyun.com
 * extras: mirrors.aliyun.com
 * updates: mirrors.aliyun.com
软件包 zip-3.0-11.el7.x86_64 已安装并且是最新版本
正在解决依赖关系
--> 正在检查事务
---> 软件包 unzip.x86_64.0.6.0-21.el7 将被 升级
---> 软件包 unzip.x86_64.0.6.0-24.el7_9 将被 更新
--> 解决依赖关系完成
依赖关系解决
================================================================================
 Package        架构            版本                     源                大小
================================================================================
正在更新:
 unzip          x86_64          6.0-24.el7_9             updates          172 k
事务概要
================================================================================
升级  1 软件包
总下载量：172 k
Downloading packages:
No Presto metadata available for updates
警告：/var/cache/yum/x86_64/7/updates/packages/unzip-6.0-24.el7_9.x86_64.rpm: 头V3 RSA/SHA256 Signature, 密钥 ID f4a80eb5: NOKEY
unzip-6.0-24.el7_9.x86_64.rpm 的公钥尚未安装
unzip-6.0-24.el7_9.x86_64.rpm                              | 172 kB   00:00     
从 http://mirrors.aliyun.com/centos/RPM-GPG-KEY-CentOS-7 检索密钥
导入 GPG key 0xF4A80EB5:
 用户ID     : "CentOS-7 Key (CentOS 7 Official Signing Key) <security@centos.org>"
 指纹       : 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7 f4a8 0eb5
 来自       : http://mirrors.aliyun.com/centos/RPM-GPG-KEY-CentOS-7
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  正在更新    : unzip-6.0-24.el7_9.x86_64                                   1/2 
  清理        : unzip-6.0-21.el7.x86_64                                     2/2 
  验证中      : unzip-6.0-24.el7_9.x86_64                                   1/2 
  验证中      : unzip-6.0-21.el7.x86_64                                     2/2 
更新完毕:
  unzip.x86_64 0:6.0-24.el7_9                                                   
完毕！
extracting files, please wait....
警告：libstdc64.rpm: 头V3 DSA/SHA1 Signature, 密钥 ID e8562897: NOKEY
	软件包 libaio-0.3.109-13.el7.x86_64 已经安装
Starting MySQL....... SUCCESS! 
mysqladmin: [Warning] Using a password on the command line interface can be insecure.
Warning: Since password will be sent to server in plain text, use ssl connection to ensure password safety.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
    case ":${PATH}:" in
                PATH=$PATH:$1
                PATH=$1:$PATH
export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE HISTCONTROL
Welcome to the redis service installer
This script will help you easily set up a running redis server
Selecting default: 6379
Selected default - /usr/local/fuwushe/redis/redis.conf
Selected default - /usr/local/fuwushe/redis/log/redis.log
Selected default - /usr/local/fuwushe/redis/
Selected config:
Port           : 6379
Config file    : /usr/local/fuwushe/redis/redis.conf
Log file       : /usr/local/fuwushe/redis/log/redis.log
Data dir       : /usr/local/fuwushe/redis/
Executable     : /usr/local/fuwushe/redis/src/redis-server
Cli Executable : /usr/local/fuwushe/redis/src/redis-cli
Copied /tmp/6379.conf => /etc/init.d/redis_6379
Installing service...
Successfully added to chkconfig!
Successfully added to runlevels 345!
Starting Redis server...
Installation successful!
/usr/local/fuwushe/jdk/bin/java  -Xms512m -Xmx512m -Xmn256m -Dnacos.standalone=true -Dnacos.member.list= -Djava.ext.dirs=/usr/local/fuwushe/jdk/jre/lib/ext:/usr/local/fuwushe/jdk/lib/ext -Xloggc:/usr/local/fuwushe/nacos/logs/nacos_gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=100M -Dloader.path=/usr/local/fuwushe/nacos/plugins/health,/usr/local/fuwushe/nacos/plugins/cmdb -Dnacos.home=/usr/local/fuwushe/nacos -jar /usr/local/fuwushe/nacos/target/nacos-server.jar  --spring.config.location=classpath:/,classpath:/config/,file:./,file:./config/,file:/usr/local/fuwushe/nacos/conf/ --logging.config=/usr/local/fuwushe/nacos/conf/nacos-logback.xml --server.max-http-header-size=524288
nacos is starting with standalone
nacos is starting，you can check the /usr/local/fuwushe/nacos/logs/start.out
警告：erlang-22.2.2-1.el6.x86_64.rpm: 头V4 RSA/SHA1 Signature, 密钥 ID 6026dfca: NOKEY
准备中...                          ################################# [100%]
正在升级/安装...
   1:erlang-22.2.2-1.el6              ################################# [100%]
已加载插件：fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * base: mirrors.aliyun.com
 * extras: mirrors.aliyun.com
 * updates: mirrors.aliyun.com
正在解决依赖关系
--> 正在检查事务
---> 软件包 socat.x86_64.0.1.7.3.2-2.el7 将被 安装
--> 解决依赖关系完成
依赖关系解决
================================================================================
 Package         架构             版本                     源              大小
================================================================================
正在安装:
 socat           x86_64           1.7.3.2-2.el7            base           290 k
事务概要
================================================================================
安装  1 软件包
总下载量：290 k
安装大小：1.1 M
Downloading packages:
socat-1.7.3.2-2.el7.x86_64.rpm                             | 290 kB   00:00     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
警告：RPM 数据库已被非 yum 程序修改。
  正在安装    : socat-1.7.3.2-2.el7.x86_64                                  1/1 
  验证中      : socat-1.7.3.2-2.el7.x86_64                                  1/1 
已安装:
  socat.x86_64 0:1.7.3.2-2.el7                                                  
完毕！
警告：rabbitmq-server-3.8.2-1.el6.noarch.rpm: 头V4 RSA/SHA256 Signature, 密钥 ID 6026dfca: NOKEY
准备中...                          ################################# [100%]
正在升级/安装...
   1:rabbitmq-server-3.8.2-1.el6      ################################# [100%]
Enabling plugins on node rabbit@fair:
rabbitmq_management
The following plugins have been configured:
  rabbitmq_management
  rabbitmq_management_agent
  rabbitmq_web_dispatch
Applying plugin configuration to rabbit@fair...
The following plugins have been enabled:
  rabbitmq_management
  rabbitmq_management_agent
  rabbitmq_web_dispatch
set 3 plugins.
Offline change; changes will take effect at broker restart.
Starting rabbitmq-server (via systemctl):  Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details.
                                                           [失败]
Error: unable to perform an operation on node 'rabbit@fair'. Please see diagnostics information and suggestions below.
Most common reasons for this are:
 * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
 * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
 * Target node is not running
In addition to the diagnostics info below:
 * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@fair
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools
DIAGNOSTICS
===========
attempted to contact: [rabbit@fair]
rabbit@fair:
  * connected to epmd (port 4369) on fair
  * epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic 
  * can't establish TCP connection to the target node, reason: timeout (timed out)
  * suggestion: check if host 'fair' resolves, is reachable and ports 25672, 4369 are not blocked by firewall
Current node details:
 * node name: 'rabbitmqcli-5249-rabbit@fair'
 * effective user's home directory: /var/lib/rabbitmq
 * Erlang cookie hash: yUurCxLUQ+Xvx08kM+BMBg==
Error: unable to perform an operation on node 'rabbit@fair'. Please see diagnostics information and suggestions below.
Most common reasons for this are:
 * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
 * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
 * Target node is not running
In addition to the diagnostics info below:
 * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@fair
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools
DIAGNOSTICS
===========
attempted to contact: [rabbit@fair]
rabbit@fair:
  * connected to epmd (port 4369) on fair
  * epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic 
  * can't establish TCP connection to the target node, reason: timeout (timed out)
  * suggestion: check if host 'fair' resolves, is reachable and ports 25672, 4369 are not blocked by firewall
Current node details:
 * node name: 'rabbitmqcli-5720-rabbit@fair'
 * effective user's home directory: /var/lib/rabbitmq
 * Erlang cookie hash: yUurCxLUQ+Xvx08kM+BMBg==
Error: unable to perform an operation on node 'rabbit@fair'. Please see diagnostics information and suggestions below.
Most common reasons for this are:
 * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
 * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
 * Target node is not running
In addition to the diagnostics info below:
 * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@fair
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools
DIAGNOSTICS
===========
attempted to contact: [rabbit@fair]
rabbit@fair:
  * connected to epmd (port 4369) on fair
  * epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic 
  * can't establish TCP connection to the target node, reason: timeout (timed out)
  * suggestion: check if host 'fair' resolves, is reachable and ports 25672, 4369 are not blocked by firewall
Current node details:
 * node name: 'rabbitmqcli-5933-rabbit@fair'
 * effective user's home directory: /var/lib/rabbitmq
 * Erlang cookie hash: yUurCxLUQ+Xvx08kM+BMBg==
Error: unable to perform an operation on node 'rabbit@fair'. Please see diagnostics information and suggestions below.
Most common reasons for this are:
 * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
 * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
 * Target node is not running
In addition to the diagnostics info below:
 * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@fair
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools
DIAGNOSTICS
===========
attempted to contact: [rabbit@fair]
rabbit@fair:
  * connected to epmd (port 4369) on fair
  * epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic 
  * can't establish TCP connection to the target node, reason: timeout (timed out)
  * suggestion: check if host 'fair' resolves, is reachable and ports 25672, 4369 are not blocked by firewall
Current node details:
 * node name: 'rabbitmqcli-6097-rabbit@fair'
 * effective user's home directory: /var/lib/rabbitmq
 * Erlang cookie hash: yUurCxLUQ+Xvx08kM+BMBg==
Error: unable to perform an operation on node 'rabbit@fair'. Please see diagnostics information and suggestions below.
Most common reasons for this are:
 * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
 * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
 * Target node is not running
In addition to the diagnostics info below:
 * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@fair
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools
DIAGNOSTICS
===========
attempted to contact: [rabbit@fair]
rabbit@fair:
  * connected to epmd (port 4369) on fair
  * epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic 
  * can't establish TCP connection to the target node, reason: timeout (timed out)
  * suggestion: check if host 'fair' resolves, is reachable and ports 25672, 4369 are not blocked by firewall
Current node details:
 * node name: 'rabbitmqcli-6302-rabbit@fair'
 * effective user's home directory: /var/lib/rabbitmq
 * Erlang cookie hash: yUurCxLUQ+Xvx08kM+BMBg==
Error: unable to perform an operation on node 'rabbit@fair'. Please see diagnostics information and suggestions below.
Most common reasons for this are:
 * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
 * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
 * Target node is not running
In addition to the diagnostics info below:
 * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@fair
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools
DIAGNOSTICS
===========
attempted to contact: [rabbit@fair]
rabbit@fair:
  * connected to epmd (port 4369) on fair
  * epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic 
  * can't establish TCP connection to the target node, reason: timeout (timed out)
  * suggestion: check if host 'fair' resolves, is reachable and ports 25672, 4369 are not blocked by firewall
Current node details:
 * node name: 'rabbitmqcli-6510-rabbit@fair'
 * effective user's home directory: /var/lib/rabbitmq
 * Erlang cookie hash: yUurCxLUQ+Xvx08kM+BMBg==
Enabling plugins on node rabbit@fair:
rabbitmq_delayed_message_exchange
The following plugins have been configured:
  rabbitmq_delayed_message_exchange
  rabbitmq_management
  rabbitmq_management_agent
  rabbitmq_web_dispatch
Applying plugin configuration to rabbit@fair...
The following plugins have been enabled:
  rabbitmq_delayed_message_exchange
set 4 plugins.
Offline change; changes will take effect at broker restart.
Using CATALINA_BASE:   /usr/local/fuwushe/tomcat
Using CATALINA_HOME:   /usr/local/fuwushe/tomcat
Using CATALINA_TMPDIR: /usr/local/fuwushe/tomcat/temp
Using JRE_HOME:        /usr/local/fuwushe/jre
Using CLASSPATH:       /usr/local/fuwushe/tomcat/bin/bootstrap.jar:/usr/local/fuwushe/tomcat/bin/tomcat-juli.jar
Using CATALINA_OPTS:   
Tomcat started.
true{"code":200,"message":"导入成功","data":{"succCount":36,"skipCount":0}}starting zuul ...
starting auth ...
starting mm-auth-api ...
starting cc ...
starting mm-biz-api ...
starting mm-organization-api ...
starting mm-customquery-api ...
starting mm-account-api ...
starting bes ...
starting hms ...
starting mm-collaboration-franchisee-api ...
starting mm-commission-api ...
starting mm-marketing-api ...
starting mm-member-api ...
starting mm-oms-api ...
starting mm-product-api ...
starting mm-tms-api ...
starting mm-wechat-api ...
starting mm-wms-api ...
starting mp ...
starting pos ...
starting scrm ...
starting sms ...
starting task ...
starting wms ...

#在客户机中输入服务器 IP:8080/cc/ ，即可见到主控系统的登录页面：