[SERVER-37119] try to connect version 3.6.4 with client version 4.0.2 Created: 13/Sep/18 Updated: 16/Nov/21 Resolved: 18/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | lee mingyu | Assignee: | Nick Brewer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | ---------------- ---------------- ---------------- -------------------------------- -------------------------------- 2018-09-13T21:46:13.118+0900 I NETWORK [conn1691] received client metadata from xxxxx conn1691: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "4.0.2" }, os: { type: "Linux", name: "CentOS release 6.5 (Final)", architecture: "x86_64", version: "Kernel 2.6.32-642.6.2.el6.x86_64" } } 0x562d48601b71 0x562d48600d89 0x562d486013f6 0x7f8a6bb975e0 0x562d47f09403 0x562d47024f4c 0x562d47028a24 0x562d47029777 0x562d47035faa 0x562d47031957 0x562d47034d91 0x562d47f36092 0x562d470307bf 0x562d47032d05 0x562d470335fb 0x562d470319dd 0x562d47034d91 0x562d47f365f5 0x562d484cb194 0x7f8a6bb8fe25 0x7f8a6b8bd34d ,{"b":"562D46423000","o":"21DDD89"},{"b":"562D46423000","o":"21DE3F6"},{"b":"7F8A6BB88000","o":"F5E0"},{"b":"562D46423000","o":"1AE6403","s":"_ZN5mongo30initializeOperationSessionInfoEPNS_16OperationContextERKNS_7BSONObjEbbb"},{"b":"562D46423000","o":"C01F4C"},{"b":"562D46423000","o":"C05A24"},{"b":"562D46423000","o":"C06777","s":"_ZN5mongo23ServiceEntryPointMongod13handleRequestEPNS_16OperationContextERKNS_7MessageE"},{"b":"562D46423000","o":"C12FAA","s":"_ZN5mongo19ServiceStateMachine15_processMessageENS0_11ThreadGuardE"},{"b":"562D46423000","o":"C0E957","s":"_ZN5mongo19ServiceStateMachine15_runNextInGuardENS0_11ThreadGuardE"},{"b":"562D46423000","o":"C11D91"},{"b":"562D46423000","o":"1B13092","s":"_ZN5mongo9transport26ServiceExecutorSynchronous8scheduleESt8functionIFvvEENS0_15ServiceExecutor13ScheduleFlagsENS0_23ServiceExecutorTaskNameE"},{"b":"562D46423000","o":"C0D7BF","s":"_ZN5mongo19ServiceStateMachine22_scheduleNextWithGuardENS0_11ThreadGuardENS_9transport15ServiceExecutor13ScheduleFlagsENS2_23ServiceExecutorTaskNameENS0_9OwnershipE"},{"b":"562D46423000","o":"C0FD05","s":"_ZN5mongo19ServiceStateMachine15_sourceCallbackENS_6StatusE"},{"b":"562D46423000","o":"C105FB","s":"_ZN5mongo19ServiceStateMachine14_sourceMessageENS0_11ThreadGuardE"},{"b":"562D46423000","o":"C0E9DD","s":"_ZN5mongo19ServiceStateMachine15_runNextInGuardENS0_11ThreadGuardE"},{"b":"562D46423000","o":"C11D91"},{"b":"562D46423000","o":"1B135F5"},{"b":"562D46423000","o":"20A8194"},{"b":"7F8A6BB88000","o":"7E25"},{"b":"7F8A6B7C5000","o":"F834D","s":"clone"}],"processInfo":{ "mongodbVersion" : "3.6.4", "gitVersion" : "d0181a711f7e7f39e60b5aeb1dc7097bf6ae5856", "compiledModules" : [], "uname" : { "sysname" : "Linux", "release" : "3.10.0-693.21.1.el7.x86_64", "version" : "#1 SMP Wed Mar 7 19:03:37 UTC 2018", "machine" : "x86_64" }, "somap" : [ { "b" : "562D46423000", "elfType" : 3, "buildId" : "9E8992AF64DDDA5CD452F1A1FFBB558210B8AD34" }, { "b" : "7FFFF5EA1000", "elfType" : 3, "buildId" : "228ADFE0D8C0852BF24F80B24803DA9E25F5B21E" }, { "b" : "7F8A6C6C8000", "path" : "/lib64/libresolv.so.2", "elfType" : 3, "buildId" : "FF4E72F4E574E143330FB3C66DB51613B0EC65EA" }, { "b" : "7F8A6C4C0000", "path" : "/lib64/librt.so.1", "elfType" : 3, "buildId" : "6D322588B36D2617C03C0F3B93677E62FCFFDA81" }, { "b" : "7F8A6C2BC000", "path" : "/lib64/libdl.so.2", "elfType" : 3, "buildId" : "1E42EBFB272D37B726F457D6FE3C33D2B094BB69" }, { "b" : "7F8A6BFBA000", "path" : "/lib64/libm.so.6", "elfType" : 3, "buildId" : "808BD35686C193F218A5AAAC6194C49214CFF379" }, { "b" : "7F8A6BDA4000", "path" : "/lib64/libgcc_s.so.1", "elfType" : 3, "buildId" : "C344A7E6783B19A5C763AC24746EC6BAD2607F28" }, { "b" : "7F8A6BB88000", "path" : "/lib64/libpthread.so.0", "elfType" : 3, "buildId" : "A48D21B2578A8381FBD8857802EAA660504248DC" }, { "b" : "7F8A6B7C5000", "path" : "/lib64/libc.so.6", "elfType" : 3, "buildId" : "95FF02A4BEBABC573C7827A66D447F7BABDDAA44" }, { "b" : "7F8A6C8E2000", "path" : "/lib64/ld-linux-x86-64.so.2", "elfType" : 3, "buildId" : "22FA66DA7D14C88BF36C69454A357E5F1DEFAE4E" } ] }}
|
||||||||
| Participants: | |||||||||
| Description |
|
I try to connect mongod with mongo shell but I connected and mongo was down in no time
|
| Comments |
| Comment by lee mingyu [ 19/Sep/18 ] | ||||||||||
|
thank you for helping | ||||||||||
| Comment by Nick Brewer [ 18/Sep/18 ] | ||||||||||
|
ee400 I believe the issue you're describing is a duplicate of: As that ticket notes, the behavior of starting a mongod with --shardsvr directly, outside of a sharded cluster, is not the intended use-case for that option. However the underlying bug that results in a crash has been fixed in version 3.6.5. While the usage you've described is not the intended one, if this is something you need I suggest upgrading your 3.6 nodes to version 3.6.8. -Nick | ||||||||||
| Comment by lee mingyu [ 18/Sep/18 ] | ||||||||||
|
and I have the same option in mongo 3.6.5 but this server is not down when I connect to that with 4.0.2 shell | ||||||||||
| Comment by lee mingyu [ 18/Sep/18 ] | ||||||||||
|
and I have the same option in mongo 3.4.4 but this server is not down when I connect to that with 4.0.2 shell | ||||||||||
| Comment by lee mingyu [ 18/Sep/18 ] | ||||||||||
|
in spite of replica set I used this option "sharding": { "clusterRole": "shardsvr" }so I remove and restart and retest, I am not able to reproduce I have experienced some of the trouble (with sharding XXXXX option in replica set) | ||||||||||
| Comment by lee mingyu [ 18/Sep/18 ] | ||||||||||
|
this is output { }, , , , , , , , , } },
and I executed db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } ) ,
| ||||||||||
| Comment by Nick Brewer [ 14/Sep/18 ] | ||||||||||
|
ee400 6 / 6Server is a RedHat convention, it is explained in greater detail here (under the "Red Hat Software Repositories" heading). I haven't been able to recreate this in my testing with a 3.6.4 server and a 4.0.2 shell:
I'll need the getCmdLineOpts output to get a more accurate reproduction. -Nick | ||||||||||
| Comment by lee mingyu [ 14/Sep/18 ] | ||||||||||
|
to be honest I manage a variety of versions
I tested connection "/usr/bin/mongo HOST:PORT/admin -u dba -p'XXX' --quiet --eval "db.serverStatus().opcounters" with 4.0.2 in all above 3.0 version
| ||||||||||
| Comment by lee mingyu [ 14/Sep/18 ] | ||||||||||
|
I do not test yet, I think there is no worthy for testing because I have managed variety mongo versions, I can not completely use same MongoDB shell version with MongoDB version I have a question 2) you can meet the same error if you test (connect to 3.6.4 mongod with 4.0.2 mongo shell)
| ||||||||||
| Comment by Nick Brewer [ 13/Sep/18 ] | ||||||||||
|
ee400 Thanks for your report. I'm curious to know if you encounter this issue when using the same (3.6.4) shell version? Additionally, it would be useful to see the output of:
Thanks, |