-
Notifications
You must be signed in to change notification settings - Fork 6
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
ExApp context_chat_backend initialization timed out #36
Comments
Hello, that is a not a big issue but definitely something to improve. What happens is that the context chat php app tries to index all the users' files but the backend isn't initialised yet, which is why the 503 response. How do you arrive at the conclusion that it timed out? Did something happen after this which is not in the logs? |
You can see the timeout message in the posted screenshot. |
Updated: I just did a clean installation, using AIO in the new version 29, without user files, the first thing I did was install the context_chat_backend from AppAPI now in version 2.5.0 Unfortunately the problem persists, it reaches 50% and stays. I was able to validate that it downloads the image and deploys the container but it doesn't work.
|
oops :) @xavierg1909 Thanks for the update. Would you mind posting the full log of the docker container to see what exactly is going wrong? |
Hello, inexplicably today the AI already works, the strange thing is that the waiting time persists in the context_chat_backend, I leave the capture and the log in case you can correct that. I hope I have helped.
|
That is very helpful indeed. Thank you very much! The models were downloading when you tried to launch a query with assistant, same with the loading of sources. The error messages definitely need improvement and the context chat php app will also need a check to see if the backend's initialisation has completed before spamming the backend with the documents. I'll look into AppAPI's reporting of the timeout. Also, thanks for the logs again, looks like a regression with odfpy being removed 🙈 (it is required to parse ods files). Will fix all the issues on Monday. Have a nice weekend. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I got the context_chat_backend deployed, however isn't working. |
hello @architectonio, your issue seems similar. Can you provide me the server logs and the docker container logs? |
hello @kyteinsky , the same happens even with the ExApp "Test Deploy". PS. |
The content_chat_backend's logs, please. |
I am trying to deploy it again but deployment process remains at 0%. |
Do you see any server error logs regarding this? |
Here the Log: Detecting hardware... App disabled at startup |
looks perfect. At this point app_api should've called the |
OK. Is there anything I still can do? |
You may manually download the gguf and tar.gz files from here: https://download.nextcloud.com/server/apps/context_chat_backend/ Extract the tar.gz file and place both the extracted folder and the gguf file in the docker volume attached to the context chat's container (mounted at |
OK, I'll try to figure it out and give you a feedback. |
Is this the Volume you are referring to? docker volume inspect nc_app_context_chat_backend_data [ and if yes, I just need to proceed as you wrote by coping the content of downloaded files in to the volume, and I guess then restarting the container? |
yes and yes. Remember to extract the tar.gz file before moving it to the volume. |
btw, since you said the Test Deploy doesn't work for you. Would you mind creating an issue with the relevant details (server, socket proxy logs and maybe the console logs) and screenshots here: https://github.com/cloud-py-api/app_api/issues ? |
I did it. |
Thank you, replying there and closing this issue. |
@kyteinsky, me again. Since even the Test Deploy ExApp isn't working well, now I believe that something is wrong with the docker socket proxy. docker ps docker inspect nextcloud-appapi-dsp [ My Nextcloud instance talks with nextcloud-appapi-dsp through docker.sock (/var/run/docker.sock) |
Ah my bad, you need to move |
OK I did it. I am going to do some test and then give you a feedback. |
After a lot of tests, including removing and reinstalling images and containers, and of course adding/copying the files above into the container, unfortunately nothing has changed. |
Any news on this? |
Hi @architectonio This is required, so nextcloud can do a hostname lookup (this won't work in network bridge!). |
Describe the bug
ExApp context_chat_backend initialization timed out by one click
To Reproduce
Steps to reproduce the behavior:
Expected behavior
context_chat_backend enabled
Server logs (if applicable)
_nextcloud-aio-nextcloud_logs (2).txt
Context Chat Backend logs (if applicable, from the docker container)
_nc_app_context_chat_backend_logs (5).txt
Screenshots
Setup Details (please complete the following information):
--
- Nextcloud deployment method: [eg. Apache bare-metal] - Context Chat Backend deployment method: [eg. manual, one-click]Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: