Generate 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.

The debug, verbose, and verbosedebug log settings can generate large files quickly. As soon as you have enough data to reproduce the problem, change the log level back to info.

Change logging level

To generate a detailed log for troubleshooting purposes:

  1. Open the Servers nrsysmond.cfg file, usually located at /etc/newrelic/nrsysmond.cfg.
  2. Change the loglevel setting from info to verbosedebug. Save the file and exit.
  3. Restart the Servers for Linux daemon; for example, use the command /etc/init.d/newrelic-sysmond restart for a standard setup.
  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.
  5. As soon as you finish collecting data: In the nrsysmond.cfg file, change the loglevel back to info. Save and exit.
  6. Restart the New Relic Servers for Linux daemon.

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

The log file is located at /var/log/newrelic/nrsysmond.log. If you are in contact with New Relic 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 support.newrelic.com.