-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Error in connecting with LocalAI server #945
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
Comments
Need more logs with debug enabled |
I don't know if it is the same issue or not, but I'm trying to run the example CUDA configuration from here, and getting similar dial tcp errors on WSL. The curl request in my case with the prompt never returns and just hangs. Here's the log: |
I am seeing the same issue. |
P.S. I am using this model definition https://github.com/go-skynet/model-gallery/blob/main/openllama_7b.yaml |
Interestingly enough If I'm using one of the CPU samples it's starts working. Though based on the previously attached log I'm not seeing any GPU issues, it finishes loading the model. I've tried increasing the resources in .wslconfig to 32GB RAM and 8 CPU cores, but made no difference. It doesn't seem to be resource constrained. I've also tried going into the running container, installing net-tools and querying the available service ports, and the gRPC service sits there, and responds to trying to access it with curl for example (bad protocol). So I don't think it's a network issue anymore. Can you suggest something to try? |
It looks like this issue is the same. So it's not Windows related. #840 |
So this might not work for everyone, but using a more recent version than what the documentation says and with cublas11 tagged image (it might also work with cublas12, haven't checked) and the exllama backend with a GPTQ compatible image, it's started functioning and using the GPU.
|
#1076 has the same errors, poses a possible root cause |
Also getting a similar issue here. .env
docker-compose.yaml
Request & Error
Container Logs
Debug
If I change to the
Also on WSL 2 with 8 cores and 32gb(out of 64gb) of memory allocated |
I am unable to connect to the server using CURL
LocalAI version:
Environment, CPU architecture, OS, and Version:
WSL on Windows 10
Linux DESKTOP-MHK5NK5 4.4.0-19041-Microsoft #2311-Microsoft Tue Nov 08 17:09:00 PST 2022 x86_64 x86_64 x86_64 GNU/Linux
Describe the bug
On the server window I see
┌───────────────────────────────────────────────────┐
│ Fiber v2.48.0 │
│ http://127.0.0.1:8080 │
│ (bound on host 0.0.0.0 and port 8080) │
│ │
│ Handlers ............ 55 Processes ........... 1 │
│ Prefork ....... Disabled PID .............. 1366 │
└───────────────────────────────────────────────────┘
rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:51860: connect: connection refused"
rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:51864: connect: connection refused"
The text was updated successfully, but these errors were encountered: