-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Bug]: No answer from KI in Assistent #142
Comments
Had the same problem but but in a LAMP stack installation. |
Thanks for the tip. When I issue the command “occ background-job:worker” in the console and start the chat, I get a response. However, the command causes a continuous loop of the running jobs in the console. If I then close the command with ctrl+c in the console, I no longer receive a response when chatting with the AI. By the way, I have also tried a LAMP installation in a VM under Ubuntu Server. Same error pattern regarding no AI response as with Docker! |
For the LAMP installation i created a dedicated service:
and enabled it with
This works perfect. |
@joshtrichards not sure, if "Assistant" is the rights section, because tho code change needs to be done in server, not in Assistant. |
I think this is related to #129 |
Me too, I was using NC 29 with LM Studio and it worked perfectly, but after I upgraded to NC 30, the Assistant stopped responding. |
As mentioned by @ascheurer-rts This is because since NC 30, tasks are running in a background job. So there is a delay, you wait until the next cron.php execution. |
But Julien, the tasks doesn't finish, that's what we are trying to explain. It is not related with a late response, it is related with no action is taken from NC, can you please try to reproduce the issue? |
Hi, might it be there is an issue/bug with the config at all in NC 30.x for the A.I. Assistant? My main NC version 30.0.2 has the same issue what the thread creator is describing no response. |
i can confirm |
Thank you for all the answers. It is correct that the query “occ background-job:worker” can be accelerated. Otherwise the query only takes place every 5 minutes e.g. 12.00...12.05...12.10 But I see a bug in Nextcloud here, because it can't be that you can only receive a request to the AI every 5 minutes without starting a background job. |
Bug description
Here is the translation:
"I'm running Nextcloud on my Unraid server, which I have set up in a Docker container using the Linuxserver Image. Additionally, I've installed a local AI (Ollama and LocalAI) as well.
When I enter the IP address of the AI (Ollama or LocalAI) into the App LocalAI under Nextcloud, the AI is found and displays the installed LLMs. The LLMs are running smoothly and I can chat with the KI using OpenWebUI or through the chat in (LocalAI).
However, when I start a chat in the Nextcloud Assistant, I don't receive an answer. However, my question goes into Ollama and LocalAI (which can be seen in their logs) but is not processed.
But if I set up a prompt using the Nextcloud App on my iPhone under "More / Assistant", I immediately get a response from the KI.
After long searching, I was able to pinpoint the error. Under Nextcloud 29.0.7 (Docker Nextcloud:29.0.7) the response works fine. But with Nextcloud 30, I don't receive any answer.
"I followed your test environment.
docker pull nextcloud:latest
and
nextcloud:29.0.7` (the official images)Note: I didn't make any changes or configurations during these tests. The first start only created the admin user, and both tests were run with minimal system setups."
I hope you can help me find a solution to this problem."
Greetings Thomas
Steps to reproduce
Expected behavior
.
Nextcloud Server version
30
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: