当前位置: 开发笔记 > 编程语言 > 正文

TiDB部署文档

作者：妈妈的话CPC-8_645 | 来源：互联网 | 2023-08-29 15:30

文章目录

- 一、安装TiUP
- 二、TiDB部署

一、安装TiUP

使用普通用户登录中控机，以 tidb 用户为例，后续安装 TiUP 及集群管理操作均通过该用户完成：

1、执行如下命令安装 TiUP 工具：

curl --proto '=https' --tlsv1.2 -sSf https://tiup-mirrors.pingcap.com/install.sh | sh

2、按如下步骤设置 TiUP 环境变量：

重新声明全局环境变量：

source .bash_profile

确认 TiUP 工具是否安装：

which tiup

3、安装 TiUP cluster 组件

tiup cluster

如果已经安装，则更新 TiUP cluster 组件至最新版本：

tiup update --self && tiup update cluster

预期输出 “Update successfully!” 字样。

4、验证当前 TiUP cluster 版本信息。执行如下命令查看 TiUP cluster 组件版本：

[tidb@db01 ~]$ tiup --binary cluster /home/tidb/.tiup/components/cluster/v1.3.1/tiup-cluster

二、TiDB部署

1、编辑配置文件

# # Global variables are applied to all deployments and used as the default value of # # the deployments if a specific deployment value is missing. global: user: "tidb" ssh_port: 22 deploy_dir: "/tidb-deploy" data_dir: "/tidb-data" pd_servers: - host: 192.168.137.129 - host: 192.168.137.130 - host: 192.168.137.131 tidb_servers: - host: 192.168.137.129 - host: 192.168.137.130 - host: 192.168.137.131 tikv_servers: - host: 192.168.137.129 - host: 192.168.137.130 - host: 192.168.137.131 monitoring_servers: - host: 192.168.137.129 grafana_servers: - host: 192.168.137.129 alertmanager_servers: - host: 192.168.137.129

2、安装TiDB

通过 TiUP 进行集群部署可以使用密钥或者交互密码方式来进行安全认证：

如果是密钥方式，可以通过 -i 或者 --identity_file 来指定密钥的路径；
如果是密码方式，可以通过 -p 进入密码交互窗口；
如果已经配置免密登陆目标机，则不需填写认证。

一般情况下 TiUP 会在目标机器上创建 topology.yaml 中约定的用户和组，以下情况例外：

topology.yaml 中设置的用户名在目标机器上已存在。
在命令行上使用了参数 --skip-create-user 明确指定跳过创建用户的步骤。

