-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 1.6.0
-
Component/s: Telemetry Data
-
None
-
Environment:K8s pod - mongosh vs mongo
-
Not Needed
-
Iteration Porpoise
The output below illustrates the issue. Running monosh in a k8s pod crashes.
mongo (obsolete) works ok.
—
I have no name!@mysharded-mongos-0:/var/lib/mongodb-mms-automation/mongosh-1.6.0-linux-x64/bin$ ./mongosh '
[mongodb://dbAdmin:Mongodb1@mysharded-mongos-0.mysharded-svc.mongodb.svc.cluster.local:27017/?authMechanism=SCRAM-SHA-256&authSource=admin&connectTimeoutMS=20000&serverSelectionTimeoutMS=20000&ssl=true&tls=true]
' --tls --tlsCAFile /mongodb-automation/tls/ca/ca-pem --tlsCertificateKeyFile /mongodb-automation/tls/FRLUT2VTL3PMDKLVSR5AZ7I6V77HGYWUZLSCRQ7G44AAN6GE6ZOA
Warning: Could not access file: ENOENT: no such file or directory, mkdir '/.mongodb'
Current Mongosh Log ID: 6366f9d00bc57dbbfef9fb97
Connecting to: mongodb://<credentials>@mysharded-mongos-0.mysharded-svc.mongodb.svc.cluster.local:27017/?authMechanism=SCRAM-SHA-256&authSource=admin&connectTimeoutMS=20000&serverSelectionTimeoutMS=20000&ssl=true&tls=true&directConnection=true&tlsCAFile=%2Fmongodb-automation%2Ftls%2Fca%2Fca-pem&tlsCertificateKeyFile=%2Fmongodb-automation%2Ftls%2FFRLUT2VTL3PMDKLVSR5AZ7I6V77HGYWUZLSCRQ7G44AAN6GE6ZOA&appName=mongosh+1.6.0
Using MongoDB: 5.0.9
Using Mongosh: 1.6.0
For mongosh info see:
https://docs.mongodb.com/mongodb-shell/
To help improve our products, anonymous usage data is collected and sent to MongoDB periodically (
https://www.mongodb.com/legal/privacy-policy
).
You can opt-out by running the disableTelemetry() command.
Error: Could not open history file.
REPL session history will not be persisted.
AssertionError: You must pass either an "anonymousId" or a "userId".
- is duplicated by
-
MONGOSH-1252 mongosh fails to start if reading config file fails
- Closed