ON THIS PAGE
Disk Notifications for JSA Appliances
Asset Persistence Queue Disk Full
38750113 - Asset Persistence Queue Disk
Full.
Explanation
The system detected the spillover disk space that is assigned to the asset persistence queue is full. Asset persistence updates are blocked until disk space is available. Information is not dropped.
User Response
Reduce the size of your scan. A reduction in the size of your scan can prevent the asset persistence queues from overflowing.
Asset Update Resolver Queue Disk Full
38750115 - Asset Update Resolver Queue
Disk Full.
Explanation
The system detected that the spillover disk space that is assigned to the asset resolver queue is full.
The system continually writes the data to disk to prevent any data loss. However, if the system has no disk space, it drops scan data. The system cannot handle incoming asset scan data until disk space is available.
User Response
Review the following options:
Ensure that your system has free disk space. The notification can accompany SAR Sentinel notifications to notify you of potential disk space issues.
Reduce the size of your scans.
Decrease the scan frequency.
Disk Failure
38750110 - Disk Failure: Hardware Monitoring
has determined that a disk is in failed state.
Explanation
On-board system tools detected that a disk failed. The notification message provides information about the failed disk and the slot or bay location of the failure.
User Response
If the notification persists, contact Juniper Customer Support or replace the parts.
Disk Full for the Asset Change Queue
38750117 - Asset Change Listener Queue
Disk Full.
Explanation
The asset profile manager includes a process, change listener, that calculates statistics to update the CVSS score of an asset. The system writes the data to disk, which prevents data loss of pending asset statistics. However, if the disk space is full, the system drops scan data.
The system cannot process incoming asset scan data until disk space is available.
User Response
Select one of the following options:
Ensure that your system has sufficient free disk space.
Reduce the size of your scans.
Decrease the scan frequency.
Disk Replication Falling Behind
38750103 - DRBD Sentinel: Disk replication
is falling behind. See log for details.
Explanation
If the replication queue fills on the primary appliance, system load on the primary might increases. Replication issues are commonly caused by performance issues on the primary system, or storage issues on the secondary system, or bandwidth problems between the appliances.
User Response
Select one of the following options:
Review bandwidth activity by loading a saved search MGMT: Bandwidth Manager from the Log Activity tab. This search displays bandwidth usage between the console and hosts.
If SAR sentinel notifications are recurring on the primary appliance, distributed replicated block device (DRBD) queues might be full on the primary system.
Use SSH and the
cat /proc/drbd
command to monitor the DRBD status of the primary or secondary hosts.
Disk Storage Available
38750093 - One or more storage partitions
that were previously inaccessible are now accessible.
Explanation
The disk sentry detected that the storage partition is available after the notification from Disk Storage Unavailable appeared. Disk unavailability was resolved.
User Response
No action is required.
Disk Usage Exceeded Max Threshold
38750038 - Disk Sentry: Disk Usage Exceeded
Max Threshold.
Explanation
At least one disk on your system is 95% full.
To prevent data corruption, some processes are shut down. Event collection is suspended until the disk usage falls below 92%.
User Response
Identify which partition is full, such as the / and /store file systems. Free disk space by deleting files that are not required. For example, remove debug output and patch files from the / file system. If the /store file system is at 95% capacity, look to the subdirectories to determine whether you can move the files to a temporary location or you can delete any files.
If the files are deleted, you cannot search these events.
You can also manually delete older data in the /store/ariel/ directories. The system automatically restarts processes after you free enough disk space to fall below a threshold of 92% capacity.
Disk Usage Exceeded Warning Threshold
38750076 - Disk Sentry: Disk Usage Exceeded
warning Threshold.
Explanation
The disk sentry detected that the disk usage on your system is greater than 90%.
When the disk space on your system reaches 95% full, the system disables processes to prevent data corruption.
User Response
You must free some disk space by deleting files or by changing your data retention policies. The system can automatically restart processes after the disk space usage falls below a threshold of 92% capacity.
Disk Usage Returned to Normal
38750077 - Disk Sentry: System Disk
Usage Back To Normal Levels.
Explanation
The disk sentry detected that the disk usage is below 90% of the overall capacity.
User Response
No action is required.
Insufficient Disk Space to Export Data
38750096 - Insufficient disk space to
complete data export request.
Explanation
If the export directory does not contain enough space, the export of event, flow, and offense data is canceled.
User Response
Select one of the following options:
Free some disk space in the /store/exports directory.
Configure the Export Directory property in the System Settings window to use to a partition that has sufficient disk space.
Configure an offboard storage device.
Predictive Disk Failure
38750111 - Predictive Disk Failure:
Hardware Monitoring has determined that a disk is in predictive failed
state.
Explanation
The system monitors the status of the hardware on an hourly basis to determine when hardware support is required on the appliance.
The on-board system tools detected that a disk is approaching failure or end of life. The slot or bay location of the failure is identified.
User Response
Schedule maintenance for the disk that is in a predictive failed state.
Process Monitor Must Lower Disk Usage
38750045 - Process Monitor: Disk usage
must be lowered.
Explanation
The process monitor is unable to start processes because of a lack of system resources. The storage partition on the system is likely 95% full or greater.
User Response
Free some disk space by manually deleting files or by changing your event or flow data retention policies. The system automatically restarts system processes when the used disk space falls below a threshold of 92% capacity.