[tidb@db01 ~]$ tiup cluster deploy tidb-test v4.0.0 ./topology.yaml --user root -p Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.3.1/tiup-cluster deploy tidb-test v4.0.0 ./topology.yaml --user root -p Please confirm your topology: Cluster type: tidb Cluster name: tidb-test Cluster version: v4.0.0 Type Host Ports OS/Arch Directories ---- ---- ----- ------- ----------- pd 192.168.137.129 2379/2380 linux/x86_64 /tidb-deploy/pd-2379,/tidb-data/pd-2379 pd 192.168.137.130 2379/2380 linux/x86_64 /tidb-deploy/pd-2379,/tidb-data/pd-2379 pd 192.168.137.131 2379/2380 linux/x86_64 /tidb-deploy/pd-2379,/tidb-data/pd-2379 tikv 192.168.137.129 20160/20180 linux/x86_64 /tidb-deploy/tikv-20160,/tidb-data/tikv-20160 tikv 192.168.137.130 20160/20180 linux/x86_64 /tidb-deploy/tikv-20160,/tidb-data/tikv-20160 tikv 192.168.137.131 20160/20180 linux/x86_64 /tidb-deploy/tikv-20160,/tidb-data/tikv-20160 tidb 192.168.137.129 4000/10080 linux/x86_64 /tidb-deploy/tidb-4000 tidb 192.168.137.130 4000/10080 linux/x86_64 /tidb-deploy/tidb-4000 tidb 192.168.137.131 4000/10080 linux/x86_64 /tidb-deploy/tidb-4000 prometheus 192.168.137.129 9090 linux/x86_64 /tidb-deploy/prometheus-9090,/tidb-data/prometheus-9090 grafana 192.168.137.129 3000 linux/x86_64 /tidb-deploy/grafana-3000 alertmanager 192.168.137.129 9093/9094 linux/x86_64 /tidb-deploy/alertmanager-9093,/tidb-data/alertmanager-9093 Attention: 1. If the topology is not what you expected, check your yaml file. 2. Please confirm there is no port/directory conflicts in same host. Do you want to continue? [y/N]: y Input SSH password: + Generate SSH keys ... Done + Download TiDB components - Download pd:v4.0.0 (linux/amd64) ... Done - Download tikv:v4.0.0 (linux/amd64) ... Done - Download tidb:v4.0.0 (linux/amd64) ... Done - Download prometheus:v4.0.0 (linux/amd64) ... Done - Download grafana:v4.0.0 (linux/amd64) ... Done - Download alertmanager:v0.17.0 (linux/amd64) ... Done - Download node_exporter:v0.17.0 (linux/amd64) ... Done - Download blackbox_exporter:v0.12.0 (linux/amd64) ... Done + Initialize target host environments - Prepare 192.168.137.129:22 ... Done - Prepare 192.168.137.130:22 ... Done - Prepare 192.168.137.131:22 ... Done + Copy files - Copy pd -> 192.168.137.129 ... Done - Copy pd -> 192.168.137.130 ... Done - Copy pd -> 192.168.137.131 ... Done - Copy tikv -> 192.168.137.129 ... Done - Copy tikv -> 192.168.137.130 ... Done - Copy tikv -> 192.168.137.131 ... Done - Copy tidb -> 192.168.137.129 ... Done - Copy tidb -> 192.168.137.130 ... Done - Copy tidb -> 192.168.137.131 ... Done - Copy prometheus -> 192.168.137.129 ... Done - Copy grafana -> 192.168.137.129 ... Done - Copy alertmanager -> 192.168.137.129 ... Done - Copy node_exporter -> 192.168.137.130 ... Done - Copy node_exporter -> 192.168.137.131 ... Done - Copy node_exporter -> 192.168.137.129 ... Done - Copy blackbox_exporter -> 192.168.137.129 ... Done - Copy blackbox_exporter -> 192.168.137.130 ... Done - Copy blackbox_exporter -> 192.168.137.131 ... Done + Check status Enabling component pd Enabling instance pd 192.168.137.131:2379 Enabling instance pd 192.168.137.129:2379 Enabling instance pd 192.168.137.130:2379 Enable pd 192.168.137.131:2379 success Enable pd 192.168.137.129:2379 success Enable pd 192.168.137.130:2379 success Enabling component node_exporter Enabling component blackbox_exporter Enabling component node_exporter Enabling component blackbox_exporter Enabling component node_exporter Enabling component blackbox_exporter Enabling component tikv Enabling instance tikv 192.168.137.131:20160 Enabling instance tikv 192.168.137.129:20160 Enabling instance tikv 192.168.137.130:20160 Enable tikv 192.168.137.129:20160 success Enable tikv 192.168.137.131:20160 success Enable tikv 192.168.137.130:20160 success Enabling component tidb Enabling instance tidb 192.168.137.131:4000 Enabling instance tidb 192.168.137.129:4000 Enabling instance tidb 192.168.137.130:4000 Enable tidb 192.168.137.129:4000 success Enable tidb 192.168.137.131:4000 success Enable tidb 192.168.137.130:4000 success Enabling component prometheus Enabling instance prometheus 192.168.137.129:9090 Enable prometheus 192.168.137.129:9090 success Enabling component grafana Enabling instance grafana 192.168.137.129:3000 Enable grafana 192.168.137.129:3000 success Enabling component alertmanager Enabling instance alertmanager 192.168.137.129:9093 Enable alertmanager 192.168.137.129:9093 success Cluster `tidb-test` deployed successfully, you can start it with command: `tiup cluster start tidb-test`

