Linux上搭建meterSphere
镜像下载、域名解析、时间同步请点击 阿里云开源镜像站
一、安装Docker
（1）安装CentOS Docker
curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun
执行后效果：
[root@localhost base]# curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun
# Executing docker install script, commit: 93d2499759296ac1f9c510605fef85052a2c32be
Warning: the "docker" command appears to already exist on this system.
If you already have Docker installed, this script can cause trouble, which is
why we're displaying this warning and provide the opportunity to cancel the
installation.
If you installed the current Docker package using this script and are using it
again to update Docker, you can safely ignore this message.
You may press Ctrl+C now to abort this script.
+ sleep 20
+ sh -c 'yum install -y -q yum-utils'
Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version
+ sh -c 'yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo'
Loaded plugins: fastestmirror, langpacks
adding repo from: https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
grabbing file https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo
repo saved to /etc/yum.repos.d/docker-ce.repo
+ '[' stable '!=' stable ']'
+ sh -c 'yum makecache'
Loaded plugins: fastestmirror, langpacks
base | 3.6 kB 00:00:00
docker-ce-stable | 3.5 kB 00:00:00
extras | 2.9 kB 00:00:00
updates | 2.9 kB 00:00:00
Loading mirror speeds from cached hostfile
* base: mirrors.aliyun.com
* extras: mirrors.aliyun.com
* updates: mirrors.aliyun.com
Metadata Cache Created
+ '[' -n '' ']'
+ sh -c 'yum install -y -q docker-ce'
+ version_gte 20.10
+ '[' -z '' ']'
+ return 0
+ sh -c 'yum install -y -q docker-ce-rootless-extras'
Package docker-ce-rootless-extras-20.10.12-3.el7.x86_64 already installed and latest version
================================================================================
To run Docker as a non-privileged user, consider setting up the
Docker daemon in rootless mode for your user:
dockerd-rootless-setuptool.sh install
Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.
To run the Docker daemon as a fully privileged service, but granting non-root
users access, refer to https://docs.docker.com/go/daemon-access/
WARNING: Access to the remote API on a privileged Docker daemon is equivalent
to root access on the host. Refer to the 'Docker daemon attack surface'
documentation for details: https://docs.docker.com/go/attack-surface/
================================================================================
（2）安装 Docker Engine-Community
sudo yum install -y yum-utils device-mapper-persistent-data lvm2
执行后效果
[root@localhost base]# sudo yum install -y yum-utils \
> device-mapper-persistent-data \
> lvm2
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirrors.aliyun.com
* extras: mirrors.aliyun.com
* updates: mirrors.aliyun.com
Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package device-mapper-persistent-data.x86_64 0:0.6.3-1.el7 will be updated
---> Package device-mapper-persistent-data.x86_64 0:0.8.5-3.el7_9.2 will be an update
---> Package lvm2.x86_64 7:2.02.166-1.el7 will be updated
---> Package lvm2.x86_64 7:2.02.187-6.el7_9.5 will be an update
--> Processing Dependency: lvm2-libs = 7:2.02.187-6.el7_9.5 for package: 7:lvm2-2.02.187-6.el7_9.5.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_141)(64bit) for package: 7:lvm2-2.02.187-6.el7_9.5.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_138)(64bit) for package: 7:lvm2-2.02.187-6.el7_9.5.x86_64
--> Running transaction check
---> Package device-mapper-libs.x86_64 7:1.02.135-1.el7 will be updated
--> Processing Dependency: device-mapper-libs = 7:1.02.135-1.el7 for package: 7:device-mapper-1.02.135-1.el7.x86_64
---> Package device-mapper-libs.x86_64 7:1.02.170-6.el7_9.5 will be an update
---> Package lvm2-libs.x86_64 7:2.02.166-1.el7 will be updated
---> Package lvm2-libs.x86_64 7:2.02.187-6.el7_9.5 will be an update
--> Processing Dependency: device-mapper-event = 7:1.02.170-6.el7_9.5 for package: 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64
--> Running transaction check
---> Package device-mapper.x86_64 7:1.02.135-1.el7 will be updated
---> Package device-mapper.x86_64 7:1.02.170-6.el7_9.5 will be an update
---> Package device-mapper-event.x86_64 7:1.02.135-1.el7 will be updated
---> Package device-mapper-event.x86_64 7:1.02.170-6.el7_9.5 will be an update
--> Processing Dependency: device-mapper-event-libs = 7:1.02.170-6.el7_9.5 for package: 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64
--> Running transaction check
---> Package device-mapper-event-libs.x86_64 7:1.02.135-1.el7 will be updated
---> Package device-mapper-event-libs.x86_64 7:1.02.170-6.el7_9.5 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================================================================
Updating:
device-mapper-persistent-data x86_64 0.8.5-3.el7_9.2 updates 423 k
lvm2 x86_64 7:2.02.187-6.el7_9.5 updates 1.3 M
Updating for dependencies:
device-mapper x86_64 7:1.02.170-6.el7_9.5 updates 297 k
device-mapper-event x86_64 7:1.02.170-6.el7_9.5 updates 192 k
device-mapper-event-libs x86_64 7:1.02.170-6.el7_9.5 updates 192 k
device-mapper-libs x86_64 7:1.02.170-6.el7_9.5 updates 325 k
lvm2-libs x86_64 7:2.02.187-6.el7_9.5 updates 1.1 M
Transaction Summary
============================================================================================================================================================================================
Upgrade 2 Packages (+5 Dependent packages)
Total size: 3.8 M
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64 1/14
Updating : 7:device-mapper-1.02.170-6.el7_9.5.x86_64 2/14
Updating : 7:device-mapper-event-libs-1.02.170-6.el7_9.5.x86_64 3/14
Updating : 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64 4/14
Updating : 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64 5/14
Updating : device-mapper-persistent-data-0.8.5-3.el7_9.2.x86_64 6/14
Updating : 7:lvm2-2.02.187-6.el7_9.5.x86_64 7/14
Cleanup : 7:lvm2-2.02.166-1.el7.x86_64 8/14
Cleanup : 7:lvm2-libs-2.02.166-1.el7.x86_64 9/14
Cleanup : 7:device-mapper-event-1.02.135-1.el7.x86_64 10/14
Cleanup : 7:device-mapper-event-libs-1.02.135-1.el7.x86_64 11/14
Cleanup : 7:device-mapper-1.02.135-1.el7.x86_64 12/14
Cleanup : 7:device-mapper-libs-1.02.135-1.el7.x86_64 13/14
Cleanup : device-mapper-persistent-data-0.6.3-1.el7.x86_64 14/14
Verifying : 7:device-mapper-event-1.02.170-6.el7_9.5.x86_64 1/14
Verifying : 7:lvm2-libs-2.02.187-6.el7_9.5.x86_64 2/14
Verifying : device-mapper-persistent-data-0.8.5-3.el7_9.2.x86_64 3/14
Verifying : 7:device-mapper-1.02.170-6.el7_9.5.x86_64 4/14
Verifying : 7:device-mapper-event-libs-1.02.170-6.el7_9.5.x86_64 5/14
Verifying : 7:lvm2-2.02.187-6.el7_9.5.x86_64 6/14
Verifying : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64 7/14
Verifying : 7:device-mapper-event-libs-1.02.135-1.el7.x86_64 8/14
Verifying : 7:device-mapper-libs-1.02.135-1.el7.x86_64 9/14
Verifying : 7:lvm2-2.02.166-1.el7.x86_64 10/14
Verifying : device-mapper-persistent-data-0.6.3-1.el7.x86_64 11/14
Verifying : 7:device-mapper-1.02.135-1.el7.x86_64 12/14
Verifying : 7:lvm2-libs-2.02.166-1.el7.x86_64 13/14
Verifying : 7:device-mapper-event-1.02.135-1.el7.x86_64 14/14
Updated:
device-mapper-persistent-data.x86_64 0:0.8.5-3.el7_9.2 lvm2.x86_64 7:2.02.187-6.el7_9.5
Dependency Updated:
device-mapper.x86_64 7:1.02.170-6.el7_9.5 device-mapper-event.x86_64 7:1.02.170-6.el7_9.5 device-mapper-event-libs.x86_64 7:1.02.170-6.el7_9.5
device-mapper-libs.x86_64 7:1.02.170-6.el7_9.5 lvm2-libs.x86_64 7:2.02.187-6.el7_9.5
Complete!
（3）启动并检查docker状态
sudo systemctl start docker
sudo systemctl status docker
[root@localhost base]# sudo systemctl start docker
[root@localhost base]# sudo systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/etc/systemd/system/docker.service; disabled; vendor preset: disabled)
Active: active (running) since Wed 2022-01-05 16:59:36 CST; 19min ago
Docs: https://docs.docker.com
Main PID: 97399 (dockerd)
Tasks: 0
Memory: 58.8M
CGroup: /system.slice/docker.service
├─97399 /usr/bin/dockerd
└─97412 containerd --config /var/run/docker/containerd/containerd.toml --log-level info
Jan 05 17:00:23 localhost.localdomain dockerd[97399]: time="2022-01-05T17:00:23.218537488+08:00" level=info msg="Attempting next endpoint for pull after error: Head \"https:/...ke timeout"
Jan 05 17:00:23 localhost.localdomain dockerd[97399]: time="2022-01-05T17:00:23.221555539+08:00" level=error msg="Handler for POST /v1.41/images/create returned error: Head \...ke timeout"
Jan 05 17:01:10 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:10.059479965+08:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/contain...d pid=98227
Jan 05 17:01:10 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:10.357324081+08:00" level=info msg="ignoring event" container=8149b29cadca1403bfe1df665f4a608bb01...TaskDelete"
Jan 05 17:01:10 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:10.359788730+08:00" level=info msg="shim disconnected" id=8149b29cadca1403bfe1df665f4a608bb0197e7...3141c638efd
Jan 05 17:01:10 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:10.359881885+08:00" level=error msg="copy shim log" error="read /proc/self/fd/14: file already closed"
Jan 05 17:01:17 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:17.341227632+08:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/contain...1 pid=98362
Jan 05 17:01:17 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:17.593448271+08:00" level=info msg="ignoring event" container=9a183ecff69e89963aa86351f53bb9d51d5...TaskDelete"
Jan 05 17:01:17 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:17.594207060+08:00" level=info msg="shim disconnected" id=9a183ecff69e89963aa86351f53bb9d51d5ca53...1fd409b3e11
Jan 05 17:01:17 localhost.localdomain dockerd[97399]: time="2022-01-05T17:01:17.594300540+08:00" level=error msg="copy shim log" error="read /proc/self/fd/14: file already closed"
Hint: Some lines were ellipsized, use -l to show in full.
二、安装metersphere
(1)离线安装metersphere
tail -zxvf metersphere-offline-installer-v1.15.4.tar.gz
cd metersphere-offline-installer-v1.15.4/
sudo sh install.sh
[root@localhost base]# tail -zxvf metersphere-offline-installer-v1.15.4.tar.gz
[root@localhost base]# cd metersphere-offline-installer-v1.15.4/
[root@localhost metersphere-offline-installer-v1.15.4]# sudo sh install.sh
存在已安装的 MeterSphere, 安装目录为 /opt/metersphere, 执行升级流程
[MeterSphere Log]: 拷贝安装文件到目标目录
‘./metersphere/docker-compose-kafka.yml’ -> ‘/opt/metersphere/docker-compose-kafka.yml’ (backup: ‘/opt/metersphere/docker-compose-kafka.yml.20220105-1719’)
‘./metersphere/docker-compose-prometheus.yml’ -> ‘/opt/metersphere/docker-compose-prometheus.yml’ (backup: ‘/opt/metersphere/docker-compose-prometheus.yml.20220105-1719’)
‘./metersphere/docker-compose-node-controller.yml’ -> ‘/opt/metersphere/docker-compose-node-controller.yml’ (backup: ‘/opt/metersphere/docker-compose-node-controller.yml.20220105-1719’)
‘./metersphere/docker-compose-mysql.yml’ -> ‘/opt/metersphere/docker-compose-mysql.yml’ (backup: ‘/opt/metersphere/docker-compose-mysql.yml.20220105-1719’)
‘./metersphere/conf/my.cnf’ -> ‘/opt/metersphere/conf/my.cnf’ (backup: ‘/opt/metersphere/conf/my.cnf.20220105-1719’)
‘./metersphere/conf/version’ -> ‘/opt/metersphere/conf/version’ (backup: ‘/opt/metersphere/conf/version.20220105-1719’)
‘./metersphere/conf/prometheus/prometheus.yml’ -> ‘/opt/metersphere/conf/prometheus/prometheus.yml’ (backup: ‘/opt/metersphere/conf/prometheus/prometheus.yml.20220105-1719’)
‘./metersphere/conf/metersphere.properties’ -> ‘/opt/metersphere/conf/metersphere.properties’ (backup: ‘/opt/metersphere/conf/metersphere.properties.20220105-1719’)
‘./metersphere/version’ -> ‘/opt/metersphere/version’ (backup: ‘/opt/metersphere/version.20220105-1719’)
‘./metersphere/docker-compose-base.yml’ -> ‘/opt/metersphere/docker-compose-base.yml’ (backup: ‘/opt/metersphere/docker-compose-base.yml.20220105-1719’)
‘./metersphere/docker-compose-server.yml’ -> ‘/opt/metersphere/docker-compose-server.yml’ (backup: ‘/opt/metersphere/docker-compose-server.yml.20220105-1719’)
‘./metersphere/logs/README.md’ -> ‘/opt/metersphere/logs/README.md’ (backup: ‘/opt/metersphere/logs/README.md.20220105-1719’)
[MeterSphere Log]: ======================= 开始安装 =======================
[MeterSphere Log]: 检测到 Docker 已安装，跳过安装步骤
[MeterSphere Log]: 启动 Docker
Redirecting to /bin/systemctl start docker.service
[MeterSphere Log]: 检测到 Docker Compose 已安装，跳过安装步骤
[MeterSphere Log]: 加载镜像
Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/jmeter-master:5.4.1-ms13-jdk8
Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/kafka:2
Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/metersphere:v1.15.4
Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/ms-data-streaming:v1.15.4
Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/ms-node-controller:v1.15.4
Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/mysql:5.7.33
Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/node-exporter:latest
Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/prometheus:latest
Loaded image: registry.cn-qingdao.aliyuncs.com/metersphere/zookeeper:3
[MeterSphere Log]: 启动服务
Removing network metersphere_ms-network
Network metersphere_ms-network not found.
Removing volume metersphere_ms-conf
Volume metersphere_ms-conf not found.
Removing volume metersphere_ms-logs
Volume metersphere_ms-logs not found.
Removing volume metersphere_ms-data
Volume metersphere_ms-data not found.
Removing volume metersphere_ms-mysql-data
Volume metersphere_ms-mysql-data not found.
Removing volume metersphere_ms-zookeeper-data
Volume metersphere_ms-zookeeper-data not found.
Removing volume metersphere_ms-kafka-data
Volume metersphere_ms-kafka-data not found.
Removing volume metersphere_ms-prometheus-data
Volume metersphere_ms-prometheus-data not found.
Removing volume metersphere_ms-prometheus-conf
Volume metersphere_ms-prometheus-conf not found.
Creating network "metersphere_ms-network" with driver "bridge"
Creating volume "metersphere_ms-conf" with default driver
Creating volume "metersphere_ms-logs" with default driver
Creating volume "metersphere_ms-data" with default driver
Creating volume "metersphere_ms-mysql-data" with default driver
Creating volume "metersphere_ms-zookeeper-data" with default driver
Creating volume "metersphere_ms-kafka-data" with default driver
Creating volume "metersphere_ms-prometheus-data" with default driver
Creating volume "metersphere_ms-prometheus-conf" with default driver
Creating zookeeper ... done
Creating mysql ... done
Creating ms-prometheus ... done
Creating ms-node-controller ... done
Creating kafka ... done
Creating nodeexporter ... done
Creating ms-server ... done
Creating ms-data-streaming ... done
Name Command State Ports
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
kafka /opt/bitnami/scripts/kafka ... Up (healthy) 0.0.0.0:19092->19092/tcp,:::19092->19092/tcp, 9092/tcp
ms-data-streaming /deployments/run-java.sh Up (health: starting)
ms-node-controller /deployments/run-java.sh Up (health: starting) 0.0.0.0:8082->8082/tcp,:::8082->8082/tcp, 0.0.0.0:9100->9100/tcp,:::9100->9100/tcp
ms-prometheus /bin/prometheus --config.f ... Up (healthy) 0.0.0.0:9090->9090/tcp,:::9090->9090/tcp
ms-server /deployments/run-java.sh Up (health: starting) 0.0.0.0:10000->10000/tcp,:::10000->10000/tcp, 0.0.0.0:10001->10001/tcp,:::10001->10001/tcp,
0.0.0.0:10002->10002/tcp,:::10002->10002/tcp, 0.0.0.0:10003->10003/tcp,:::10003->10003/tcp,
0.0.0.0:10004->10004/tcp,:::10004->10004/tcp, 0.0.0.0:10005->10005/tcp,:::10005->10005/tcp,
0.0.0.0:10006->10006/tcp,:::10006->10006/tcp, 0.0.0.0:10007->10007/tcp,:::10007->10007/tcp,
0.0.0.0:10008->10008/tcp,:::10008->10008/tcp, 0.0.0.0:10009->10009/tcp,:::10009->10009/tcp,
0.0.0.0:10010->10010/tcp,:::10010->10010/tcp, 0.0.0.0:8081->8081/tcp,:::8081->8081/tcp
mysql docker-entrypoint.sh mysqld Up (healthy) 0.0.0.0:3307->3306/tcp,:::3307->3306/tcp, 33060/tcp
nodeexporter /bin/node_exporter --path. ... Up (healthy)
zookeeper /opt/bitnami/scripts/zooke ... Up (healthy) 2181/tcp, 2888/tcp, 3888/tcp, 8080/tcp
======================= 安装完成 =======================
请通过以下方式访问:
URL: http://$LOCAL_IP:8081
用户名: admin
初始密码: metersphere
您可以使用命令 'msctl status' 检查服务运行情况.
（2）检查服务运行情况
sudo msctl status
[root@localhost metersphere-offline-installer-v1.15.4]# sudo msctl status
Name Command State Ports
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
kafka /opt/bitnami/scripts/kafka ... Up (healthy) 0.0.0.0:19092->19092/tcp,:::19092->19092/tcp, 9092/tcp
ms-data-streaming /deployments/run-java.sh Up (healthy)
ms-node-controller /deployments/run-java.sh Up (healthy) 0.0.0.0:8082->8082/tcp,:::8082->8082/tcp, 0.0.0.0:9100->9100/tcp,:::9100->9100/tcp
ms-prometheus /bin/prometheus --config.f ... Up (healthy) 0.0.0.0:9090->9090/tcp,:::9090->9090/tcp
ms-server /deployments/run-java.sh Up (health: starting) 0.0.0.0:10000->10000/tcp,:::10000->10000/tcp, 0.0.0.0:10001->10001/tcp,:::10001->10001/tcp,
0.0.0.0:10002->10002/tcp,:::10002->10002/tcp, 0.0.0.0:10003->10003/tcp,:::10003->10003/tcp,
0.0.0.0:10004->10004/tcp,:::10004->10004/tcp, 0.0.0.0:10005->10005/tcp,:::10005->10005/tcp,
0.0.0.0:10006->10006/tcp,:::10006->10006/tcp, 0.0.0.0:10007->10007/tcp,:::10007->10007/tcp,
0.0.0.0:10008->10008/tcp,:::10008->10008/tcp, 0.0.0.0:10009->10009/tcp,:::10009->10009/tcp,
0.0.0.0:10010->10010/tcp,:::10010->10010/tcp, 0.0.0.0:8081->8081/tcp,:::8081->8081/tcp
mysql docker-entrypoint.sh mysqld Up (healthy) 0.0.0.0:3307->3306/tcp,:::3307->3306/tcp, 33060/tcp
nodeexporter /bin/node_exporter --path. ... Up (healthy)
zookeeper /opt/bitnami/scripts/zooke ... Up (healthy) 2181/tcp, 2888/tcp, 3888/tcp, 8080/tcp
[root@localhost metersphere-offline-installer-v1.15.4]# netstat -antlpe | grep 8081
tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 0 282143 28166/docker-proxy
tcp6 0 0 :::8081 :::* LISTEN 0 282150 28171/docker-proxy
三、访问刚刚搭建的meterSphere
请通过以下方式访问:
URL: http://$LOCAL_IP:8081
（我这里用的是Linux的主机IP登录：http://192.168.182.128:8081/login）
使用ifconfig即可查到IP信息，[如果这里没显示IP，可以先执行：sudo dhclient ens33，再执行ifconfig]
ifconfig
[bonree@localhost ~]$ ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.182.128 netmask 255.255.255.0 broadcast 192.168.182.255
inet6 fe80::bccc:a8a0:6dd9:6969 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:ea:bc:d4 txqueuelen 1000 (Ethernet)
RX packets 2473629 bytes 3524726711 (3.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 352058 bytes 45140138 (43.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
用户名: admin
初始密码: metersphere
本文转自：https://blog.csdn.net/weixin_45072910/article/details/122329016
Linux上搭建meterSphere的更多相关文章
- linux上搭建ftp
linux上搭建ftp 重要 解决如何搭建ftp 解决用户指定访问其根目录 解决访问ftp超时连接 解决ftp主动连接.被动连接的问题 1.安装ftp ...
- 使用Nginx在windows和linux上搭建集群
Nginx Nginx (engine x) 是一个高性能的HTTP和反向代理服务器,也是一个IMAP/POP3/SMTP服务器 特点:反向代理 负载均衡 动静分离… 反向代理(Reverse Pro ...
- linux上搭建ftp、vsftp, 解决访问ftp超时连接, 解决用户指定访问其根目录,解决ftp主动连接、被动连接的问题
linux上搭建ftp 重要 解决如何搭建ftp 解决用户指定访问其根目录 解决访问ftp超时连接 解决ftp主动连接.被动连接的问题 1.安装ftp ...
- CentOS Linux上搭建PPPoE服务器及拨号设置
CentOS Linux上搭建PPPoE服务器及拨号设置 搭建PPPoE,成功了的话,就觉得超级简单,在CentOS Linux更是5步左右就能搞定. 1.安装pppoe,安装完成后,会有pppoe- ...
- 【转帖】Linux上搭建Samba,实现windows与Linux文件数据同步
Linux上搭建Samba,实现windows与Linux文件数据同步 2018年06月09日 :: m_nanle_xiaobudiu 阅读数 15812更多 分类专栏: Linux Samba 版 ...
- Linux上搭建SVN服务
环境:centos7 一.搭建svn服务 1. 安装svn yum -y install subversion 2. 创建一个目录作为svn服务的地址(svn://192.168.0.2:3690 访 ...
- mongo学习笔记（六）：linux上搭建
linux分以下几台 monogos mongocfg mongod1 mongod2 1.用ssh把 mongodb-linux-x86_64-3.0.6.tgz 移到linux /root上 2. ...
- linux上搭建nginx+php+mysql环境详细讲解
1.mysql安装 #安装编译环境 yum install -y gcc gcc-c++ gcc-devel g++ g++-devel; yum install -y wget yum instal ...
- Openfire+spark在linux上搭建内部聊天系统
一. 实验环境 Ubuntu server14.04 openfire:http://www.igniterealtime.org/downloads/index.jsp spark:http: ...
随机推荐
- docker | jenkins 实现自动化部署项目，后端躺着把运维的钱挣了！(上)
前言 背景 最近在帮学校导师写项目,团队有4个人,项目前后端分离.如果是选择瀑布式开发:(在约定好接口的情况下)A.B同学写前端,C.D同学写后端,然后约定一个时间统一联调,最后将项目交付安装到客户机 ...
- docker错误处理——docker Job for docker.service failed because the control process exited with error code.
(15条消息) docker Job for docker.service failed because the control process exited with error code._Hel ...
- Oracle用户创建、删除和授权等方法总结
一.查看用户及权限 1.查询所有用户: 1.1.查看所有用户基本信息 select * from all_users; 1.2.查看所有用户相信信息 select * from dba_users; ...
- 搭建 Nginx 服务
今日内容 上一篇测试 c出现问题 web 服务 部署 Nginx 内容详细 上一篇测试 NFS共享文件步骤 - 服务端 [root@backup ~]# yum install nfs-utils r ...
- Note - 千年食谱颂
其实是兔子收集的各种下饭操作与名菜食谱.( 零·策略篇 多校 NOIP 2021.11.05: 这个真的是,我每次打毛毛虫剖分都是 rush 状态 qwq.像这种 已知代码难度大.不便于调试的 ...
- Solution -「ARC 126E」Infinite Operations
\(\mathcal{Description}\) Link. 给定序列 \(\{a_n\}\),定义一次操作为: 选择 \(a_i<a_j\),以及一个 \(x\in\mathbb R ...
- LibOpenCM3(三) .ld文件(连接器脚本)和startup代码说明
目录 LibOpenCM3(一) Linux下命令行开发环境配置 LibOpenCM3(二) 项目模板 Makefile分析 LibOpenCM3(三) .ld文件(连接器脚本)和startup代码说 ...
- 【C# .Net GC】GC的类型与工作方式 和配置
.net主要有两种类型垃圾回收器,也可也说是垃圾回收器的两种工作模式. GC的类型主要有两种: 工作模式是针对进程的,程序启动后就不能修改了.只能在配置文件.json .xml进行设置.但是可用通过G ...
- 【硬件基础知识】指令集框架（ISA：Instruction Set Architecture）
指令框架(ISA:Instruction Set Architecture) 定义 指令集架构(英语:Instruction Set Architecture,缩写为ISA),又称指令集或指令集体系, ...
- CLR 详解
公共语言运行时就是按照CLI标准制作的执行托管代码的环境.CLR 能运行非托管代码. 公共语言运行的功能:代码JIT/AOT编译. 内存管理 .垃圾回收.异常处理.反射服务.安全服务.程序集加载.本 ...