-
Notifications
You must be signed in to change notification settings - Fork 263
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
Search not working (even with 1.3) #2941
Comments
The Nextcloud mail app offers an extensive logging system to make it easier identifying and tracking down bugs. Please enable debug mode and set the log level to debug in your admin settings. Then, try to reproduce your issue and take another look at |
horde_imap.log:
nextcloud.log is not particularily useful, as that's now full of hundreds of unrelated messages per second. If you have something I should search for there, I could probably find it, but otherwise it's pretty useless right now. |
That is strange. I can't tell if this means it's a timeout between Nextcloud and IMAP or withing the IMAP server. But given the time spent, I think the IMAP server is just a bit slow. Could you add
|
(To make sure: I added
|
With quotes. Like "app.mail.imap.timeout" => 20, |
That seems to fix it so far. Do you need more logs with this setting? |
This is the fix. Your IMAP server is just a bit slow, thus the 5s timeout were too short. You can experiment with lower values. |
Thanks for your help, I'm happy that searching works again now. So I guess the local message cache is not (yet?) used for search functionality? (For others ending up here, here's the relevant page for setting up a dovecot full text search engine, which should make the search faster on the imap server side: https://doc.dovecot.org/configuration_manual/fts/) |
It is used, but it depends on the search type. So the cache does not contain the actual messages, but just the headers or anything that is shown in the message list when you open the app. If you then search for a string, it might still ask the IMAP server for the UIDs. The UIDs are then used to load the local data. If you search like
But do you have that set up? |
That's good to know!
I have not, which is why full text search is slow. |
I now added an elasticsearch backend to my dovecot and search returns in about a second now. :-) |
Expected behavior
I enter a search term and get some (or no) results a few seconds later
Actual behavior
After entering a search term after about 30s I get only the message "Could not open mailbox". Subsequent searches (without force reloading the page) result in the same message after only about 1-2 seconds.
Mail app
Mail app version: 1.3.2
Mailserver or service: dovecot 2.3.10
Server configuration
Operating system: Archlinux
Web server: Apache 2.4.43
Database: mariadb 10.4.12
PHP version: 7.4.5
Nextcloud Version: 18.0.3
Client configuration
Browser: Firefox 75
Operating system: Ubuntu 18.04
Logs: (the copy formatted button is broken for exactly these errors (nextcloud/logreader#301) :-/)
The text was updated successfully, but these errors were encountered: