Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > LEM reboot for troubleshooting

LEM reboot for troubleshooting

Table of contents
Created by Tim Rush, last modified by Aileen de Lara_ret on Feb 15, 2017

Views: 914 Votes: 0 Revisions: 6

Overview

This article provides brief information on rebooting LEM for troubleshooting.

Environment

All LEM deployments

Detail

LEM is a Linux-based hardened-appliance that has been virtualized.

 

Common misconception: Rebooting LEM fixes issues.

Fact: A reboot rarely fixes any problem, but may delay getting to the cause for why the reboot was considered.

 

A reboot will do the following:

  1. Clear out cached log data.
  2. Re-connect all agents after it starts up.

 

A reboot may be required when all other troubleshooting has failed, or recommended by SolarWinds Support.

Otherwise, if you changed the hostname, changed the network configurations, or imported a "backupconfig" (used for migrating to different VM platform, disaster recovery testing, or to restore the rules/groups).

 

 

Last modified

Tags

Classifications

Public