xray问题排查,curl: (35) Encountered end of file(已解决)

经过了好几次排查,都没找到问题,先说问题的排查过程,多次确认了user信息,包括用户id和alterid,都没问题,头大的一逼

问题排查过程

确保本地的xray服务是正常的

[root@k8s-master01 xray]# systemctl status xray
● xray.service - Xray ServiceLoaded: loaded (/etc/systemd/system/xray.service; enabled; vendor preset: disabled)Active: active (running) since 六 2024-03-16 22:12:12 CST; 16min agoMain PID: 16207 (xray)CGroup: /system.slice/xray.service└─16207 /usr/local/xray/xray -config /usr/local/xray/config.json3月 16 22:12:12 k8s-master01 systemd[1]: Started Xray Service.
3月 16 22:12:12 k8s-master01 xray[16207]: Xray 1.8.6 (Xray, Penetrates Everything.) Custom (go1.21.4 linux/amd64)
3月 16 22:12:12 k8s-master01 xray[16207]: A unified platform for anti-censorship.
3月 16 22:12:12 k8s-master01 xray[16207]: 2024/03/16 22:12:12 [Info] infra/conf/serial: Reading config: /usr/local/xray/config.json

从这一步看上去没问题,接着又开始第二步,通过journalctl排查

[root@k8s-master01 xray]# journalctl -f -xu xray
-- Logs begin at 一 2024-03-04 18:07:02 CST. --
3月 16 22:12:07 k8s-master01 systemd[1]: Started Xray Service.
-- Subject: Unit xray.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit xray.service has finished starting up.
-- 
-- The start-up result is done.
3月 16 22:12:07 k8s-master01 xray[16057]: Xray 1.8.6 (Xray, Penetrates Everything.) Custom (go1.21.4 linux/amd64)
3月 16 22:12:07 k8s-master01 xray[16057]: A unified platform for anti-censorship.
3月 16 22:12:07 k8s-master01 xray[16057]: 2024/03/16 22:12:07 [Info] infra/conf/serial: Reading config: /usr/local/xray/config.json
3月 16 22:12:12 k8s-master01 systemd[1]: Stopping Xray Service...
-- Subject: Unit xray.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit xray.service has begun shutting down.
3月 16 22:12:12 k8s-master01 systemd[1]: Stopped Xray Service.
-- Subject: Unit xray.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit xray.service has finished shutting down.
3月 16 22:12:12 k8s-master01 systemd[1]: Started Xray Service.
-- Subject: Unit xray.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit xray.service has finished starting up.
-- 
-- The start-up result is done.
3月 16 22:12:12 k8s-master01 xray[16207]: Xray 1.8.6 (Xray, Penetrates Everything.) Custom (go1.21.4 linux/amd64)
3月 16 22:12:12 k8s-master01 xray[16207]: A unified platform for anti-censorship.
3月 16 22:12:12 k8s-master01 xray[16207]: 2024/03/16 22:12:12 [Info] infra/conf/serial: Reading config: /usr/local/xray/config.json

也没看出什么问题,windows上测试几次都是正常的

为了保持统一,已经把windows上的config.json的内容复制粘贴到centos上了

现在开始接下来操作就是配日志(服务端和客户端都配置了)

  "log": {"access": "/var/log/xray/access.log","error": "/var/log/xray/error.log","loglevel": "debug"},

然后通过tail命令查看

服务端日志是这个

2024/03/16 14:10:09 [Info] [4164381125] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:11:01 [Info] [634757384] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:14:01 [Info] [1120841913] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:14:57 [Info] [1537117142] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:14:57 [Info] [549166064] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:15:05 [Info] [1278316473] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:15:15 [Info] [1619787935] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:16:07 [Info] [336587068] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:19:14 [Info] [3178032418] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:20:02 [Info] [1422900044] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:20:19 [Info] [2559318044] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:20:22 [Info] [1461925477] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist
2024/03/16 14:21:16 [Info] [850676330] app/proxyman/inbound: connection ends > proxy/vmess/inbound: invalid request from 183.222.204.175:0 > proxy/vmess/encoding: invalid user > user do not exist

 客户端日志是这个

3月 04 18:16:00 k8s-master01 xray[1346]: 2024/03/04 18:16:00 [Warning] [2403275693] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:02 k8s-master01 xray[1346]: 2024/03/04 18:16:02 127.0.0.1:46674 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:10 k8s-master01 xray[1346]: 2024/03/04 18:16:10 [Warning] [2594380722] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:12 k8s-master01 xray[1346]: 2024/03/04 18:16:12 127.0.0.1:46770 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:20 k8s-master01 xray[1346]: 2024/03/04 18:16:20 [Warning] [1302667946] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:22 k8s-master01 xray[1346]: 2024/03/04 18:16:22 127.0.0.1:46874 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:30 k8s-master01 xray[1346]: 2024/03/04 18:16:30 [Warning] [2697733957] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:32 k8s-master01 xray[1346]: 2024/03/04 18:16:32 127.0.0.1:46966 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:38 k8s-master01 xray[1346]: 2024/03/04 18:16:38 websocket: failed to close network connection: close tcp 192.168.10.10:43776->8.210.103.219:443: use of closed network connection
3月 04 18:16:40 k8s-master01 xray[1346]: 2024/03/04 18:16:40 websocket: failed to close network connection: close tcp 192.168.10.10:43786->8.210.103.219:443: use of closed network connection
3月 04 18:16:40 k8s-master01 xray[1346]: 2024/03/04 18:16:40 [Warning] [1423899102] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:42 k8s-master01 xray[1346]: 2024/03/04 18:16:42 127.0.0.1:47070 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:50 k8s-master01 xray[1346]: 2024/03/04 18:16:50 [Warning] [3280367621] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:16:50 k8s-master01 xray[1346]: 2024/03/04 18:16:50 websocket: failed to close network connection: close tcp 192.168.10.10:43890->8.210.103.219:443: use of closed network connection
3月 04 18:16:52 k8s-master01 xray[1346]: 2024/03/04 18:16:52 127.0.0.1:47164 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:16:58 k8s-master01 xray[1346]: 2024/03/04 18:16:58 websocket: failed to close network connection: close tcp 192.168.10.10:43974->8.210.103.219:443: use of closed network connection
3月 04 18:17:00 k8s-master01 xray[1346]: 2024/03/04 18:17:00 [Warning] [2142162998] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:17:10 k8s-master01 xray[1346]: 2024/03/04 18:17:10 [Warning] [1406668282] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:17:53 k8s-master01 xray[1346]: 2024/03/04 18:17:53 127.0.0.1:47750 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:03 k8s-master01 xray[1346]: 2024/03/04 18:18:03 127.0.0.1:47840 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:06 k8s-master01 xray[1346]: 2024/03/04 18:18:06 [Warning] [4145448540] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:18:13 k8s-master01 xray[1346]: 2024/03/04 18:18:13 127.0.0.1:47942 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:16 k8s-master01 xray[1346]: 2024/03/04 18:18:16 [Warning] [1365796855] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:18:23 k8s-master01 xray[1346]: 2024/03/04 18:18:23 127.0.0.1:48032 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:26 k8s-master01 xray[1346]: 2024/03/04 18:18:26 [Warning] [2392807403] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:18:33 k8s-master01 xray[1346]: 2024/03/04 18:18:33 127.0.0.1:48136 accepted //registry-1.docker.io:443 [http -> proxy]
3月 04 18:18:36 k8s-master01 xray[1346]: 2024/03/04 18:18:36 [Warning] [2814008583] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:18:46 k8s-master01 xray[1346]: 2024/03/04 18:18:46 [Warning] [2119998531] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/
3月 04 18:20:09 k8s-master01 xray[1346]: 2024/03/04 18:20:09 127.0.0.1:49040 accepted //registry-1.docker.io:443 [http -> proxy]

说实话,看了上面两个日志,我是摸不着头,因为userid和alterid都确认过都不知道多少次了,都感觉没问题

一度怀疑是xray的问题,于是换了一个客户端,采用v2ray的客服端

于是用v2ray进行本地服务配置,可还是出现同样的问题

后面网上说通过alter为0可以解决,然后还有其它乱七八着的解决方法,还是不行

终于,看到一条有用的信息,时间差

于是,更新centos的时间

 ntpdate time.windows.com

 再次查看

[root@k8s-master01 ~]# curl -x http://127.0.0.1:10809 https://www.google.com -v
* About to connect() to proxy 127.0.0.1 port 10809 (#0)
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 10809 (#0)
* Establish HTTP proxy tunnel to www.google.com:443
> CONNECT www.google.com:443 HTTP/1.1
> Host: www.google.com:443
> User-Agent: curl/7.29.0
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 200 Connection established
< 
* Proxy replied OK to CONNECT request
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crtCApath: none
* SSL connection using TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
* Server certificate:
*       subject: CN=www.google.com
*       start date: 2月 19 08:19:14 2024 GMT
*       expire date: 5月 13 08:19:13 2024 GMT
*       common name: www.google.com
*       issuer: CN=GTS CA 1C3,O=Google Trust Services LLC,C=US
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: www.google.com
> Accept: */*
> 
< HTTP/1.1 302 Found
< Location: https://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=https://www.google.com.hk/&ust=1710600070261911&usg=AOvVaw1xFQ6FZSUAQ0p_KF1PPren
< Cache-Control: private
< Content-Type: text/html; charset=UTF-8
< Content-Security-Policy-Report-Only: object-src 'none';base-uri 'self';script-src 'nonce-zeU1oF1mM8-Ul5Hpk8GhNw' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hp
< P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
< Date: Sat, 16 Mar 2024 14:40:40 GMT
< Server: gws
< Content-Length: 372
< X-XSS-Protection: 0
< X-Frame-Options: SAMEORIGIN
< Set-Cookie: 1P_JAR=2024-03-16-14; expires=Mon, 15-Apr-2024 14:40:40 GMT; path=/; domain=.google.com; Secure
< Set-Cookie: AEC=Ae3NU9PNmRL7EUmFbkfvziLkI-U_QJBZOxNBfkb0OXkO9kOOvAlHiX_gSQ; expires=Thu, 12-Sep-2024 14:40:40 GMT; path=/; domain=.google.com; Secure; HttpOnly; SameSite=lax
< Set-Cookie: NID=512=A4a6jbVPAvqT8ipYJhTvbuS-FsX-hDEA90zLI0FhkT3oDJKoMsYaqQlRyllu2wH_Bw-_nTgAwCrvr4TogqxEOfh77CPlxc4A9jRMmHQBpWjqF7yFiByuBB6O6vgmQNDGALw5zZue0O8irX7h_2w4zRNUrOEZVA32rSLmYoJpl1s; expires=Sun, 15-Sep-2024 14:40:40 GMT; path=/; domain=.google.com; HttpOnly
< Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
< 
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="https://www.google.com.hk/url?sa=p&amp;hl=zh-CN&amp;pref=hkredirect&amp;pval=yes&amp;q=https://www.google.com.hk/&amp;ust=1710600070261911&amp;usg=AOvVaw1xFQ6FZSUAQ0p_KF1PPren">here</A>.
</BODY></HTML>
* Connection #0 to host 127.0.0.1 left intact

成功解决

问题排查方向

VMess: Invalid User 可能的原因:

    1、客户端和服务器端的用户 ID 不匹配;2、客户端和服务器端的用户 alterId 不匹配;3、客户端与服务器的时间不匹配,误差不能超过90秒钟;

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

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

相关文章

StarRocks面试题及答案整理,最新面试题

StarRocks 的 MV&#xff08;物化视图&#xff09;机制是如何工作的&#xff1f; StarRocks 的物化视图&#xff08;MV&#xff09;机制通过预先计算和存储数据的聚合结果或者转换结果来提高查询性能。其工作原理如下&#xff1a; 1、数据预处理&#xff1a; 在创建物化视图时…

2024年3月环境管理体系基础考试真题

2024年3月环境管理体系基础考试真题 一、单项选择题&#xff08;每题1.5分&#xff0c;共60分&#xff09; 1.依据GB/T24001-2016标准&#xff0c;6.1.1中要求应确定需应对的风险和机遇&#xff0c;以确保组织能够实现其环境管理体系的预期结果&#xff0c;预防或减少&#x…

开发指南005-前端配置文件

平台要求无论前端还是后端&#xff0c;修改配置可以直接用记事本修改&#xff0c;无需重新打包或修改压缩包里文件。就前端而言&#xff0c;很多系统修改配置是在代码里修改&#xff0c;然后打包或者是修改编译环境来重新编译。 平台前端的配置文件为/static/js/下qlm_config.j…

算法打卡day19|二叉树篇08|Leetcode 235. 二叉搜索树的最近公共祖先、701.二叉搜索树中的插入操作、450.删除二叉搜索树中的节点

算法题 Leetcode 235. 二叉搜索树的最近公共祖先 题目链接:235. 二叉搜索树的最近公共祖先 大佬视频讲解&#xff1a;二叉搜索树的最近公共祖先视频讲解 个人思路 昨天做过一道二叉树的最近公共祖先&#xff0c;而这道是二叉搜索树&#xff0c;那就要好好利用这个有序的特点…

Linux: 调用接口

进程相关 获取进程id与创建进程 头文件: <unistd.h>getpid() : 获取进程idgetppid() : 获取父进程的idfork() : 创建子进程, 给父进程返回子进程的id, 给子进程返回0 等待子进程 头文件: <sys/types.h> <sys/wait.h>pid_t wait(int*status); 返回值: 成…

欧拉openeuler23.09默认软件源太慢了,修改为华为云更新源,附上具体配置内容。

因为是直接在原有的文件基础上修改的&#xff0c;所以有一些不需要的内容我用#号屏蔽掉了。 #generic-repos is licensed under the Mulan PSL v2. #You can use this software according to the terms and conditions of the Mulan PS L v2. #You may obtain a copy of Mulan…

2000-2021年各省外商直接投资水平面板数据(含原始数据+计算结果)(无缺失)

2000-2021年各省外商直接投资水平面板数据&#xff08;含原始数据计算结果&#xff09;&#xff08;无缺失&#xff09; 1、时间&#xff1a;2000-2021年 2、指标&#xff1a;外商直接投资额&#xff08;万美元&#xff09;、外商直接投资额&#xff08;万元&#xff09;、国…

代码随想录 二叉树—二叉树的最大深度

思路&#xff1a;depth初始为0&#xff0c;要是有子孩子就depth加1&#xff0c;循环过了之后最后一个没子孩子&#xff0c;depth也会加1&#xff0c;弥补了先开始的0。简单题&#xff0c;模板略微改一点。 题解c&#xff1a; /*** Definition for a binary tree node.* struc…

lv17 安防监控实现之通信协议制定 2

项目功能框架分层 ***************************************************** 分层分析&#xff1a; ***************************************************** web网页端显示部分&#xff1a; 环境信息摄像头采集图像&#xff1a; 硬件控制&#xff1a; A9数据处理部分 A9-Z…

Linux下最常用的MySQL运维脚本

MySQL是一个广泛用于Web应用程序和服务器的开源关系型数据库管理系统。在Linux环境中&#xff0c;运维MySQL数据库可能涉及到许多日常任务&#xff0c;如备份、性能优化、监控等。为了提高效率&#xff0c;许多运维工作可以通过编写脚本来自动化执行。本文将介绍一些在Linux下最…

Leetcode64. 最小路径和

Problem: 64. 最小路径和 文章目录 思路解题方法复杂度Code 思路 动态规划,偷房子问题变形 解题方法 dp[i][j] min(dp[i-1][j],dp[i][j-1])grid[i][j]; 复杂度 时间复杂度: O ( m ∗ n ) O(m*n) O(m∗n) 空间复杂度: O ( m ∗ n ) O(m*n) O(m∗n) Code class Solution { pub…

leetcode代码记录(动态规划基础题(斐波那契数列)

目录 1. 题目&#xff1a;2. 斐波那契数列&#xff1a;小结&#xff1a; 1. 题目&#xff1a; 斐波那契数 &#xff08;通常用 F(n) 表示&#xff09;形成的序列称为 斐波那契数列 。该数列由 0 和 1 开始&#xff0c;后面的每一项数字都是前面两项数字的和。也就是&#xff1a…

[LeetCode][LCR173]点名——二分结合输入数据特点找边界

题目 LCR 173. 点名 某班级 n 位同学的学号为 0 ~ n-1。点名结果记录于升序数组 records。假定仅有一位同学缺席&#xff0c;请返回他的学号。 示例 1&#xff1a; 输入&#xff1a;records [0,1,2,3,5] 输出&#xff1a;4 示例 2&#xff1a; 输入&#xff1a;records [0, …

王道c语言-判断对称数,sprintf应用

Description 输入一个整型数&#xff0c;判断是否是对称数&#xff0c;如果是&#xff0c;输出yes&#xff0c;否则输出no&#xff0c;不用考虑这个整型数过大&#xff0c;int类型存不下&#xff0c;不用考虑负值 方法一 取余乘位权 #include <stdio.h> int main() {i…

TensorFlow的介绍和简单案例

TensorFlow是一个开源的机器学习框架,由Google开发和维护。它旨在使构建和训练机器学习模型变得更加容易,同时提供高度灵活性和可扩展性。 TensorFlow基于数据流图的概念。数据流图是一个由节点和边组成的有向图,其中节点表示操作,边表示数据的流动。TensorFlow通过在数据…

YOLOv9更换iou|包含CIoU、DIoU、MDPIoU、GIoU

专栏介绍&#xff1a;YOLOv9改进系列 | 包含深度学习最新创新&#xff0c;助力高效涨点&#xff01;&#xff01;&#xff01; 一、改进点介绍 更换YOLOv9中使用的Iou计算方式&#xff0c;目前支持CIoU、DIoU、MDPIoU、GIoU。 二、Iou模块详解 2.1 模块简介 Iou的主要思想&…

<JavaEE> 数据链路层 -- 以太网协议、MTU限制、ARP协议

目录 以太网协议 什么是以太网&#xff1f; 以太网的帧格式 什么是MAC地址&#xff1f; MAC地址和IP地址的对比&#xff1f; MTU&#xff08;最大传输单元&#xff09;限制 什么是MTU限制&#xff1f; MTU对IP协议有什么影响&#xff1f; MTU对UDP协议有什么影响&…

HDOJ 2034

人见人爱A-B Problem Description 参加过上个月月赛的同学一定还记得其中的一个最简单的题目&#xff0c;就是{A}{B}&#xff0c;那个题目求的是两个集合的并集&#xff0c;今天我们这个A-B求的是两个集合的差&#xff0c;就是做集合的减法运算。&#xff08;当然&#xff0c;…

pre_min[0:10, 2:3] = pre和pre_min[0:10, 2] = pre区别

在NumPy中&#xff0c;数组切片的语法非常具体&#xff0c;它决定了哪些元素被选取或赋值。对于您提到的两个切片表达式&#xff0c;pre_min[0:10, 2:3] 和 pre_min[0:10, 2]&#xff0c;它们有本质的区别&#xff0c;主要体现在所选的维度和形状上。 pre_min[0:10, 2:3]:这个…

微服务:Bot代码执行

每次要多传一个bot_id 判网关的时候判127.0.0.1所以最好改localhost 创建SpringCloud的子项目 BotRunningSystem 在BotRunningSystem项目中添加依赖&#xff1a; joor-java-8 可动态编译Java代码 2. 修改前端&#xff0c;传入对Bot的选择操作 package com.kob.botrunningsy…