Skip to content
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

按照文档中的快速开始执行到查询步骤时出错 #400

Open
UCyanMei opened this issue Nov 18, 2024 · 4 comments
Open

按照文档中的快速开始执行到查询步骤时出错 #400

UCyanMei opened this issue Nov 18, 2024 · 4 comments

Comments

@UCyanMei
Copy link

Issue Type

Others

Have you searched for existing issues?

Yes

Link to Relevant Documentation

No response

Question Details

按照SecretFlow文档进行快速开始部署,前面的步骤都能够成功执行,但执行最后的查询步骤时,报出如下错误:
[demo]alice> SELECT ta.credit_rank, COUNT(*) as cnt, AVG(ta.income) as avg_income, AVG(tb.order_amount) as avg_amount FROM ta INNER JOIN tb ON ta.ID = tb.ID WHERE ta.age >= 20 AND ta.age <= 30 AND tb.is_active=1 GROUP BY ta.credit_rank;
WARN[0023] content-type (text/plain; charset=utf-8) is not one of application/json and application/x-protobuf 
[fetch]err: Code: 320, message:RunExecutionPlan create session(0b8ceb1f-a586-11ef-bd53-0242ac120002) failed, catch std::exception=[Enforce fail at engine/auth/authenticator.cc:61] self_public_key_ == pi.pub_key. self public key mismatched
Stacktrace:
#0 scql::engine::auth::Authenticator::Verify()+0xaaaacba93b34
#1 scql::engine::EngineServiceImpl::VerifyPublicKeys()+0xaaaacba8592c
#2 scql::engine::EngineServiceImpl::RunExecutionPlan()+0xaaaacba8e138
#3 brpc::policy::ProcessHttpRequest()+0xaaaace995eb8
#4 brpc::ProcessInputMessage()+0xaaaace94871c
#5 brpc::InputMessenger::InputMessageClosure::~InputMessageClosure()+0xaaaace9490d4
#6 brpc::InputMessenger::OnNewMessages()+0xaaaace94a6cc
#7 brpc::Socket::ProcessEvent()+0xaaaacea2b654
#8 bthread::TaskGroup::task_runner()+0xaaaacea8a048
@BrainWH
Copy link

BrainWH commented Nov 18, 2024

根据报错信息是生成公钥不匹配,可以参照官网部署文档重新部署

@UCyanMei
Copy link
Author

麻烦问一下有没有办法能检查生成的公钥具体内容的办法,比如文件在哪里,查看是如何不匹配之类的

@BrainWH
Copy link

BrainWH commented Nov 19, 2024

当前参考的版本是哪一个,可以提供一下

@jingshi-ant
Copy link
Collaborator

麻烦问一下有没有办法能检查生成的公钥具体内容的办法,比如文件在哪里,查看是如何不匹配之类的

在create user的时候会将user和公钥绑定,绑定信息存储在mysql的user表里;
engine实例拉起依赖两个文件:ed25519key.pem(自己的私钥、公钥);authorized_profile.json(其它参与方的公钥)

具体排查的时候,可以用docker logs -f xxxid 查看日志,并docker exec -it xxxid bash登录实例check文件,登录xxxmysql查看表内容来确认。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants