Server: Deprecated event type for OCA\User_LDAP\User\User::postLDAPBackendAdded: null

Created on 23 Jan 2020 · 19Comments · Source: nextcloud/server

After 18.0.0, my log is being flooded with LDAP logs like these.

Info | user_ldap | Cannot determine UUID for cn=W,ou=Z,dc=Y,dc=X. Skipping. 
Error | user_ldap | Could not autodetect the UUID attribute
Info | no app in context | Deprecated event type for OCA\User_LDAP\User\User::postLDAPBackendAdded: null

I had no errors like these on 17.0.2.

2. developing bug

Source

jsalatiel

Most helpful comment

same here for version 19

joergmschulz on 18 Jun 2020

👍5

All 19 comments

also experiencing it on 18.0.0.10, and log is clean once i locally apply #19118.

landryb on 24 Jan 2020

@rullzer should this issue (and #18331) be fixed now that #19118 has been merged ? locally deploying stable18 branch doesnt display the msg in logs anymore. Or issues are closed only when a release is available from the stable branch..

landryb on 30 Jan 2020

The error "[user_ldap] Error: Could not autodetect the UUID attribute" also floods my logs after upgrading from 17.0.2 to 17.0.3.

There is also a thread in the forum here

patrick1990 on 6 Feb 2020

👍3

I agree with @patrick1990 - This issue appeared right after upgrading from 17.0.2 to 17.0.3 and is bombarding the log with these entries.

In the mentioned forum thread, a user found that using the old app user_ldap from 17.0.2 fixes the log flooding. I guess this could be used as a workaround but there should be a proper fix.

HigH-HawK on 6 Feb 2020

Could not autodetect the UUID attribute flooding on 18.0.1 too.

corincorvus on 11 Mar 2020

After upgrading to 18.0.3, it seems that the flooding has stopped.

A user on the forums mentioned, that the log entries keep appearing after upgrading, only for groups being added after the upgrade though.

HigH-HawK on 3 Apr 2020

Upgraded to 18.0.3 from 17.0.2 and still get messages Deprecated event type for OCA\User_LDAP\User\User::postLDAPBackendAdded: null.

Nextcloud shows it as DEBUG messages and it can be hidden by setting 'loglevel' => 2 in config.php, but the root of the problem is still there, at least in my case.

galichenkosemyon on 15 Apr 2020

fresh install 18.0.3
log is flooded with this message
around 500Mb a day

https://youtu.be/m23u-16_bt0

do-d1 on 16 Apr 2020

After upgrading to 18.0.3, it seems that the flooding has stopped.

A user on the forums mentioned, that the log entries keep appearing after upgrading, only for groups being added after the upgrade though.

I cannot confirm this. We just performed the upgrade from 17.0.3 to 18.0.3 and are also seeing tons of Deprecated event type for OCA\User_LDAP\User\User::postLDAPBackendAdded: null. messages.
We have sort of a mixed user account situation here. Individual user accounts are Active Directory based, thus we're using the LDAP connector. When it comes to "group" accounts (more than one person is using this account, normally with the Windows NextCloud Client) we do not hold these specific accounts in the Active Directory.

It does not make any difference to our NextCloud instance wether the groups accounts have been created prior or after the upgrade.

As the above mentioned errors are only showing up in conjunction with non-ldap/AD-, yet local nextcloud accounts, I figure, that whatever function is checking whatever (sorry, I haven't really taken a look into the sources yet) and thereby stumbling over the fact, that some accounts are no present in the LDAP-Backend, these messages are being generated.

I have the feeling that there might not be any other side-effects other than flooding and jamming the log file, but it's sure worth fixing :)