- play_arrow Troubleshooting a Problem
- play_arrow Running Health Checks
- play_arrow Increased DNS Requests
- play_arrow JSA System Notifications
- JSA System Notifications
- Disk Usage System Notifications
- Asset Notifications for JSA Appliances
- Automatic Update Notifications for JSA Appliances
- Custom Rules Notifications for JSA Appliances
- Disk Notifications for JSA Appliances
- Event and Flow Notifications for JSA Appliances
- Failure Notifications for JSA Appliances
- Failure Notifications for QRadar Apps
- High Availability Notifications for JSA Appliances
- License Notifications for JSA Appliances
- Limit Notifications for JSA Appliances
- Log and Log Source Notifications for JSA Appliances
- Memory and Backup Notifications for JSA Appliances
- Offense Notifications for JSA Appliances
- Repair Notifications for JSA Appliances
- Vulnerability Scan Notifications for JSA Appliances
Disk Storage Not Accessible Error
Each host in your JSA deployment monitors the availability of partitions. Disk availability is tested every minute by opening a file, writing to it, and deleting it.
If the disk availability test takes longer than the default 5 seconds, then the host context process reports an error in the JSA logs. An error might also occur when the JSA system experiences high load and large volumes of data are written, searched, purged, or copied to another system.
The error might resemble the following output:
Jun 24 07:22:41 127.0.0.1 [hostcontext.hostcontext] [5b3acf9a-aa8a-437a-b059-01da87333f43/SequentialEventDispatcher] com.q1labs.hostcontext.ds.DiskSpaceSentinel: [ERROR] [NOT:0150062100][172.16.77.116/- -] [-/- -]The storage partition(s) /store/backup on qradarfc (172.16.77.116) are not currently accessible. Manual intervention may be required to restore normal operation.
If the message is displayed repeatedly, then verify the problem. For more information, see Verifying Partition Storage Problem.
Verifying Partition Storage Problem
You verify a partition storage problem by creating a temporary file on the JSA Console or a managed host.
Verify that the partition storage problem is not caused by external storage that is slow or unavailable.
Use SSH to log in JSA console.
Create a test by typing the following commands:
touch /store/backup/testfile
ls -la /store/backup/testfile
If one of the following two messages is displayed, increase the partition test timeout period.
touch: cannot touch `/store/backup/testfile': Read-only file systemnfs server time out
Click the Admin tab.
On the System Configuration menu, click System Settings >Advanced.
In the Partition Tester Timeout (seconds) list box, select or type 20.
Click Save.
Choose one of the following options:
If you use a network file system, such as iSCSI, or Network File System (NFS), then contact your storage administrator to verify that the file servers are accessible and operational.
If you use a local file system, then you might have a file system issue or a failed disk.