TiUP 支持管理多个 TiDB 集群，该命令会输出当前通过 TiUP cluster 管理的所有集群信息，包括集群名称、部署用户、版本、密钥信息等：

[tidb@db01 ~]$ tiup cluster list Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.3.1/tiup-cluster list Name User Version Path PrivateKey ---- ---- ------- ---- ---------- tidb-test tidb v4.0.0 /home/tidb/.tiup/storage/cluster/clusters/tidb-test /home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa

执行如下命令检查 tidb-test 集群情况，预期输出包括 tidb-test 集群中实例 ID、角色、主机、监听端口和状态（由于还未启动，所以状态为 Down/inactive）、目录信息：

[tidb@db01 ~]$ tiup cluster display tidb-test Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.3.1/tiup-cluster display tidb-test Cluster type: tidb Cluster name: tidb-test Cluster version: v4.0.0 SSH type: builtin ID Role Host Ports OS/Arch Status Data Dir Deploy Dir -- ---- ---- ----- ------- ------ -------- ---------- 192.168.137.129:9093 alertmanager 192.168.137.129 9093/9094 linux/x86_64 inactive /tidb-data/alertmanager-9093 /tidb-deploy/alertmanager-9093 192.168.137.129:3000 grafana 192.168.137.129 3000 linux/x86_64 inactive - /tidb-deploy/grafana-3000 192.168.137.129:2379 pd 192.168.137.129 2379/2380 linux/x86_64 Down /tidb-data/pd-2379 /tidb-deploy/pd-2379 192.168.137.130:2379 pd 192.168.137.130 2379/2380 linux/x86_64 Down /tidb-data/pd-2379 /tidb-deploy/pd-2379 192.168.137.131:2379 pd 192.168.137.131 2379/2380 linux/x86_64 Down /tidb-data/pd-2379 /tidb-deploy/pd-2379 192.168.137.129:9090 prometheus 192.168.137.129 9090 linux/x86_64 inactive /tidb-data/prometheus-9090 /tidb-deploy/prometheus-9090 192.168.137.129:4000 tidb 192.168.137.129 4000/10080 linux/x86_64 Down - /tidb-deploy/tidb-4000 192.168.137.130:4000 tidb 192.168.137.130 4000/10080 linux/x86_64 Down - /tidb-deploy/tidb-4000 192.168.137.131:4000 tidb 192.168.137.131 4000/10080 linux/x86_64 Down - /tidb-deploy/tidb-4000 192.168.137.129:20160 tikv 192.168.137.129 20160/20180 linux/x86_64 N/A /tidb-data/tikv-20160 /tidb-deploy/tikv-20160 192.168.137.130:20160 tikv 192.168.137.130 20160/20180 linux/x86_64 N/A /tidb-data/tikv-20160 /tidb-deploy/tikv-20160 192.168.137.131:20160 tikv 192.168.137.131 20160/20180 linux/x86_64 N/A /tidb-data/tikv-20160 /tidb-deploy/tikv-20160

预期结果输出 Started cluster tidb-test successfully 标志启动成功。

