-
Notifications
You must be signed in to change notification settings - Fork 51
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
Error indexing getUID() null #697
Error indexing getUID() null #697
Comments
I'm facing the same issue with NC24, fulltextsearch 24 and php7.4. Not sure whether following info might be relevant: |
While testing I tried to focus on the path which thows the mentioned "getUID() on null" error. For example: Doing this, I don't get an error msg, but the index keeps running in background, even though the indexing seems to be finished: Doing the same for a path which is not affected by this issue, index does not keep running in background after it was finished. Any chance that this issue was triggered during "migration:24"? Rebuilding the index took a week last time. I'm afraid that a reset of the index won't fix the issue and that I'm stuck without a working index. |
Same here with updated NC24, fulltextsearch 24, nginx and php8.0. Resetting the index did not work for me, nor did reinstalling elasticsearch. |
I was able to rebuild the index after changing the line https://github.com/nextcloud/files_fulltextsearch/blob/40254a35e8e2650d010f96c88d6bb96ed8df16e5/lib/Service/FilesService.php#L449 original:
modified:
|
On the first view this was introduced with nextcloud/files_fulltextsearch#146 |
@priiduonu 's solution seems to work for me. many thanks! |
I am not able to reproduce the issue, do you have any details on the files that is generating this issue ? is the filesystem local ? is it a specific type of file ? were you able to catch the |
My filesystem is external, mounted via SFTP. But I also disabled indexing external files and group folders, the results were the same as the OP described. I'm not sure if it was a specific type or certain file, too late for that :-) |
I'm using a local filesystem, groupfolders (indexing enabled) and external (smb, indexing path only).
As previously mentioned. I created the initial index on NC23. Now it fails after updating to NC24. indexing:
document info:
error message:
@ArtificialOwl just let me know which additional info you need! |
Same here with Nextcloud 24.0.0 in the official docker container. Would be glad to see a fix.. or at least understand what causes the problem. |
Not sure if that helps: I just noticed that the above error occured in my case when fulltextsearch was indexing files for the Account "bridge-bot". I had been experimenting with talk bridges and abviously that account was created than, but I never really used it. I deleted that acount manually, and now indexing sees to run.. ok stopped with another error somewhat later, but that is a different one. |
I'm still trying to understand the cause of this issue. I now started to delete all files/folders which causes this issue. Finally this error still appears but I don't see a reference to an actual file!?
Error:
|
I'm now able to reproduce the issue! After disabling the external SMB/CIFS storage, the issue did not appear again. The other way around, enabling a SMB/CIFS storage for an account which was not affected so far, does cause this issue! I was able to reproduce this behaviour on all three nextcloud instances running latest NC24.0.1. Would be great if someone could double check if the external storage is the root cause! @ArtificialOwl: Any idea how to prevent this error if an external storage is available? |
So i tried add SMB/CIFS external storage mount to new created user, the error happen. And can confirm this is related to external storage handling, the options disable external storage scan also not working? as i uncheck it but it still try to scan external storage? 🤔 Edit: i got |
I don't have external storages, but saw the error as well. |
Good findings! I use local type external storage on all my instances and can't get around this ... so any hotfix is appreciated. |
This should fix it, if you are willing to patch |
Thanks a lot! |
Confirmed fix on |
it also works on my side. many thanks! |
Closed, look nextcloud/files_fulltextsearch#170 |
Nextcloud 24 , PHP 8.0, fulltextsearch 24.0.0, already do migration
occ fulltextsearch:migration:24
index already running
Should it stop index or just let it run,i assume it keep run in background?
Edit:
The text was updated successfully, but these errors were encountered: