No data appears (Infrastructure)

Problem

You installed the infrastructure agent and waited a few minutes, but no data appears in the infrastructure UI.

Solution

Data should appear in the infrastructure monitoring UI within a few minutes for accounts with previously installed agents.

Missing infrastructure data

If no data appears in the UI, try the following steps to diagnose the problem:

1. Use your package manager to verify that the infrastructure agent is installed:

   Verify install for apt (Debian or Ubuntu)

   1. Use dpkg to verify that the agent is installed:

      bash

      Copy

      $
      dpkg -l | grep newrelic-infra

   2. If dpkg returns no output, see Install with apt.

   Verify install for yum (Amazon Linux, CentOS, or RHEL)

   1. Use rpm to verify that agent is installed:

      bash

      Copy

      $
      rpm -qa | grep newrelic-infra

   2. If rpm returns no output, see Install with yum.

   Verify install for Windows Server

   1. Use the Windows command prompt or Powershell to verify that the agent directory exists:

      bash

      Copy

      $
      dir "C:\Program Files\New Relic\newrelic-infra"

   2. If you receive a File not found error, see Install for Windows Server.

2. Use your init system to verify that the agent is running:

   Verify status with SystemD

   Use SystemD commands with CentOS 7, Debian 8, RHEL 7, and Ubuntu 15.04 or higher:

   1. Check that the agent is running:

      bash

      Copy

      $
      sudo systemctl status newrelic-infra

   2. If the agent isn't running, start the agent manually:

      bash

      Copy

      $
      sudo systemctl start newrelic-infra

   Verify status with System V

   Use System V commands with Debian 7:

   1. Check that the agent is running:

      bash

      Copy

      $
      sudo /etc/init.d/newrelic-infra status

   2. If the agent isn't running, start the agent manually:

      bash

      Copy

      $
      sudo /etc/init.d/newrelic-infra start

   Verify status with Upstart

   Use Upstart commands with Amazon Linux, CentOS 6, RHEL 6, and Ubuntu 14.10 or lower:

   1. Check that the agent is running:

      bash

      Copy

      $
      sudo initctl status newrelic-infra

   2. If the agent isn't running, start the agent manually:

      bash

      Copy

      $
      sudo initctl start newrelic-infra

   Verify status with Windows

   Use the Windows command prompt:

   1. Check that the agent is running:

      bash

      Copy

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

   2. If the agent isn't running, start the agent manually with the Windows command prompt:

      bash

      Copy

      $
      net start newrelic-infra

      If running net start newrelic-infra returns The service name is invalid, the infrastructure agent may not have been installed correctly and the service was not properly created.

      To test this:

   3. From Powershell, run the command get-service newrelic-infra, which will return the status of the service.

   4. If it returns an error Cannot find any service with service name newrelic-infra, then follow standard procedures to reinstall the agent.

3. Use New Relic Diagnostics to try to automatically identify the issue.

4. Verify that your newrelic-infra.yml configuration file contains a valid license_key setting.

5. Verify that the host has a unique hostname, and verify that the hostname is not localhost. For more information, see this Support Forum post.

6. Verify that no firewalls or proxies are blocking outbound connections from the agent process to the Infrastructure domains and ports.

7. Confirm the host is reporting correctly even though it is not appearing in the infrastructure monitoring UI by creating a basic query in Query builder, like:

   SELECT * FROM SystemSample SINCE 60 minutes ago LIMIT 100

   Copy

   Use the query results to note the timestamps, which show when the data was reported. To determine when data was first received, look at the earliest timestamp.

8. Generate verbose logs and examine the logs for errors.

Missing integration data

If you are missing data from an integration, see troubleshooting procedures for:

• APM data missing from infrastructure monitoring
• Amazon/AWS integrations

Other factors affecting access

For more on factors that can affect your ability to access New Relic features, see Factors affecting access.