org.springframework.data.mongodb.UncategorizedMongoDbException

could not initialize sharding on connection 54.xx.xx.198:27017 :: caused by :: mongos specified a different config database string : stored : 54.xx.xx.55:27019 vs given : 54.xx.xx.249:27019; nested exception is com.mongodb.MongoException: could not initialize sharding on connection 54.xx.xx.198:27017 :: caused by :: mongos specified a different config database string : stored : 54.xx.xx.55:27019 vs given : 54.xx.xx.249:27019

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web31

  • via Ask Ubuntu by Rahul
    , 9 months ago
    could not initialize sharding on connection 54.xx.xx.198:27017 :: caused by :: mongos specified a different config database string : stored : 54.xx.xx.55:27019 vs given : 54.xx.xx.249:27019; nested exception is com.mongodb.MongoException: could
  • not talking to master and retries used up; nested exception is com.mongodb.MongoException: not talking to master and retries used up The stacktrace is here: Caused by: com.mongodb.MongoException: not talking to master and retries used up
  • via Stack Overflow by user1493140
    , 1 year ago
    not authorized for query on alphasaverdev.student; nested exception is com.mongodb.MongoException: not authorized for query on alphasaverdev.student
  • Stack trace

    • org.springframework.data.mongodb.UncategorizedMongoDbException: could not initialize sharding on connection 54.xx.xx.198:27017 :: caused by :: mongos specified a different config database string : stored : 54.xx.xx.55:27019 vs given : 54.xx.xx.249:27019; nested exception is com.mongodb.MongoException: could not initialize sharding on connection 54.xx.xx.198:27017 :: caused by :: mongos specified a different config database string : stored : 54.xx.xx.55:27019 vs given : 54.xx.xx.249:27019 at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:133)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.