[tidb@db01 ~]$ tiup cluster start tidb-test Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.3.1/tiup-cluster start tidb-test Starting cluster tidb-test... + [ Serial ] - SSHKeySet: privateKey=/home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa, publicKey=/home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa.pub + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.131 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.130 + [Parallel] - UserSSH: user=tidb, host=192.168.137.130 + [Parallel] - UserSSH: user=tidb, host=192.168.137.131 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.131 + [Parallel] - UserSSH: user=tidb, host=192.168.137.130 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [ Serial ] - StartCluster Starting component pd Starting instance pd 192.168.137.131:2379 Starting instance pd 192.168.137.129:2379 Starting instance pd 192.168.137.130:2379 Start pd 192.168.137.131:2379 success Start pd 192.168.137.129:2379 success Start pd 192.168.137.130:2379 success Starting component node_exporter Starting instance 192.168.137.129 Start 192.168.137.129 success Starting component blackbox_exporter Starting instance 192.168.137.129 Start 192.168.137.129 success Starting component node_exporter Starting instance 192.168.137.130 Start 192.168.137.130 success Starting component blackbox_exporter Starting instance 192.168.137.130 Start 192.168.137.130 success Starting component node_exporter Starting instance 192.168.137.131 Start 192.168.137.131 success Starting component blackbox_exporter Starting instance 192.168.137.131 Start 192.168.137.131 success Starting component tikv Starting instance tikv 192.168.137.131:20160 Starting instance tikv 192.168.137.129:20160 Starting instance tikv 192.168.137.130:20160 Start tikv 192.168.137.131:20160 success Start tikv 192.168.137.129:20160 success Start tikv 192.168.137.130:20160 success Starting component tidb Starting instance tidb 192.168.137.131:4000 Starting instance tidb 192.168.137.129:4000 Starting instance tidb 192.168.137.130:4000 Start tidb 192.168.137.129:4000 success Start tidb 192.168.137.131:4000 success Start tidb 192.168.137.130:4000 success Starting component prometheus Starting instance prometheus 192.168.137.129:9090 Start prometheus 192.168.137.129:9090 success Starting component grafana Starting instance grafana 192.168.137.129:3000 Start grafana 192.168.137.129:3000 success Starting component alertmanager Starting instance alertmanager 192.168.137.129:9093 Start alertmanager 192.168.137.129:9093 success + [ Serial ] - UpdateTopology: cluster=tidb-test Started cluster `tidb-test` successfully

通过 TiUP 检查集群状态，预期结果输出，注意 Status 状态信息为 Up 说明集群状态正常

[tidb@db01 ~]$ tiup cluster display tidb-test Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.3.1/tiup-cluster display tidb-test Cluster type: tidb Cluster name: tidb-test Cluster version: v4.0.0 SSH type: builtin Dashboard URL: http://192.168.137.131:2379/dashboard ID Role Host Ports OS/Arch Status Data Dir Deploy Dir -- ---- ---- ----- ------- ------ -------- ---------- 192.168.137.129:9093 alertmanager 192.168.137.129 9093/9094 linux/x86_64 Up /tidb-data/alertmanager-9093 /tidb-deploy/alertmanager-9093 192.168.137.129:3000 grafana 192.168.137.129 3000 linux/x86_64 Up - /tidb-deploy/grafana-3000 192.168.137.129:2379 pd 192.168.137.129 2379/2380 linux/x86_64 Up|L /tidb-data/pd-2379 /tidb-deploy/pd-2379 192.168.137.130:2379 pd 192.168.137.130 2379/2380 linux/x86_64 Up /tidb-data/pd-2379 /tidb-deploy/pd-2379 192.168.137.131:2379 pd 192.168.137.131 2379/2380 linux/x86_64 Up|UI /tidb-data/pd-2379 /tidb-deploy/pd-2379 192.168.137.129:9090 prometheus 192.168.137.129 9090 linux/x86_64 Up /tidb-data/prometheus-9090 /tidb-deploy/prometheus-9090 192.168.137.129:4000 tidb 192.168.137.129 4000/10080 linux/x86_64 Up - /tidb-deploy/tidb-4000 192.168.137.130:4000 tidb 192.168.137.130 4000/10080 linux/x86_64 Up - /tidb-deploy/tidb-4000 192.168.137.131:4000 tidb 192.168.137.131 4000/10080 linux/x86_64 Up - /tidb-deploy/tidb-4000 192.168.137.129:20160 tikv 192.168.137.129 20160/20180 linux/x86_64 Up /tidb-data/tikv-20160 /tidb-deploy/tikv-20160 192.168.137.130:20160 tikv 192.168.137.130 20160/20180 linux/x86_64 Up /tidb-data/tikv-20160 /tidb-deploy/tikv-20160 192.168.137.131:20160 tikv 192.168.137.131 20160/20180 linux/x86_64 Up /tidb-data/tikv-20160 /tidb-deploy/tikv-20160 Total nodes: 12

连接TiDB

