doesn't seem to work #4

Open
opened 2022-08-26 18:54:10 +00:00 by rabble · 1 comment

RUST_LOG=lykin=info ./target/release/lykin
[2022-08-26T18:49:17Z INFO lykin::sbot] Executing whoami call
thread 'main' panicked at 'whoami rpc call failed. please ensure the sbot is running before trying again: "IO error: failed to initiate tcp stream connection"', src/main.rs:134:10
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace


go-sbot
t=6.504166ms starting=metrics addr=localhost:6078
level=info t=82.082666ms event="waiting for indexes to catch up"
level=info t=85.993625ms event="repo open" feeds=0 msgs=0
level=info t=86.089041ms event=serving ID="@oLTta/PY8Ikra+XS9C5vqyNo5/fctfqmpQy2P8SborA=.ed25519" addr=:8008 version=snapshot build=

Go-sbot is running but lykin can't connect to it...

the cli works:

sbotcli call whoami
level=info client=connected method="unix sock"
level=debug event="call reply"
{
"id": "@oLTta/PY8Ikra+XS9C5vqyNo5/fctfqmpQy2P8SborA=.ed25519"
}%

RUST_LOG=lykin=info ./target/release/lykin [2022-08-26T18:49:17Z INFO lykin::sbot] Executing `whoami` call thread 'main' panicked at 'whoami rpc call failed. please ensure the sbot is running before trying again: "IO error: failed to initiate tcp stream connection"', src/main.rs:134:10 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ----- go-sbot t=6.504166ms starting=metrics addr=localhost:6078 level=info t=82.082666ms event="waiting for indexes to catch up" level=info t=85.993625ms event="repo open" feeds=0 msgs=0 level=info t=86.089041ms event=serving ID="@oLTta/PY8Ikra+XS9C5vqyNo5/fctfqmpQy2P8SborA=.ed25519" addr=:8008 version=snapshot build= Go-sbot is running but lykin can't connect to it... the cli works: sbotcli call whoami level=info client=connected method="unix sock" level=debug event="call reply" { "id": "@oLTta/PY8Ikra+XS9C5vqyNo5/fctfqmpQy2P8SborA=.ed25519" }%
Owner

Hey @rabble, thanks for trying it out and reporting back! This issue snuck past me somehow and I've only just seen it.

I can see from your logs that go-sbot is running on port 8008.

There's a note about this in the Quickstart section of the README (I should probably aim to have this info stand out more):

Note: by default, lykin attempts to connect to the go-sbot instance on port 8021. Set the GO_SBOT_PORT environment variable if you wish to use another port.

So you should be able to get it running with:

GO_SBOT_PORT=8008 ./target/release/lykin

Hey @rabble, thanks for trying it out and reporting back! This issue snuck past me somehow and I've only just seen it. I can see from your logs that go-sbot is running on port 8008. There's a note about this in the Quickstart section of the README (I should probably aim to have this info stand out more): > Note: by default, lykin attempts to connect to the go-sbot instance on port 8021. Set the GO_SBOT_PORT environment variable if you wish to use another port. So you should be able to get it running with: `GO_SBOT_PORT=8008 ./target/release/lykin`
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: glyph/lykin#4
No description provided.