Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Unable to compress large Syslog data files

Unable to compress large Syslog data files

Created by David Clark, last modified by Brian.Kiely on Jan 11, 2018

Views: 1,156 Votes: 1 Revisions: 11

Overview

The log size is over 7 GB and Linux is having an issue compressing it.

Environment

All LEM versions

Cause 

  • ASA, for example, can generate up to 6 GB of syslog an hour if info severity is enabled.
  • In 24 hours that log can easily exceed 8 GB.
  • The Log file is exceeding 8 GB and LEM is set to compress compresses the log files daily.
  • Linux cannot compress files over 8 GB.

Resolution

  1. Change the default values on the LEM by going to the CMC shell in Vsphere or putty.
  2. In the command prompt, enter the command appliance.
  3. Enter the command setlogrotate and change to hourly. This allows LEM to compress a file each hour instead of daily.
    Note: If your Logs/Data partition is full or a particular Syslog file is large, contact SolarWinds Support to assist in this process.
     
Last modified

Tags

Classifications

Public