Reset Search
 

 

Article

KB44583 - Event log showing iveDiskNearlyFull Critical Trap Message Even after Clearing the PCS logs

« Go Back

Information

 
Last Modified Date9/28/2020 5:20 AM
Synopsis

Event log showing iveDiskNearlyFull  Critical Trap Message Even after Clearing the PCS logs


This article describes about a use case when the Event log shows " iveDiskNearlyFull  critical trap message" even after clearing the PCS logs.

The SNMP threshold notification is configured at 80%

critical - Root::System()[][] - 20xx/08/21  22:52:34 PULSELAB-01 - Sending iveDiskNearlyFull [ diskFullPercent='81' ] SNMP trap to 172.x.x.x:161
critical - Root::System()[][] - 20xx/08/21 22:52:34 - PULSELAB-01 - Sending iveDiskNearlyFull [ diskFullPercent='81' ] SNMP trap to 172.x.x.x:161

info - Root::System()[][] - 20xx/08/21 22:52:34 - PULSELAB-01 - Sending logMessageTrap [ logID='SYS20704' logType='critical' logDescription='critical - Root::System()[][] - PULSELAB-01 - Sending iveDiskNearlyFull [ diskFullPercent='81 ] SNMP trap to 172.x.x.x:161' ] SNMP trap to 172.x.x.x:161

 
Problem or Goal
Cause
The cause of the issue has been identified to be, the way in which tcpdump configuration is captured. It does not have any limit on the number of files. Therefore, no file rotation happens and the number of files grows. 

If the  tcpdump is on, and number of packets passing through PCS box is large, the tcpdump command writes its output to a file tcpdump.dump and, if the file size reaches to 512 MB, continues to write multiple tcpdump.dump files. This will utilize the existing disk space of the device in data partition. Hence, as a result, the above SNMP trap messages is generated in the event logs. 

 
Solution

The issue is fixed in 9.1 R8.2 ,9.1R9 and above releases.
Related Links
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB2564
 
Attachment 1 
Created ByBiju Kadavil

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255