[tidb@db01 ~]$ mysql -u root -h 192.168.137.129 -P 4000 Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 Server version: 5.7.25-TiDB-v4.0.0 TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. root@mysql 19:51: [(none)]> show databases; +--------------------+ | Database | +--------------------+ | INFORMATION_SCHEMA | | METRICS_SCHEMA | | PERFORMANCE_SCHEMA | | mysql | | test | +--------------------+ 5 rows in set (0.00 sec) root@mysql 19:51: [(none)]> use test; Database changed root@mysql 19:51: [test]> show tables; Empty set (0.00 sec) root@mysql 19:51: [test]> select user,host from mysql.user; +------+------+ | user | host | +------+------+ | root | % | +------+------+ 1 row in set (0.00 sec) root@mysql 19:51: [test]> ^DBye

停止TiDB

[tidb@db01 ~]$ tiup cluster stop tidb-test Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.3.1/tiup-cluster stop tidb-test + [ Serial ] - SSHKeySet: privateKey=/home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa, publicKey=/home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa.pub + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.131 + [Parallel] - UserSSH: user=tidb, host=192.168.137.130 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.131 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.130 + [Parallel] - UserSSH: user=tidb, host=192.168.137.129 + [Parallel] - UserSSH: user=tidb, host=192.168.137.131 + [Parallel] - UserSSH: user=tidb, host=192.168.137.130 + [ Serial ] - StopCluster Stopping component alertmanager Stopping instance 192.168.137.129 Stop alertmanager 192.168.137.129:9093 success Stopping component grafana Stopping instance 192.168.137.129 Stop grafana 192.168.137.129:3000 success Stopping component prometheus Stopping instance 192.168.137.129 Stop prometheus 192.168.137.129:9090 success Stopping component tidb Stopping instance 192.168.137.131 Stopping instance 192.168.137.129 Stopping instance 192.168.137.130 Stop tidb 192.168.137.129:4000 success Stop tidb 192.168.137.131:4000 success Stop tidb 192.168.137.130:4000 success Stopping component tikv Stopping instance 192.168.137.131 Stopping instance 192.168.137.129 Stopping instance 192.168.137.130 Stop tikv 192.168.137.129:20160 success Stop tikv 192.168.137.130:20160 success Stop tikv 192.168.137.131:20160 success Stopping component pd Stopping instance 192.168.137.131 Stopping instance 192.168.137.129 Stopping instance 192.168.137.130 Stop pd 192.168.137.129:2379 success Stop pd 192.168.137.130:2379 success Stop pd 192.168.137.131:2379 success Stopping component node_exporter Stopping component blackbox_exporter Stopping component node_exporter Stopping component blackbox_exporter Stopping component node_exporter Stopping component blackbox_exporter Stopped cluster `tidb-test` successfully

原文链接：https://blog.csdn.net/qq_42979842/article/details/112849430

推荐阅读

io
基于KVM的SRIOV直通配置及性能测试

SRIOV介绍、VF直通配置，以及包转发率性能测试小慢哥的原创文章，欢迎转载目录?1.SRIOV介绍?2.环境说明?3.开启SRIOV?4.生成VF?5.VF ... [详细]

蜡笔小新 2024-12-25 19:26:39
io
Linux 透明防火墙（网桥模式）的部署与配置

本文介绍如何在现有网络中部署基于Linux系统的透明防火墙（网桥模式），以实现灵活的时间段控制、流量限制等功能。通过详细的步骤和配置说明，确保内部网络的安全性和稳定性。 ... [详细]

蜡笔小新 2024-12-25 13:17:38
get
告别传统文件传输，迎接新一代高效工具Croc

在现代网络环境中，两台计算机之间的文件传输需求日益增长。传统的FTP和SSH方式虽然有效，但其配置复杂、步骤繁琐，难以满足快速且安全的传输需求。本文将介绍一种基于Go语言开发的新一代文件传输工具——Croc，它不仅简化了操作流程，还提供了强大的加密和跨平台支持。 ... [详细]

蜡笔小新 2024-12-26 16:16:06
copy
使用SSH密钥对实现Linux系统免密码登录

本文详细介绍如何在Linux系统中配置SSH密钥对，以实现从一台主机到另一台主机的无密码登录。内容涵盖密钥对生成、公钥分发及权限设置等关键步骤。 ... [详细]

