-
Notifications
You must be signed in to change notification settings - Fork 30
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
Fulltextindex fail with Exeption #6
Comments
Is it still failing with 0.7 ? |
I am seeing what looks like the exact same issue. Versions:
This is a very old installation which has been updated from an owncloud.
|
could it be that that user never logged in your Nextcloud ? |
Yes - that is possible. Looks like the user(s) where I am hitting this are actually users which are marked by the system as ldap remnants. |
I have worked around this by changing Line 1922 from View.php to:
|
can you reverse your edit and try this: |
Should be fixed in 0.8.0 |
Please re-open this report if issue is not fixed |
I am still running into this issue on NC 13.0.6(.1) and fulltextsearch_files 0.99.4:
I checked the user account in NC and it states this:
Indexing reliably stops at that account. |
Okay, the issue has been that NC wasn't able to read the user's homedirectory setting from AD. I removed the setting in LDAP/AD config from the advanced preferences and right now, I am giving it another try. I have a gutt-feeling, that this will resolve the issue. |
I don't know if it helps, but it resolved my problem. The indexing process stumbled upon users that where not member of AD-goups anymore(ex-employees) but still had shares active in de OC_SHARE table on the database server(I use Mariadb) . I rudely removed those lines from the table using SQL(HeidiSQL) filtering on those usernames and found the indexing process continued successfully. More detailed explanation is welcome. |
I should have a look to the source, but the version of fulltextsearch for nc14 should not crash on Throwable, meaning that even if there is an issue like this during a scan, it should just go on with the next file, |
Could it be that although the message as shown in this issue the indexing process still continues but progress indicator is not shown on the console anymore? Anyhow my initial indexing has finished yesterday after a it ran for several hours and finally works in Nextcloud. So I'm glad it worked out for me. NC 14.0.3 |
Hello,
I using this fine App with several Servers. On one Server I've got an exeption during:
sudo -u www-data php ./occ fulltextsearch:index
I already tried to use
But the exeption comes again:
The text was updated successfully, but these errors were encountered: