[Bug]: v28 - Receiving erroneous emails about removal from LDAP groups #42195
Comments
Caligatio
added
0. Needs triage
Have you looked into why your database server is going offline? |
This also super confuses me as it's a service running on the same VM. Much like the LDAP issue, this is a first time problem since upgrading to v28. |
|
For the group/ldap matter specifically:
Hmm. Those db connection errors are generated by the db stack - we don't even directly generate them. Anything interesting in your db server logs or server I understand the timing; that's weird. But generally that sort of thing is a local environment issue. 🤔 |
|
OK, on the DB front: I rebooted the machine within +/- 1 minute of that log so that almost definitively answers that one. I cranked up the logging for the LDAP issue... now I just need to wait <= 65 minutes. |
|
I've disabled my email as it was spamming affected users but there's now this: I only have two groups so this is the whole list. It looks like I'm also suffering from #42158 |
|
More logs but still nothing clear why this is happening: |
|
I have exactly the same problem. |
|
@systemofapwne Where did you find that notification setting? I ended up just invalidating my SMTP config EDIT: Turns out I'm also bit by nextcloud/logreader/issues/1073, found the setting! |
Here you go:
|
|
Yet, I emphasize, this is just a workaround for the bug (that has no other impact but the email spam). It might be related to the LDAP plugin, but I'm not 100% sure, since it just happened after the recent NC update. |
|
@joshtrichards Anything else I can do to help troubleshoot this? I happen to check the activity feed in my Nextcloud Windows client and I'm getting dozens of these events each day. |
|
The same thing is happening to me since I upgraded from 27 to 28 this morning ! I am using LDAP, MariaDB and encryption. |
|
Same here, my users are spammed by multiple emails about their removal from a ldap group, immediatly after updating my nextcloud instance from 27 to 28. Openldap as users/groups backend. |
|
Same issue upgrading to 28.0.1. I have errors like these in logs that may be related : Duplicate entry '[redacted group]-[redaxcted username' for key 'user_ldap_membership_unique' |
|
In my case, updating to nc 28 seems to have alterate the user to group ldap mapping. See this post which solved my problem: |
I just noticedm that my groups also were all empty. Switching that setting to "memberUid" populated my groups. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
For people having this issue, I think the problem is indeed a misconfigured group association attribute. For the misconfigured group membership, I’m sure what could be done to help people testing and configuring that. |
Any example of such a misconfiguration ? I how no idea on how to fix it. The configuration is rather simple and done with the UI |
The |
|
@come-nc Thanks ! I went in LDAP advanced settings and changed the |
Bug description
Since upgrading to v28 yesterday, my users have been receiving emails at seemingly random intervals saying that "An administrator removed you from group ". The groups in question are LDAP based groups, absolutely no edits have been performed, and the users are actually still members of the group when viewed in the Nextcloud interface. This setup has been stable for months and I haven't received these sorts of messages previously.
Steps to reproduce
Unknown at this time other than to be using LDAP and upgrading to v28.
Expected behavior
Not to receive emails about being removed from a group.
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
{ "system": { "instanceid": "***REMOVED SENSITIVE VALUE***", "passwordsalt": "***REMOVED SENSITIVE VALUE***", "secret": "***REMOVED SENSITIVE VALUE***", "trusted_domains": [ "nextcloud.REDACTED_INTERNAL_DOMAIN", "nextcloud.REDACTED_EXTERNAL_DOMAIN" ], "trusted_proxies": "***REMOVED SENSITIVE VALUE***", "datadirectory": "***REMOVED SENSITIVE VALUE***", "dbtype": "mysql", "version": "28.0.0.11", "overwrite.cli.url": "https:\/\/nextcloud.REDACTED_EXTERNAL_DOMAIN", "dbname": "***REMOVED SENSITIVE VALUE***", "dbhost": "***REMOVED SENSITIVE VALUE***", "dbport": "", "dbtableprefix": "oc_", "mysql.utf8mb4": true, "dbuser": "***REMOVED SENSITIVE VALUE***", "dbpassword": "***REMOVED SENSITIVE VALUE***", "installed": true, "memcache.local": "\\OC\\Memcache\\Redis", "memcache.distributed": "\\OC\\Memcache\\Redis", "memcache.locking": "\\OC\\Memcache\\Redis", "mail_smtpmode": "smtp", "mail_smtpauth": 1, "mail_smtpauthtype": "LOGIN", "mail_smtphost": "***REMOVED SENSITIVE VALUE***", "mail_from_address": "***REMOVED SENSITIVE VALUE***", "mail_domain": "***REMOVED SENSITIVE VALUE***", "mail_smtpsecure": "ssl", "mail_smtpport": "465", "mail_sendmailmode": "smtp", "mail_smtpname": "***REMOVED SENSITIVE VALUE***", "mail_smtppassword": "***REMOVED SENSITIVE VALUE***", "loglevel": 3, "defaultapp": "files", "redis": { "host": "***REMOVED SENSITIVE VALUE***", "port": 6379, "timeout": 0 }, "default_phone_region": "US", "ldapProviderFactory": "OCA\\User_LDAP\\LDAPProviderFactory", "account_manager.default_property_scope": { "displayname": "v2-local", "email": "v2-local", "avatar": "v2-local", "address": "v2-private", "website": "v2-private", "phone": "v2-private", "twitter": "v2-private", "fediverse": "v2-private", "organisation": "v2-private", "role": "v2-private", "headline": "v2-private", "biography": "v2-private", "profile_enabled": "v2-private" }, "maintenance": false, "theme": "", "updater.secret": "***REMOVED SENSITIVE VALUE***" } }List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
The frequency of the activity emails is every 65 minutes or not at all. For instance, I got them at 2000, 2105, 2210, and 2315 but then nothing for the next ~9 hours until now.
The text was updated successfully, but these errors were encountered: