Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

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: 1,036 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