Hi @Amber_Adamson! I don’t have a complete answer for you, but here’s the troubleshooting that I’d do if I were in your situation:
echo $PATH – Just double-checking that the path environment variable is set to what it is supposed to be set
which mongosh vs. type mongosh – Does the behavior for finding mongosh differ between bash itself and its subprocesses? (Maybe also compare with which mongo / which mongod just to be sure that those pick up the right directory)
hash -r – Clear bash’s cache for executable paths, then run mongosh again
- And finally, can you run mongosh by specifying its full path inside bash, or is it only typing the literal single word
mongosh that fails?
Finally, this is not related to troubleshooting but points to something being wrong in general:
$ mongo
BadValue: error: no args for --configdb
try ‘C:\Program Files\MongoDB\Server\6.0\bin\mongos.exe --help’ for more information
mongo and mongos are different executables, so if mongo self-identifies as mongos and reports an error that only mongos should ever really report, there’s most likely something else wrong with the MongoDB installation here as well.
1 Like