You probably got errors when you restarted with the new configuration. Share those errors. You should use a log file as it simplifies trouble shooting.
No, there are 64 GB. According to htop it is 62.6 GB. My goal is to allow MongoDB to use 56 GB. The inability to connect is observed with different cacheSizeGB values.
The error was observed both immediately after saving the changes in mongod.conf, and after rebooting the OS.
sudo systemctl start mongod sudo systemctl status mongod
× mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-09-10 22:47:59
MSK; 16s ago
Docs: https://docs.mongodb.org/manual
Process: 5069 ExecStart=/usr/bin/mongod --config /etc/mongod.conf
(code=exited, status=2)
Main PID: 5069 (code=exited, status=2)
CPU: 20ms
сен 10 22:47:59 platon-MS-7D42 systemd[1]: Started MongoDB Database Server.
сен 10 22:47:59 platon-MS-7D42 mongod[5069]: Unrecognized option:
storage.wiredTiger
сен 10 22:47:59 platon-MS-7D42 mongod[5069]: try '/usr/bin/mongod
--help' for more information
сен 10 22:47:59 platon-MS-7D42 systemd[1]: mongod.service: Main
process exited, code=exited, status=2/INVALIDARGUMENT
сен 10 22:47:59 platon-MS-7D42 systemd[1]: mongod.service: Failed with
result 'exit-code'.
I just tested locally with this in my config file and mongod starts up just fine with MongoDB 6.0.1. This config even works with version 3.4.23, so storage.wiredTiger is a valid key.
I know you said that you’re running MongoDB 6.0.1, but can you post the results of mongod --version just for sanity. It’s almost like you have a really old version of mongod running.