Error logs generated while running a request
the100rabh opened this issue · 3 comments
Describe the bug
I get a bunch of error messages while processing the requests like
backend-1 | 2024/04/05 10:25:52 Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 error from evaluator: Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 error from evaluator: Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 Error adding document: error adding document: Post "http://chromadb:8000/api/v1/collections/23c6026d-4ded-4fdd-8741-8f9541dfeebd/add": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 error from evaluator: Error adding document: error adding document: Post "http://chromadb:8000/api/v1/collections/23c6026d-4ded-4fdd-8741-8f9541dfeebd/add": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 error from evaluator: Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 error from evaluator: Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 error from evaluator: Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:52 error from evaluator: Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:53 Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
backend-1 | 2024/04/05 10:25:53 error from evaluator: Error adding document: error adding document: Post "http://host.docker.internal:11434/api/embeddings": context deadline exceeded
To Reproduce
Steps to reproduce the behavior:
- Start LLSearch via docker and give a request
- Watch the request logs in the command prompt
- UI is updated with proper response
Additional context
Not sure if there is actually a problem here but just wanted to report the logs
There is a timeout on the create embeddings function, could you please post your device specs? I might have to up the timeout for lower end hardware or something
I have the same issue, at least for me I assume it's, because I'm running it on a CPU. The models run fine, just slow.
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz with 64gb of ram
I have the same issue, at least for me I assume it's, because I'm running it on a CPU. The models run fine, just slow.
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz with 64gb of ram
Yes that makes sense. The embedding model has no time to create the embeddings since it's running a lot slower on the CPU.
I would like to find a better solution than just disabling the timeout (since some overly large pages can otherwise block the web search for tens of seconds, which isn't really a nice user experience).
But until we find something better I'm just going to disable the timeout haha. Sorry for the inconvenience.