lenra-io / lenra-io/server

[Bug]: MongoDB connection error throw randomly

Open
#561 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Elixir
Stars
6
Forks
0
PR merge metrics
No merged PRs in 30d

Description

What happened?

Sometimes, there a mongodb connection error that got thrown randomly when accessing Lenra server using app.lenra.io
We got that error multiple times a day, but not every days.

Mostly always thrown after this error :

auth failed for user root: Authentication failed. 18

We need to check mongo logs before going futher.

What browsers are you seeing the problem on?

No response

Version

1.5.3

Relevant log output
GenStateMachine #PID<0.3811.0> terminating
** (exit) exited in: GenServer.call(#PID<0.3727.0>, :get, 5000)
    ** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
    (elixir 1.13.4) lib/gen_server.ex:1030: GenServer.call/3
    (mongodb_driver 1.2.1) lib/mongo/auth.ex:34: Mongo.Auth.credentials/1
    (mongodb_driver 1.2.1) lib/mongo/auth.ex:20: Mongo.Auth.run/2
    (mongodb_driver 1.2.1) lib/mongo/mongo_db_connection.ex:114: Mongo.MongoDBConnection.connect/2
    (db_connection 2.6.0) lib/db_connection/connection.ex:92: DBConnection.Connection.handle_event/4
    (stdlib 3.17.2.4) gen_statem.erl:1205: :gen_statem.loop_state_callback/11
    (stdlib 3.17.2.4) proc_lib.erl:236: :proc_lib.wake_up/3
State: Mongo.MongoDBConnection
Callback mode: :handle_event_function
Postponed events: []
Last event: {:internal, {:connect, :disconnect}}
Queued events: []
State: Mongo.MongoDBConnection

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking MongoDB logs around the reported authentication failure, then trace the connection path shown in the stack trace through mongodb_driver and DBConnection. Done means identifying the cause of the intermittent connection error and confirming a reliable fix against the reported failure sequence.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir, mongodb
Domain
database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.