Start, stop, and restart the infrastructure agent

The infrastructure agent starts automatically after you run the installation script. However, there are situations where you may need to manually restart the agent (for example, after changing your agent configuration).

Want to try out our infrastructure agent? Create a New Relic account for free! No credit card required.

Linux

For Linux, ensure you use the correct command for your init system. Select start, stop, restart, or status as appropriate:

• SystemD (Amazon Linux 2, SLES 12, CentOS 7 or higher, Debian 8 or higher, RHEL 7 or higher, Ubuntu 15.04 or higher):

  bash

  Copy

  $
  sudo systemctl <start|stop|restart|status> newrelic-infra

• System V (Debian 7, SLES 11.4, RHEL 5):

  bash

  Copy

  $
  sudo /etc/init.d/newrelic-infra <start|stop|restart|status>

• Upstart (Amazon Linux, RHEL 6, Ubuntu 14.04 or lower):

  bash

  Copy

  $
  sudo initctl <start|stop|restart|status> newrelic-infra

Windows

For Windows Server, you can use the Windows command prompt or PowerShell.

Command prompt (cmd.exe)

• Start or stop the Windows agent:

  bash

  Copy

  $
  net <start|stop> newrelic-infra

• Restart the Windows agent:

  bash

  Copy

  $
  net stop newrelic-infra ; net start newrelic-infra

• Check the status of the Windows agent:

  bash

  Copy

  $
  sc query "newrelic-infra" | find "STATE"

PowerShell

• Start or stop the Windows agent:

  bash

  Copy

  $
  Stop-Service -Name "newrelic-infra"
  $
  Start-Service -Name "newrelic-infra"

  Tip

  You can also use net start|stop newrelic-infra

• Restart the Windows agent:

  bash

  Copy

  $
  Restart-Service newrelic-infra

• Check status of Windows agent:

  bash

  Copy

  $
  (Get-Service newrelic-infra).Status

macOS

• Stop or start the agent:

  bash

  Copy

  $
  brew services stop newrelic-infra-agent
  $
  brew services start newrelic-infra-agent

• Restart the agent:

  bash

  Copy

  $
  brew services restart newrelic-infra-agent

• Check status of the agent:

  bash

  Copy

  $
  brew services list

Customize agent logs

The infrastructure agent logs to a default location which depends on your platform. You can customize this location with the log_file setting. You can also generate verbose logs for troubleshooting.

Determine your init system

For Windows Server, the commands in this document use the Windows command prompt.

For Linux, the infrastructure agent selects an init system appropriate for your distribution:

Configuration management tools

To manage the infrastructure agent with your config management tool, see:

• Ansible configuration
• Chef configuration
• AWS Elastic Beanstalk configuration
• Puppet configuration