Error Log through LDAP Sync

Community Support
1

Description

Hello together,

I am writing because we have a problem with our instance that we have connected our Rocketchat to an LDAP server. Everything works fine so far and the login has been working for several months.
Now we have noticed the following error:
{“level”:50,“time”:“2025-02-17T15:13:18.143Z”,“pid”:1,“hostname”:“rocketchat”,“name”:“LDAP”,“err”:{“type”:“Error”,“message”:“User not found”,“stack”:“Error: User not found\n at Function.findUser (server/lib/ldap/Manager.ts:203:11)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at Function.login (server/lib/ldap/Manager.ts:35:16)\n at packages/accounts-base/accounts_server.js:593:9\n at tryLoginMethod (packages/accounts-base/accounts_server.js:1560:14)\n at AccountsServer._runLoginHandlers (packages/accounts-base/accounts_server.js:592:22)\n at AccountsServer.Accounts._runLoginHandlers (app/lib/server/lib/loginErrorMessageOverride.ts:9:17)\n at MethodInvocation.methods.login (packages/accounts-base/accounts_server.js:654:22)”},“msg”:“User not found”}

That the user is not found in the LDAP is correct because it is a local user and this user can also log in. It is not an alternative that he becomes an LDAP user.
The whole thing also writes this in the log, is there a way to ignore this explicit error message or to hide it so that it is no longer visible in the log?

Thanks you!
Max

Server Setup Information

  • Version of Rocket.Chat Server: 7.2.1
  • Operating System: Alma 9
  • Deployment Method:
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:
  • Proxy:
  • Firewalls involved:

Any additional Information

2

Probably just set logging to info, not debug.

It is just noise, and presumably it’s happened for some time without you noticing. Nothing is broken.

3

It is already on info, that’s my problem.

4

I think the problem is not using the system the way it is intended.

You should either authenticate with Rocket, or with LDAP.

You are trying to run both. Note this:

Screenshot_2025-02-24_11-03-05
Screenshot_2025-02-24_11-03-05758×189 13.5 KB

It will allow you a fallback to local user login, but is designed to do that ONLY in the event of a LDAP failure. Not day to day use.

You might try messing with a few settings to see:

Screenshot_2025-02-24_11-00-12
Screenshot_2025-02-24_11-00-12692×247 9.01 KB

However, the real answer is use one auth method only.

Or ignore the noise - it is trying to warn you for a reason.

5

Thank you for your help!

6

NP.

I know it isn’t necessarily the answer you want, but it is the answer nonetheless… !