蜡笔小新 2024-12-23 16:17:45
io
DNN Community 和 Professional 版本的主要差异

本文详细解析了 DotNetNuke (DNN) 的两种主要版本：Community 和 Professional。通过对比两者的功能和附加组件，帮助用户选择最适合其需求的版本。 ... [详细]

蜡笔小新 2024-12-27 13:14:08
io
Linux 网卡绑定的七种工作模式详解

本文深入探讨了Linux系统中网卡绑定（bonding）的七种工作模式。网卡绑定技术通过将多个物理网卡组合成一个逻辑网卡，实现网络冗余、带宽聚合和负载均衡，在生产环境中广泛应用。文章详细介绍了每种模式的特点、适用场景及配置方法。 ... [详细]

蜡笔小新 2024-12-27 10:18:13
io
MySQL 数据库迁移指南：从本地到远程及磁盘间迁移

本文详细介绍了如何在不同场景下进行 MySQL 数据库的迁移，包括从一个硬盘迁移到另一个硬盘、从一台计算机迁移到另一台计算机，以及解决迁移过程中可能遇到的问题。 ... [详细]

蜡笔小新 2024-12-26 13:21:38
io
2023年全球运营商网络设备市场预计突破202亿美元

尽管某些细分市场如WAN优化表现不佳，但全球运营商路由器和交换机市场持续增长。根据最新研究，该市场预计在2023年达到202亿美元的规模。 ... [详细]

蜡笔小新 2024-12-27 12:44:44
copy
从 .NET 转 Java 的自学之路：IO 流基础篇

本文详细介绍了 Java 中的 IO 流，包括字节流和字符流的基本概念及其操作方式。探讨了如何处理不同类型的文件数据，并结合编码机制确保字符数据的正确读写。同时，文中还涵盖了装饰设计模式的应用，以及多种常见的 IO 操作实例。 ... [详细]

蜡笔小新 2024-12-26 17:37:25
php
使用Xshell通过SSH协议远程连接Ubuntu系统

本文介绍如何通过SSH协议使用Xshell远程连接到Ubuntu系统。为了实现这一目标，需要确保Ubuntu系统已安装并配置好SSH服务器，并保证网络连通性。 ... [详细]

蜡笔小新 2024-12-25 16:29:11
chat
深入解析 Spring Security 用户认证机制

本文将详细介绍 Spring Security 中用户登录认证的核心流程，重点分析 AbstractAuthenticationProcessingFilter 和 AuthenticationManager 的工作原理。通过理解这些组件的实现，读者可以更好地掌握 Spring Security 的认证机制。 ... [详细]

蜡笔小新 2024-12-25 16:00:21
io
优化局域网SSH连接延迟问题的解决方案

本文介绍了解决局域网内SSH连接到服务器时出现长时间等待问题的方法。通过调整配置和优化网络设置，可以显著缩短SSH连接的时间。 ... [详细]

蜡笔小新 2024-12-25 11:31:48
io
配置多VLAN环境下的透明SQUID代理

本文介绍如何在包含多个VLAN的网络环境中配置SQUID作为透明网关。网络拓扑包括Cisco 3750交换机、PANABIT防火墙和SQUID服务器，所有设备均部署在ESXi虚拟化平台上。 ... [详细]

蜡笔小新 2024-12-23 14:57:39
copy
Python——对象自省

对象自省自省在计算机编程领域里，是指在运行时判断一个对象的类型和能力。dir能够返回一个列表，列举了一个对象所拥有的属性和方法。my_list[ ... [详细]

蜡笔小新 2024-12-23 12:55:35
copy
利用MySQL弱口令获取系统权限的实战案例

本文详细介绍了一种通过MySQL弱口令漏洞在Windows操作系统上获取SYSTEM权限的方法。该方法涉及使用自定义UDF DLL文件来执行任意命令，从而实现对远程服务器的完全控制。 ... [详细]

蜡笔小新 2024-12-21 18:17:57

妈妈的话CPC-8_645

这个家伙很懒，什么也没留下！

Tags | 热门标签

RankList | 热门文章