Skip to content
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

Can't connect to Mongodb 5.x #76

Closed
adityapatadia opened this issue Dec 22, 2021 · 13 comments
Closed

Can't connect to Mongodb 5.x #76

adityapatadia opened this issue Dec 22, 2021 · 13 comments
Labels
bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@adityapatadia
Copy link

I get following error in logs
Failed to create session: server returned error on SASL authentication step: BSON field 'saslContinue.mechanism' is an unknown field."

I think the problem is with old drivers.

@literakl
Copy link

literakl commented Dec 25, 2021

The mongo agent stopped working on my nodes since I upgraded Mongo from 4.4 to 5.0:

Dec 25 13:15:21 db1 newrelic-infra-service[744]: time="2021-12-25T13:15:21+01:00" level=warning msg="integration exited with error state" component=integrations.runner.Runner error="exit status 1" integration_name=nri-mongodb stderr="[WARN] Using the deprecated config ClusterName instead of MongodbClusterName\n[ERR] Failed to create session: server returned error on SASL authentication step: BSON field 'saslContinue.mechanism' is an unknown field."

@alvarocabanas alvarocabanas added bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 14, 2022
@alvarocabanas
Copy link
Contributor

Hello, thanks for raising this issue, it has been accepted and it is going to be prioritized.

@achar007
Copy link

When we can expect a fix for this bug ?

@gsanchezgavier gsanchezgavier self-assigned this Feb 2, 2022
@gsanchezgavier
Copy link
Contributor

I have reproduced this issue and I think is also related to the old driver. This should be resolved when #71 is addressed.

Did a quick check using the branch mentioned in #67 but that did not resolve the issue.

@gsanchezgavier gsanchezgavier removed their assignment Feb 4, 2022
@nscriptdotgo
Copy link

Having a similar issue, when can we expect a fix for this?

@Dgadavin
Copy link

Can you please provide the info on when this can be fixed? Thanks a lot. We really need this integration works on Mongo 5.x

@yndo97
Copy link

yndo97 commented Apr 26, 2022

The same issue. Could you please provide any ETA?

@acharbha
Copy link

is there a mongodb patch available to fix this ?

@mangulonr
Copy link
Contributor

Hi

We plan to work on update MongoDB OHI to support v5 during FY23Q2.

@pyrotechnics-io
Copy link

pyrotechnics-io commented Jun 28, 2022

Would v5 support also include SCRAM-SHA-256 auth (which has been supported on MongoDB since 4.0) ?
globalsign/mgo#282

@fingolfi
Copy link

Any chance to get it soon ?

@pyrotechnics-io
Copy link

pyrotechnics-io commented Sep 18, 2022

Any chance to get it soon ?

There is a fork that's under testing. If you're game to try it out, any bug reports are more than welcome.

It fixes several issues since it dumps mgo altogether and uses the official Go Mongodb driver.

@mangulonr
Copy link
Contributor

Hi

The new MongoDB OHI has been released in public preview, this version will be GA during June.

Some of the new features provided:

For more information check the following resources.

Because it is based on Prometheus the metric names are different from our legacy OHI, check our migration guide if you need more details.
Our legacy MongoDB OHI will be deprecated on FY24H2 (final date pending to be decided).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests