Generating logs for troubleshooting (Servers for Linux)

For the latest, most advanced host monitoring, check out New Relic Infrastructure.

In New Relic's Servers for Linux, you can change the log file's level of detail. Making logging more verbose can help when troubleshooting an issue.

To generate a detailed log for troubleshooting purposes:

  1. Open the New Relic Servers nrsysmond.cfg file, which is usually located at /etc/newrelic/nrsysmond.cfg.
  2. Change the loglevel setting from info to verbosedebug. Save the file and exit.

  3. Restart the New Relics Servers for Linux daemon. The command /etc/init.d/newrelic-sysmond restart should work in a standard setup.

    Your webserver does not need to be restarted. Restarting the New Relic Servers daemon will have no effect on your webserver.

  4. If you are trying to reproduce a specific known issue, let New Relic record data until the issue is reproduced. Otherwise, record data for around 5-6 minutes.

    The DEBUG and VERBOSE log settings can generate large files quickly when left on. It is best to leave these log levels on for only as long as it takes to reproduce the problem.

  5. In the nrsysmond.cfg file, change the loglevel back to info. Save and exit.
  6. Restart the New Relic Servers for Linux daemon.

The log file is located at /var/log/newrelic/nrsysmond.log. If you are in contact with New Relic technical support, this is the log file they request.

For more help

Additional documentation resources include:

Discuss New Relic Servers in the New Relic Online Technical Community! Troubleshoot and ask questions, or discuss Servers for Linux or Servers for Windows in detail.

If you need additional help, get support at