Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > The syslog file is empty, logs show 0 kb, but data is sent to LEM

The syslog file is empty, logs show 0 kb, but data is sent to LEM

Updated December 7, 2017

Overview

The particular log in LEM has not rotated. This means you are seeing, for example, a user.log with 0 bytes. Also, the user.log.1 has not compressed and contains incoming data. Subsequently, the connectors are pointing at user.log and see no current data.  

Environment

  • LEM 6.3.1

Cause 

High frequency logging to non local0-7 log files may break their rotation. This means the default log shows 0 kb after the rotation occurs.

Resolution

  1. Edit the syslog service on the device to log to any syslog local[0-7].log facility, as they deal with high frequency logging.
  2. Contact SolarWinds Support if this does not resolve the issue.
 

 

Last modified

Tags

Classifications

Public