Elasticsearch-8.17.0 centos7安装

下载链接
https://www.elastic.co/downloads/past-releases/elasticsearch-8-17-0
https://www.elastic.co/downloads/past-releases/logstash-8-17-0
https://www.elastic.co/cn/downloads/past-releases/kibana-8-17-0https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-8.17.0-linux-x86_64.tar.gz
https://artifacts.elastic.co/downloads/logstash/logstash-8.17.0-linux-x86_64.tar.gz
https://artifacts.elastic.co/downloads/kibana/kibana-8.17.0-linux-x86_64.tar.gz1、上传下载的安装包到指定机器上,然后做准备工作1)编辑 /etc/security/limits.conf 文件,添加以下行:星号(*)代表对所有用户应用该限制
*          soft    nofile      65535
*          hard    nofile      65535
2)编辑/etc/pam.d/login
加在最后
session required pam_limits.so3)vi /etc/sysctl.conf
添加或修改以下行:
vm.max_map_count=262144运行以下命令以使配置立即生效:
sudo sysctl -p然后重启电脑2、解压和改名
进入到软件的目录
/usr/local/software执行如下2条命令
tar -xzf elasticsearch-8.17.0-linux-x86_64.tar.gz
mv elasticsearch-8.17.0  elasticsearch3、运行
cd /usr/local/software/elasticsearch/bin
[root@localhost bin]# ./elasticsearch遇到错误,不能以 root 用户身份运行 Elasticsearch
fatal exception while booting Elasticsearch java.lang.RuntimeException: can not run elasticsearch as root
这个错误的含义是 不能以 root 用户身份运行 Elasticsearch。为了安全性和权限问题4、创建data目录
在/usr/local/software/elasticsearch目录下mkdir data5、新建用户和授权
useradd elasticsearchchown -R elasticsearch:elasticsearch /usr/local/software/elasticsearch
chown -R elasticsearch:elasticsearch /usr/local/software/elasticsearch/datachown -R elasticsearch:elasticsearch /usr/local/software/elasticsearch/logs/
chmod -R 755 /usr/local/software/elasticsearch/logs/6、删除elasticsearch.keystore[root@localhost config]# rm elasticsearch.keystore
rm: remove regular file ‘elasticsearch.keystore’? y7、修改elasticsearch.yml cd /usr/local/software/elasticsearch/configvi /usr/local/software/elasticsearch/config/elasticsearch.yml备份下
cp elasticsearch.yml  elasticsearch_bak.yml修改
vi elasticsearch.ymldiscovery.seed_hosts: ["127.0.0.1:9300"]
cluster.initial_master_nodes: ["localhost"]xpack.security.enabled: false
xpack.security.enrollment.enabled: truehttp.host: 0.0.0.0transport.host: 0.0.0.0修改elasticsearch的堆内存
cd /usr/local/software/elasticsearch/config/jvm.options.d/
没有文件就创建一个
touch heap-size.options
-Xms2g
-Xmx2g下面   Memory: 2.6G就是证明改变更了[root@localhost ~]# systemctl status elasticsearch
● elasticsearch.service - ElasticsearchLoaded: loaded (/etc/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)Active: active (running) since Tue 2024-12-31 16:00:36 CST; 1min 46s agoDocs: http://www.elastic.coMain PID: 992 (java)Tasks: 87Memory: 2.6G8 切换到 elasticsearch 用户
sudo su - elasticsearch9 以 elasticsearch 用户身份启动 Elasticsearch
在 elasticsearch 用户下,进入到 Elasticsearch 安装目录并启动服务:cd /usr/local/software/elasticsearch/bin
./elasticsearch -d-d代表后台启动10 访问http://192.168.150.50:9200/, 如果不能访问再往下看或者文腾讯的AI,https://cat.aichatos8.com.cn/#/home
{"name" : "localhost.localdomain","cluster_name" : "elasticsearch","cluster_uuid" : "udrBoGSRRwal_hpQ7ocUlQ","version" : {"number" : "8.17.0","build_flavor" : "default","build_type" : "tar","build_hash" : "2b6a7fed44faa321997703718f07ee0420804b41","build_date" : "2024-12-11T12:08:05.663969764Z","build_snapshot" : false,"lucene_version" : "9.12.0","minimum_wire_compatibility_version" : "7.17.0","minimum_index_compatibility_version" : "7.0.0"},"tagline" : "You Know, for Search"
}11 创建服务 vi /etc/systemd/system/elasticsearch.service
文件内容如下:[Unit]
Description=Elasticsearch
Documentation=http://www.elastic.co
After=network.target[Service]
Type=simple
ExecStart=/usr/local/software/elasticsearch/bin/elasticsearch
User=elasticsearch
Group=elasticsearch
Restart=always
LimitMEMLOCK=infinity
LimitNOFILE=65536
LimitNPROC=4096[Install]
WantedBy=multi-user.target替换 /path/to/elasticsearch-8.17.0 为实际路径。12 开机启动
systemctl daemon-reload
systemctl enable elasticsearch
systemctl start elasticsearch
systemctl status elasticsearchelasticsearch.yml
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
#       Before you set out to tweak and tune the configuration, make sure you
#       understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
#path.data: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
#network.host: 192.168.0.1
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
#http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.seed_hosts: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
discovery.seed_hosts: ["127.0.0.1:9300"]
cluster.initial_master_nodes: ["localhost"]
# ---------------------------------- Various -----------------------------------
#
# Allow wildcard deletion of indices:
#
#action.destructive_requires_name: false#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically      
# generated to configure Elasticsearch security features on 30-12-2024 12:29:02
#
# --------------------------------------------------------------------------------# Enable security features
xpack.security.enabled: false
xpack.security.enrollment.enabled: true# Allow HTTP API connections from anywhere
# Connections are encrypted and require user authentication
http.host: 0.0.0.0# Allow other nodes to join the cluster from anywhere
# Connections are encrypted and mutually authenticated
transport.host: 0.0.0.0#----------------------- END SECURITY AUTO CONFIGURATION -------------------------
==============================安装遇到的具体问题分析==================运行后Elasticsearch security features have been automatically configured!
✅ Authentication is enabled and cluster connections are encrypted.ℹ️  Password for the elastic user (reset with `bin/elasticsearch-reset-password -u elastic`):7b9UkBY*NeEH3_ea85JGℹ️  HTTP CA certificate SHA-256 fingerprint:d7a127636d720f927127c4f974f806f512eae01dd8b85af21be192dd5bbb3c3cℹ️  Configure Kibana to use this cluster:
• Run Kibana and click the configuration link in the terminal when Kibana starts.
• Copy the following enrollment token and paste it into Kibana in your browser (valid for the next 30 minutes):eyJ2ZXIiOiI4LjE0LjAiLCJhZHIiOlsiMTkyLjE2OC4xNTAuNTA6OTIwMCJdLCJmZ3IiOiJkN2ExMjc2MzZkNzIwZjkyNzEyN2M0Zjk3NGY4MDZmNTEyZWFlMDFkZDhiODVhZjIxYmUxOTJkZDViYmIzYzNjIiwia2V5IjoiYVR5VkY1UUJWLTBzb19zV0UzT246UkhSangyMFRReWl1ZzZPeUtWSVJIQSJ9ℹ️  Configure other nodes to join this cluster:
• On this node:⁃ Create an enrollment token with `bin/elasticsearch-create-enrollment-token -s node`.⁃ Uncomment the transport.host setting at the end of config/elasticsearch.yml.⁃ Restart Elasticsearch.
• On other nodes:⁃ Start Elasticsearch with `bin/elasticsearch --enrollment-token <token>`, using the enrollment token that you generated.重要信息:
elastic user 的密码是 7b9UkBY*NeEH3_ea85JG
重置密码的命令 bin/elasticsearch-reset-password -u elastic使用:bin/elasticsearch-create-enrollment-token -s node创建一个token, 但这个还用不上"取消对config/exelasticsearch.yml末尾transport.host设置的注释。重新启动Elasticsearch。8、修改elasticsearch.yml cd /usr/local/software/elasticsearch/config备份下
cp elasticsearch.yml  elasticsearch_bak.yml修改
vi elasticsearch.yml把它的注释去掉,然后保存重启。
transport.host: 0.0.0.0[2024-12-30T21:00:35,801][ERROR][o.e.b.Elasticsearch      ] [localhost.localdomain] node validation exception
[2] bootstrap checks failed. You must address the points described in the following [2] lines before starting Elasticsearch. For more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.17/bootstrap-checks.html]
bootstrap check failure [1] of [2]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]; for more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.17/bootstrap-checks-file-descriptor.html]
bootstrap check failure [2] of [2]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]; for more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.17/bootstrap-checks-max-map-count.html]
ERROR: 这个错误信息说明 Elasticsearch 在启动时执行了 bootstrap checks(启动检查),并且未通过两个关键的检查。具体来说,出现了以下两个问题:错误信息解析:
max file descriptors 设置过低错误信息:[bootstrap check failure [1] of [2]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65535]]
解释:Elasticsearch 需要较高的文件描述符限制,因为它会同时打开很多文件(例如索引文件、日志文件等)。默认情况下,操作系统可能只允许最多 4096 个文件描述符,而 Elasticsearch 要求至少 65535 个。
vm.max_map_count 设置过低错误信息:[bootstrap check failure [2] of [2]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]]
解释:vm.max_map_count 是操作系统设置的最大虚拟内存区域数(用于内存映射文件)。Elasticsearch 需要更高的这个值,特别是在处理大数据量时。默认值可能较低(如 65530),而 Elasticsearch 要求至少 262144。
如何解决这些问题:
1. 增加 max file descriptors 限制
你需要增加操作系统中可打开文件的最大数量。方法如下:查看当前设置:bash
ulimit -n
如果显示的数字小于 65535,你需要增加它。临时修改(只对当前会话有效):bash
ulimit -n 65535
永久修改(适用于 Linux):编辑 /etc/security/limits.conf 文件,添加以下行:星号(*)代表对所有用户应用该限制
*          soft    nofile      65535
*          hard    nofile      65535如果你知道运行 Elasticsearch 的用户(例如 elasticsearch 用户),你可以替换星号为该用户名:elasticsearch soft nofile 65535
elasticsearch hard nofile 65535还需要修改 /etc/pam.d/common-session 或 /etc/pam.d/login 文件(具体路径取决于发行版),并添加以下行:
centos7 用这个/etc/pam.d/login
加在最后
session required pam_limits.so
最后,重新启动机器或注销当前会话后生效。2. 增加 vm.max_map_count 限制
vm.max_map_count 控制了每个进程可以映射的最大虚拟内存区域数量。需要将其增加到至少 262144:临时修改:
bash
sudo sysctl -w vm.max_map_count=262144永久修改:
编辑 /etc/sysctl.conf 文件:bash
sudo vi /etc/sysctl.conf
添加或修改以下行:bash
vm.max_map_count=262144
运行以下命令以使配置立即生效:bash
sudo sysctl -p
3. 重启 Elasticsearch
完成上述设置后,重启 Elasticsearch:bash
sudo systemctl restart elasticsearch
或者如果你是手动启动 Elasticsearch,则执行:bash
./bin/elasticsearch
总结:
max file descriptors 的问题:增加文件描述符的限制到 65535。
vm.max_map_count 的问题:增加虚拟内存映射区域的限制到 262144。
完成配置后重启 Elasticsearch,应该能够顺利启动。如果还有其他问题,或者配置后仍然无法启动,可以查看 Elasticsearch 的日志(/usr/local/software/elasticsearch/logs/elasticsearch.log)来获取更多详细的错误信息。启动说没权限,继续修改目录权限
如果 Elasticsearch 进程没有足够的权限来写入该目录,你可以更改该目录的权限,使得 Elasticsearch 有权访问它。假设 Elasticsearch 是以 elasticsearch 用户运行的,你可以执行以下命令来修复权限。给目录赋予适当的权限:bash
sudo chown -R elasticsearch:elasticsearch /usr/local/software/elasticsearch/logs/
这条命令将目录的所有权授予 elasticsearch 用户和组。确保目录具有正确的读写权限:bash
sudo chmod -R 755 /usr/local/software/elasticsearch/logs/
这样,目录将具有所有者的读、写和执行权限,其他用户只有读和执行权限。3. 检查日志文件权限
同样需要确保日志文件本身(elasticsearch.log)的权限设置正确。执行以下命令来检查日志文件的权限:查看日志文件的权限:ls -l /usr/local/software/elasticsearch/logs/elasticsearch.log删除elasticsearch.keystore[root@localhost config]# rm elasticsearch.keystore
rm: remove regular file ‘elasticsearch.keystore’? y从你提供的日志信息来看,Elasticsearch 在启动时遇到了 bootstrap 检查失败,并且因为 缺少配置 导致启动失败。错误消息中指出了如下问题:错误描述
bootstrap check failure [1] of [1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured;
这意味着 Elasticsearch 发现你没有配置必要的发现设置,这是在生产环境中启动集群时的强制要求。具体来说,Elasticsearch 需要知道如何找到集群的节点和确定主节点。解决办法
编辑 Elasticsearch 配置文件Elasticsearch 的配置文件 elasticsearch.yml 存在于你的 Elasticsearch 安装目录下的 config 目录中,例如:/usr/local/software/elasticsearch/config/elasticsearch.yml。添加 Discovery 配置在该文件中,你需要添加以下配置来启用节点发现机制。对于单节点部署,可以配置 discovery.seed_hosts 或 cluster.initial_master_nodes。
如果你的环境是 单节点(即只有一个 Elasticsearch 实例),你可以添加以下配置:yaml
# discovery.seed_hosts 用于指定初始节点列表,Elasticsearch 用它来查找其他节点
discovery.seed_hosts: ["127.0.0.1:9300"]# 或者你可以使用 cluster.initial_master_nodes 指定初始的主节点列表
cluster.initial_master_nodes: ["localhost"]
如果你部署的是 多节点集群,你需要配置集群中的所有节点的 IP 地址。例如:
yaml
discovery.seed_hosts: ["node1_ip:9300", "node2_ip:9300", "node3_ip:9300"]
cluster.initial_master_nodes: ["node1", "node2", "node3"]
discovery.seed_hosts 用于帮助节点相互发现,而 cluster.initial_master_nodes 用于在集群启动时指定初始的主节点。重启 Elasticsearch修改配置文件后,重启 Elasticsearch 服务。你可以使用以下命令来启动 Elasticsearch:vi /usr/local/software/elasticsearch/config/elasticsearch.yml
discovery.seed_hosts: ["127.0.0.1:9300"]
cluster.initial_master_nodes: ["localhost"]bash
./bin/elasticsearch

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。
如若转载,请注明出处:http://www.pswp.cn/bicheng/90661.shtml
繁体地址,请注明出处:http://hk.pswp.cn/bicheng/90661.shtml

如若内容造成侵权/违法违规/事实不符,请联系多彩编程网进行投诉反馈email:809451989@qq.com,一经查实,立即删除!

相关文章

windows下SAS9.4软件下载与安装教程

SAS 9.4是SAS公司推出的一款功能强大的统计分析软件&#xff0c;广泛应用于数据分析、商业智能、预测分析、数据挖掘及统计建模等多个领域。数据处理与管理能力&#xff1a;SAS 9.4支持多种数据格式的导入导出&#xff0c;包括JSON、XML等&#xff0c;便于处理来自Web和API的数…

MyBatis-Plus极速开发指南

MyBatis-Plus简介MyBatis-Plus 是一个 MyBatis 的增强工具&#xff0c;在 MyBatis 的基础上只做增强不做改变&#xff0c;简化开发&#xff0c;提高效率。它提供了以下主要特性&#xff1a;无侵入&#xff1a;只做增强不做改变&#xff0c;引入它不会对现有工程产生影响强大的 …

Django接口自动化平台实现(五)

8. 测试用例执行 预期效果如下&#xff1a;用例执行逻辑如下&#xff1a;前端提交用例 id 列表到后台&#xff0c;后台获取每一条用例的信息&#xff1b;后台获取域名信息、用例 id 列表&#xff1b;对用例的请求数据进行变量的参数化、函数化等预处理操作&#xff1b;根据先后…

一个没有手动加分号引发的bug

最近因为分号的疏忽&#xff0c;导致出现了一个bug&#xff0c;记录下来&#xff0c;分享给大家。 1、一个示例 给你下面这一段代码&#xff0c;你根据经验判断一下运营结果 let [a,b] [a,b] let [x,y] [1,2] if(x < y){[x,y] [y,x][a,b] [b,a] }按照一般的理解&#xf…

Elasticsearch安全审计日志设置与最佳实践

一、Elasticsearch安全审计简介 审计日志&#xff08;Audit Logging&#xff09;用于记录Elasticsearch中的安全相关事件&#xff0c;包括认证失败、连接拒绝、数据访问事件以及通过API对安全配置&#xff08;如用户、角色、API密钥&#xff09;的变更记录。 注意&#xff1a;审…

算法训练营day29 贪心算法③ 134. 加油站、135. 分发糖果 、860.柠檬水找零、406.根据身高重建队列

贪心算法的第三篇博客&#xff0c;继续脑筋风暴&#xff01; 134. 加油站 写在前面 这道题规定了有解的话&#xff0c;必定为唯一解 贪心思路 直接从全局进行贪心选择&#xff0c;情况如下&#xff1a; 情况一&#xff1a;如果gas的总和小于cost总和&#xff0c;那么无论从…

【09】C#入门到精通——C# 结构体对齐 与 常用数据 对应关系

文章目录1 C# 结构体对齐1.1 默认对齐方式1.2 节对齐方式设置1.3 偏移量设置2 C#与C/C之间类型的对应关系1 C# 结构体对齐 1.1 默认对齐方式 struct默认对齐方式&#xff0c;结构体长度必须是&#xff0c;最大成员长度的整数倍&#xff0c;所以下面结构体大小是 24 (实际占用…

pytest 测试报告生成方案有哪些?

在 pytest 中&#xff0c;除了 Allure 和 HTMLTestRunner&#xff0c;还有许多其他生成测试报告的方法和插件。以下是一些常用的方案及其特点&#xff1a;1. pytest-html&#xff08;官方推荐&#xff09;特点&#xff1a;轻量级、易集成&#xff0c;生成独立的 HTML 报告。安装…

Unity中EditorPrefs与PlayerPrefs对比分析

Unity中EditorPrefs与PlayerPrefs对比分析 EditorPrefs与PlayerPrefs是Unity引擎中用于数据持久化的两个核心类&#xff0c;分别用于于编辑器扩展与游戏运行时场景。以下从设计目标、存储位置、数据类型、生命周期、安全性、使用场景等方面展开对比&#xff0c;并结合代码示例说…

蓝光中的愧疚

蓝光中的愧疚活动结束那晚&#xff0c;深圳的空气吸饱了水汽&#xff0c;沉甸甸地压在胸口。我站在西乡社区活动中心冰凉的玻璃门外&#xff0c;目送着最后一个离开的王老师。她关掉门厅的灯&#xff0c;电子门锁合拢时发出轻微却尖锐的“嘀”声&#xff0c;像一根细针扎在我紧…

Linux: network: wireshark: esp attempt to detec null-encrypted esp payloads

最近看到一个pcap文件&#xff0c;里面有esp协议包&#xff0c;而且是明文/没有加密的消息&#xff0c;为什么wireshark没有将esp上层的tcp/sip消息没有解出来。 类似于Info列只有ESP的信息。后来选中了协议选项里的&#xff1a;attempt to detect/decode NULL encrypted ESP p…

10分钟搭建脚手架:Spring Boot 3.2 + Vue3 前后端分离模板

10分钟搭建脚手架&#xff1a;Spring Boot 3.2 Vue3 前后端分离模板一、项目结构设计二、后端搭建&#xff08;Spring Boot 3.2&#xff09;1. 快速初始化&#xff08;使用 Spring Initializr&#xff09;2. 核心配置application.yml跨域配置 CorsConfig.java3. 安全配置Secur…

【轨物方案】分布式光伏电站运维升级智能化系列:老电站的数智化重生

自2010年分布式光伏在国内兴起以来&#xff0c;十余年间&#xff0c;市场装机容量已实现飞跃式增长。长期以来&#xff0c;传统的人工巡查和抄表模式是它们日常运维的主要手段。然而&#xff0c;随着电站数量的激增和设备的老化&#xff0c;由此导致的事故频发&#xff0c;使得…

RAG 技术深度面试题:架构、优化与实践应用

1. RAG 基础架构设计 问题&#xff1a;对比单阶段检索&#xff08;Single-stage Retrieval&#xff09;与两阶段检索&#xff08;Two-stage Retrieval&#xff09;在 RAG 系统中的架构差异&#xff0c;说明在企业知识库场景下为何优先选择两阶段检索&#xff1f; 答案&#xff…

yolov8通道级剪枝讲解(超详细思考版)

为了提升推理速度并降低部署成本&#xff0c;模型剪枝已成为关键技术。本文将结合实践操作&#xff0c;讲解YOLOv8模型剪枝的方法原理、实施步骤及注意事项。 虽然YOLOv8n版本本身参数量少、推理速度快&#xff0c;能满足大多数工业检测需求&#xff0c;但谷歌研究表明&#x…

JavaSE:随机数生成

随机数在游戏开发、密码学、模拟测试等场景中扮演着关键角色。本文将深入探讨Java中两种主流的随机数生成技术&#xff1a;Random类和Math.random()方法&#xff0c;并解析背后的类与对象概念&#xff0c;助你全面掌握随机数生成的核心机制。一、随机数生成的两大技术 Java提供…

Android 持久化存储原理与使用解析

一、核心存储方案详解1. SharedPreferences (SP)使用方式&#xff1a;// 获取实例 SharedPreferences sp getSharedPreferences("user_prefs", MODE_PRIVATE);// 写入数据 sp.edit().putString("username", "john_doe").putInt("login_cou…

无 sudo 权限的环境下将 nvcc (CUDA Toolkit) 安装到个人目录 linux

要在无 sudo 权限的环境下将 nvcc 安装到 home 个人目录&#xff0c;你可以手动安装 CUDA Toolkit 到你的 $HOME 目录&#xff0c;只需以下几步即可使用 nvcc 编译 CUDA 程序。 ✅ 步骤&#xff1a;本地安装 CUDA Toolkit&#xff08;含 nvcc&#xff09; 下载 CUDA Toolkit Ru…

从指标定义到AI执行流:衡石SENSE 6.0的BI PaaS如何重构ISV分析链路

一、痛点&#xff1a;ISV行业解决方案的“三重断链”传统ISV构建行业分析模块时面临的核心挑战&#xff1a;指标定义碎片化&#xff1a;客户A的“销售额”含税&#xff0c;客户B不含税&#xff0c;衍生指标无法复用&#xff1b;分析-执行割裂&#xff1a;发现库存异常后需人工导…

构建跨平台远程医疗系统中的视频通路技术方案探究

一、远程医疗走向日常化&#xff0c;音视频能力成为关键基础设施 随着医疗数字化与分级诊疗体系的不断演进&#xff0c;远程医疗正从试点探索阶段&#xff0c;逐步迈向常态化、标准化应用。从县域医院远程问诊、基层医疗协作&#xff0c;到大型三甲医院的术中协同、专科教学直…