-
Notifications
You must be signed in to change notification settings - Fork 314
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
Tiup fail to start tiflash because of libtiflash_proxy.so #1135
Comments
Start playground failed too: Starting component
Playground Bootstrapping... |
Any updates? |
@JaySon-Huang PTAL, i suspect it may be related to the Jenkins job of release packaging. |
Now we don't support starting TiFlash instance without a TiDB cluster. So fail to run But starting tiup playground with TiFlash failed is not as expected. We will take a look at this. cc @LittleFall @birdstorm |
Thanks! |
@tohghua Can you get the log from tiflash when tiup playground failed? It should be under the ~/.tiup/data/ directory |
tiflash.log tiflash_tikv.log |
Seems there is something wrong when starting with " --host 0.0.0.0 ". TiUP playground will convert "0.0.0.0" to specific IP for the "advertise-addr" of TiKV but not convert it for TiFlash-Proxy. Can you try to set the parameter to " --host 127.0.0.1" or to a specific IP? @tohghua |
@JaySon-Huang [2021/02/22 09:19:25.671 +08:00] [INFO] [lib.rs:35] ["Welcome To TiFlash Raft Proxy"] |
Can you upload your |
@JaySon-Huang So pls check the "--host 0.0.0.0" case. Attached is tiflash.toml & tiflash-learner.toml at this time |
What did you do?
$ tiup tiflash
What did you expect to see?
No error message.
What did you see instead?
/home/hgh/.tiup/components/tiflash/v5.0.0-rc/tiflash/tiflash: error while loading shared libraries: libtiflash_proxy.so: cannot open shared object file: No such file or directory
Error: run
/home/hgh/.tiup/components/tiflash/v5.0.0-rc/tiflash/tiflash
(wd:/home/hgh/.tiup/data/SOccVcq) failed: exit status 127What version of TiUP are you using (
tiup --version
)?v1.3.2
It seems related to LD_LIBRARY_PATH env variable.
BTW, I'm using Ubuntu 20.04LTS
The text was updated successfully, but these errors were encountered: