[SERVER-28965] Mongod crash with InputStreamSecureRandom failed to generate random bytes Created: 25/Apr/17 Updated: 11/Jun/20 Resolved: 21/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.5 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Davenson Lombard | Assignee: | Kelsey Schubert |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
| Comments |
| Comment by Maximus N/A [ 11/Jun/20 ] |
|
We faced this problem too in MongoDB server 3.2. Please fix it: 2020-06-09T16:23:14.205+0530 E - [conn347] InputStreamSecureRandom failed to generate random bytes , {"b":"400000","o":"F640E9"}, {"b":"400000","o":"F648F2"}, {"b":"3592000000","o":"ECA0"}, {"b":"3591800000","o":"2FFC5","s":"gsignal"}, {"b":"3591800000","o":"31A70","s":"abort"}, {"b":"400000","o":"EE1572","s":"_ZN5mongo13fassertFailedEi"}, {"b":"400000","o":"D313EC","s":"_ZN5mongo23InputStreamSecureRandom9nextInt64Ev"}, {"b":"400000","o":"709CE9","s":"_ZN5mongo11CmdGetNonce3runEPNS_16OperationContextERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderE"}, {"b":"400000","o":"7AEB93","s":"_ZN5mongo7Command3runEPNS_16OperationContextERKNS_3rpc16RequestInterfaceEPNS3_21ReplyBuilderInterfaceE"}, {"b":"400000","o":"7AFA4C","s":"_ZN5mongo7Command11execCommandEPNS_16OperationContextEPS0_RKNS_3rpc16RequestInterfaceEPNS4_21ReplyBuilderInterfaceE"}, {"b":"400000","o":"702176","s":"_ZN5mongo11runCommandsEPNS_16OperationContextERKNS_3rpc16RequestInterfaceEPNS2_21ReplyBuilderInterfaceE"}, {"b":"400000","o":"8C9815"}, {"b":"400000","o":"8CC0E6","s":"_ZN5mongo16assembleResponseEPNS_16OperationContextERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE"}, {"b":"400000","o":"578DFC"}, {"b":"400000","o":"F09E05","s":"_ZN5mongo17PortMessageServer17handleIncomingMsgEPv"}, {"b":"3592000000","o":"683D"}, {"b":"3591800000","o":"D4FCD","s":"clone"}],"processInfo":{ "mongodbVersion" : "3.2.22", "gitVersion" : "105acca0d443f9a47c1a5bd608fd7133840a58dd", "compiledModules" : [], "uname" : { "sysname" : "Linux", "release" : "2.6.18-308.el5", "version" : "#1 SMP Tue Feb 21 20:06:06 EST 2012", "machine" : "x86_64" }, "somap" : [ { "elfType" : 2, "b" : "400000" }, { "b" : "7FFF76328000", "elfType" : 3 }, { "path" : "/lib64/libssl.so.6", "elfType" : 3 }, { "path" : "/lib64/libcrypto.so.6", "elfType" : 3 }, { "path" : "/lib64/librt.so.1", "elfType" : 3 }, { "path" : "/lib64/libdl.so.2", "elfType" : 3 }, { "path" : "/lib64/libm.so.6", "elfType" : 3 }, { "path" : "/lib64/libgcc_s.so.1", "elfType" : 3 }, { "path" : "/lib64/libpthread.so.0", "elfType" : 3 }, { "path" : "/lib64/libc.so.6", "elfType" : 3 }, { "path" : "/lib64/ld-linux-x86-64.so.2", "elfType" : 3 }, { "path" : "/usr/lib64/libgssapi_krb5.so.2", "elfType" : 3 }, { "path" : "/usr/lib64/libkrb5.so.3", "elfType" : 3 }, { "path" : "/lib64/libcom_err.so.2", "elfType" : 3 }, { "path" : "/usr/lib64/libk5crypto.so.3", "elfType" : 3 }, { "path" : "/lib64/libz.so.1", "elfType" : 3 }, { "path" : "/usr/lib64/libkrb5support.so.0", "elfType" : 3 }, { "path" : "/lib64/libkeyutils.so.1", "elfType" : 3 }, { "path" : "/lib64/libresolv.so.2", "elfType" : 3 }, { "path" : "/lib64/libselinux.so.1", "elfType" : 3 }, { "path" : "/lib64/libsepol.so.1", "elfType" : 3 } ] }} |
| Comment by Kelsey Schubert [ 21/Jun/17 ] |
|
After investigation, we have been unable to reproduce this issue. A code inspection suggests this issue appears to be the result of an operating system anomaly. |