This version has reached end of life on October 2016. Learn more about upgrading your version of MongoDB.



The logRotate command is an administrative command that allows you to rotate the MongoDB logs to prevent a single logfile from consuming too much disk space. You must issue the logRotate command against the admin database in the form:

{ logRotate: 1 }


Your mongod instance needs to be running with the --logpath [file] option.

You may also rotate the logs by sending a SIGUSR1 signal to the mongod process. If your mongod has a process ID of 2200, here’s how to send the signal on Linux:

kill -SIGUSR1 2200

logRotate renames the existing log file by appending the current timestamp to the filename. The appended timestamp has the following form:


Then logRotate creates a new log file with the same name as originally specified by the systemLog.path setting to mongod or mongos.


New in version 2.0.3: The logRotate command is available to mongod instances running on Windows systems with MongoDB release 2.0.3 and higher.