![]() You said you nuked /var/lib/mongo, but are you certain its empty? IF you're OK that there's no data in that directory, nuke it again. ![]() To change the storage.directoryPerDB option for existing deployments, you must restart the mongod instances with the new storage.directoryPerDB value and a new data directory (storage.dbPath value), and then repopulate the data. If there's no way to fix this, can I simply re-install mongodb on the servers without having to totally wipe and re-install the VMs? Why does this keep happening and how do I fix it? Is it broken because I used the repair option and it's not setting directoryPerDB when doing the repair? T10:12:09.418-0400 I STORAGE exception in initAndListen: InvalidOptions: Requested option conflicts with current storage engine option for directoryPerDB you requested true but the current server storage is already set to false and cannot be changed, terminating
0 Comments
Leave a Reply. |