Update Agent to Enable Fatal Log Rotation

Ops Manager v6.0 will EOL in January 2025. Upgrade to a higher Ops Manager version as soon as possible.

For MongoDB Agent versions below 12.0.21, you must reinstall the MongoDB Agent to enable fatal log file rotation.

In MongoDB Agent versions 12.0.21 and above, fatal log file rotation is automatically enabled.

Note

Fatal log file rotation helps to maintain a useful automation-agent-fatal.log file by rotating the file on a regular basis and deleting only the oldest logs.

Reinstall the MongoDB Agent

To reinstall the MongoDB Agent to enable fatal log file rotation, follow the procedure for your distribution:

Stop the MongoDB Agent.

Stop the MongoDB Agent using the appropriate command for your agent process.

If you started your agent process with systemd, run the following command:

sudo systemctl stop mongodb-mms-automation-agent.service

If you started your agent process with init.d, run the following command:

sudo service mongodb-mms-automation-agent stop

Reinstall the MongoDB Agent.

Use the installation instructions that apply to your MongoDB Agent use case:

If you use MongoDB Agent to manage deployments, follow the instructions to Install the MongoDB Agent to Manage Deployments, or
If you use MongoDB Agent to only monitor or back up deployments, follow the instructions to Install the MongoDB Agent to Only Monitor or Backup Deployments.

At the top of the installation page, select RHEL/CentOS/SLES/AMZ and follow the procedure to install the MongoDB Agent.

Start the MongoDB Agent.

Using your terminal, start the MongoDB Agent with the appropriate command for your system:

To start the agent process with systemd, run the following command:

sudo systemctl start mongodb-mms-automation-agent.service

To start the agent process with init.d, run the following command:

sudo service mongodb-mms-automation-agent start

The reinstalled MongoDB Agent rotates automation-agent-fatal.log on a regular basis.

Stop the MongoDB Agent.

Stop the MongoDB Agent using the following command:

sudo systemctl stop mongodb-mms-automation-agent.service

Reinstall the MongoDB Agent.

Use the installation instructions that apply to your MongoDB Agent use case:

If you use MongoDB Agent to manage deployments, follow the instructions to Install the MongoDB Agent to Manage Deployments, or
If you use MongoDB Agent to only monitor or back up deployments, follow the instructions to Install the MongoDB Agent to Only Monitor or Backup Deployments.

At the top of the installation page, select Ubuntu/ Debian and follow the procedure to install the MongoDB Agent.

Start the MongoDB Agent.

Using your terminal, start the MongoDB Agent with the following command:

sudo systemctl start mongodb-mms-automation-agent.service

The reinstalled MongoDB Agent rotates automation-agent-fatal.log on a regular basis.

Stop the MongoDB Agent.

Stop the MongoDB Agent using the following command:

pkill -f mongodb-mms-automation-agent

Reinstall the MongoDB Agent.

Use the installation instructions that apply to your MongoDB Agent use case:

If you use MongoDB Agent to manage deployments, follow the instructions to Install the MongoDB Agent to Manage Deployments, or
If you use MongoDB Agent to only monitor or back up deployments, follow the instructions to Install the MongoDB Agent to Only Monitor or Backup Deployments.

At the top of the installation page, select Linux and follow the procedure to install the MongoDB Agent.

Start the MongoDB Agent.

Using your terminal, run the following command with:

The path to your configuration file
The path to save the fatal log file

nohup /bin/bash -c "./mongodb-mms-automation-agent --config=./example/path/to/config 2>&1 | ./fatallogger -logfile ./example/path/to/log 2>&1"

Back

Manage API Keys

Organizations & Projects