Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Network Performance Monitor (NPM) > How to set SolarWinds Agent logs to debug if the Web transaction gets stuck

How to set SolarWinds Agent logs to debug if the Web transaction gets stuck

Table of contents

Updated: 4-6-2017

Overview

When setting a SolarWinds Agent (for Windows or for Linux) logs to DEBUG from INFO (default), the website may hang and not save the change. If this occurs, you can manually change the logging type (DEBUG) on the target agent by remote access and editing a configuration file. See Steps to resolve.

The following images displays the Edit Agent Settings page. This page may hang when changing the drop-down under Troubleshooting and saving: /Orion/AgentManagement/Admin/EditAgent.aspx

 

Environment

  • NPM 12, NPM 12.0.1, NPM 12.1
  • SolarWinds agents

Steps

To resolve, you need to remote access the server/system with the target agent (RDP).

  1. Navigate to this path: C:\Program Files (x86)\SolarWinds\Agent\
  2. Find the SolarWinds.Agent.Service.exe CFG file and edit it in Notepad.
  3. Find the tags: <logging> </logging> 
  4. In these tags, locate the <level></level> tags and replace the default value INFO with DEBUG.
  5. Save the file changes.

 

To verify the change worked:

  1. Navigate to C:\ProgramData\Solarwinds\Logs\Agent\
  2. Open any of the Discovery Plugin logs or the Agent Service EXE logs. 
  3. You should now see the logging level is inflated to DEBUG.

 

 

Last modified

Tags

Classifications

Public