[SERVER-35399] MongoDB Server not received client metadata Created: 05/Jun/18 Updated: 23/Jul/18 Resolved: 15/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, WiredTiger |
| Affects Version/s: | 3.4.0 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Sandeep [X] | Assignee: | Nick Brewer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Dear Team, A critical issues observed at our side. MongoTimeoutException is occurring even when DB is running!! we observed that MOngoServer didnt receive any metadata from the client-172.29.105.17. Note: Both Client and MOngoServer are running on same Machine Detailed Scenario is described below As observed from the MongoDB logs on 1st may 2018
on 12th may 2018
Please let us know Why DB Operations is not successful in above said scenario?? Thanks & Regards Sandeep KS
|
| Comments |
| Comment by Nick Brewer [ 20/Jun/18 ] | ||
|
Sandeep, The error you're receiving indicates that the client is not able to reach the the mongod:
It looks like you have both the client and the mongod running on the same Windows machine. One thing that sticks out here is that it appears that you were previously starting mongod on port 8090, however the getCmdLineOpts output you provided suggests that it is configured to listen on port 8099 - if you've changed the port that it's set to listen on, have you updated the command you're using to connect the client as well? Before you attempt to connect the client, try using the following command to confirm that mongod is listening on the desired port:
The use of readPreference=primary indicates that you're using a replica set - if this is the case, could you please attach the full output of rs.conf()? Also, what happens if you change your read preference to readPreference=primaryPreferred ? Finally, it would be helpful to see the full command that you're using to attempt to connect to the mongod and perform CRUD operations, along with any logs from:
You may need to remove the quiet: true setting for more verbose logging of failed connections. Nick | ||
| Comment by Sandeep [X] [ 20/Jun/18 ] | ||
|
Dear Nick, Thank you for the support! I agree with you that quiet: true option will suppress "Connection received" but this will not suppress "received client metadata". This bug/ticket Rather this ticket is about why the Client is not able to perform any CURD Operations while MongoDB Server is running !! Note: I have Posted the same ticket in mongodb-user-group as well https://groups.google.com/forum/#!topic/mongodb-user/vPCZcJT8toU Hence Please let us know Why DB Operations is not successful in above said scenario?? Thanks & Regards Sandeep KS | ||
| Comment by Nick Brewer [ 14/Jun/18 ] | ||
|
Hi, You're running mongod with the "quiet" : true option, which suppresses "connection received" and "end connection" messages, but does not currently suppress "received client metadata" messages. We're working on fixing this behavior to include those messages, and the relevant ticket for that change had been attached to this one. In the instances where you're not seeing the "received client metadata" notifications, the cause is most likely that the client is failing to connect altogether - however this wouldn't be related to any inability on the part of the mongod server to accept client metadata. If you are running into an issue connecting to your mongod install, I'd suggest making a post on the mongodb-user group or Stack Overflow with the mongodb tag. Regards, | ||
| Comment by Sandeep [X] [ 14/Jun/18 ] | ||
|
Dear Nick, I have attached the request command output .<<db.adminCommandOutput-10062018.json Let us any other information required if any to facilitate your support db.adminCommandOutput-10062018.json Thanks & Regards Sandeep KS | ||
| Comment by Nick Brewer [ 13/Jun/18 ] | ||
|
Hi, We'd like to see the output of the following command:
This will let us evaluate the settings that are being passed to mongod on startup. Since this is a public project, feel free to redact any hostnames or other sensitive information, but please leave the configuration options intact. Thanks, | ||
| Comment by Jeffrey Yemin [ 12/Jun/18 ] | ||
|
Yes, it was added in 3.4.0 in scope of Is there any evidence that the application was able to establish a connection the server at all, let alone include client metadata as part of the isMaster command that the driver sends after successfully connecting? | ||
| Comment by Mark Benvenuto [ 12/Jun/18 ] | ||
|
jeff.yemin Does the Java Driver version 3.4.0 send client metadata to the server? | ||
| Comment by Sandeep [X] [ 12/Jun/18 ] | ||
|
Dear Mark, Please find details as below:
Please let us know if you need any other information Thanks & Regards Sandeep KS
| ||
| Comment by Mark Benvenuto [ 11/Jun/18 ] | ||
|
Dear Sandeep, What driver and version are using to connect to MongoDB? Which version of MongoDB are you using? Thanks Mark | ||
| Comment by Sandeep [X] [ 11/Jun/18 ] | ||
|
Dear Team, Please let us know Why DB Operations is not successful When MongoDB Server was unable to received client metadata message as observed from the MongoDB Logs.!! Note: MongoDB Server is running in the above said case ** Also I have posted a query as below https://groups.google.com/forum/#!topic/mongodb-user/vPCZcJT8toU
Thanks & Regards Sandeep KS | ||
| Comment by Sandeep [X] [ 06/Jun/18 ] | ||
|
Dear Team, May I request MongoDB Team to provide us the support for the above said Issue please...? Thanks & Regards Sandeep KS |