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

p2p inferencing not work #4214

Closed
mintyleaf opened this issue Nov 20, 2024 · 1 comment · Fixed by #4220
Closed

p2p inferencing not work #4214

mintyleaf opened this issue Nov 20, 2024 · 1 comment · Fixed by #4220
Labels
bug Something isn't working unconfirmed

Comments

@mintyleaf
Copy link
Contributor

LocalAI version:
7adbc16 (7adbc16)

Environment, CPU architecture, OS, and Version:
some vast.ai nvidia gpu instance

Describe the bug
telegram-cloud-photo-size-2-5327815199232747918-y

To Reproduce
just try to start p2p worker node in the working p2p environment

Additional context
using latest master docker image with my p2p fixes makes everything work in federated mode and connect two nodes with third just head server cpu node (+ using own DHT for faster discovery), yet, that only works for federated mode, worker is stuck in the loop here:

go func() {
for {
log.Info().Msgf("Starting llama-cpp-rpc-server on '%s:%d'", address, port)
grpcProcess := assets.ResolvePath(
r.BackendAssetsPath,
"util",

i'll try to investigate that further, but maybe you can get the idea of what is happening faster

@mudler
Copy link
Owner

mudler commented Nov 21, 2024

Seems there was a regression: should be fixed by #4220

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unconfirmed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants