-
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
[Bug]: NoUserException
Backends provided no user object
#292
Comments
For LDAP remnants, see: |
Thank you very much for the link, but unfortunately the
|
How do I find the records in the DB causing this error messages? Maybe deleting or updating the records triggering the message in the DB directly helps getting rid of these recurring messages for non-existing users. Sometimes the object is referred to with an UUID, sometimes with username the user had as it existed.
|
NoUserException
Backends provided no user object
@joshtrichards is there any progress on this topic, or where can I follow the progress, maybe even contribute by adding information? |
Hi, I have a similar situation, where the log is getting inundated with the "NoUserException Backends provided no user object" error message. The user in question was an LDAP user, which was deleted from LDAP, and then deleted from Nextcloud, as per the manual https://docs.nextcloud.com/server/29/admin_manual/configuration_user/user_auth_ldap_cleanup.html. At present the command ldap:show-remnants command displays nothing. How can I solve this? |
Yes I do have files_fulltextsearch app installed, and seems that is where the error is comming from. { |
FTS may need a similar fix as nextcloud/server#41786 made for |
I also have this app installed, but do not see why this app in the report stands out more then others (just being curious)? Second, this app is not to be trusted @joshtrichards ? Last, it was very difficult to find the source of this problem, how can I help for users simular to me, looking for answers? Thanks both for the earlier and future responses! Roelof |
Ehh, what am I doing wrong? `user@nas:/opt/nextcloud# ./ncocc.sh app:enable files_fulltextsearch
|
Hi everyone,
My Nextcloud instance has 4 users, so not a lot of files. Be careful on large instances. |
Unverified take: It seems we need to either:
There is already a listener for when files are deleted AFAIK. I would have expected this would catch these situations (once the user's files after account removal), but maybe not. |
Reindexing now, big thanks for that, seems a logical solution, my setup is also small (but I like to think enterprise-like, so this is not the best workaround). |
nextcloud/server#47896 might be relevant here. |
I have the system in production, I wanted to avoid reindexing, it takes 2 / 3 days. |
Bug description
After enabling the LDAP backend, logging in with a user of LDAP, removing the necessary group for login in LDAP and then removing the LDAP backend from Nextcloud causes the user to stay somehow in the system which causes flooding of the log with messages like this:
How do I get rid of this non-existing user
testuser_2438
?Steps to reproduce
testuser
_<number>
postfixedExpected behavior
The really expected behaviour would be to join existing and ldap users as soon as
Internal Username
corresponds to the username and isn't UID.After having learned the LDAP backend can't do it, the expected behavior is:
Deleting users deletes them really - no matter which backend added the user.
Installation method
Official All-in-One appliance
Nextcloud Server version
29
Operating system
RHEL/CentOS
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 28.0.1 to 28.0.2)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: