-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
项目邀请成员报错:300 #381
Comments
麻烦补充下 broker 的日志 |
日志没有报错,如果是挂载目录里的/logs/pods里borker的话,0.log |
请问是哪个目录里的日志,叫什么名字 |
节点1对应的broker的0.log的内容可以贴一下。 |
日志贴全了吗?看不到有用的信息 |
2024-10-18T16:20:04.692819161+08:00 stdout F 2024-10-18 08:20:04.10188 INFO main.go:98 Starting to read config file: ./configs/config.yml |
以上是全部 |
受邀的节点名称是 |
现在找到问题是两个http协议的kuscia节点间通信状态为false,之前颁发证书、授权都是成功的,验证通信状态是false,这是为啥呢 |
hi,可以参考文档 https://www.secretflow.org.cn/zh-CN/docs/kuscia/v0.11.0b0/troubleshoot/network_authorization_check 排查下原因 |
现在发现重新授权两个http节点通信可以正常,但是经常会断开,Token又变成false,不知道为什么这么不稳定 |
可以检查下kuscia.log是否有异常信息 |
Issue Type
Running
Have you searched for existing issues?
Yes
OS Platform and Distribution
centos7
SCQL Version
SCQL. latest
What happend and What you expected to happen.
Configuration used to run SCQL.
SCQL log output.
The text was updated successfully, but these errors were encountered: