Software events overview
Software events provide information about OneFS and related application software status, such as SyncIQ policy issues and
errors.
100010001
The /var partition on the node is at or near capacity.
Description
Allowing nodes to run with a full
/var
partition could lead to system stability issues. This issue is often temporary and can be
caused by a problem with log rotation or system files that are eventually deleted automatically. This event also commonly occurs
when a file is mistakenly written into the
/var
partition by an administrator working in the node console.
If the
/var
partition returns to a normal usage level of less than 75 percent, and the issue does not recur, you can disregard the
event.
Administrator action
Follow the instructions in
OneFS: Event notification: The /var partition is near capacity (95% used) - Event ID: 100010001
,
.
If the event persists, gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to
gather cluster logs, see
.
100010002
The /var/crash partition on a node is at or near capacity.
Description
The purpose of the
/var/crash
partition is to preserve data about failed processes and unplanned restarts to enable analysis
of those events. This event is usually the result of a process or service stopping unexpectedly and producing a core file, which is
a type of log file. Core files record all of the system events when the system terminates unexpectedly. Depending on the state
of the process when the problem occurred, these core files can be very large.
Administrator action
●
If the cluster has generated a number of core files, you can redirect those core files to another directory with a larger
capacity by following the instructions in
Isilon: OneFS-How to redirect core files from the /var/crash directory to a larger
capacity directory
,
site.
●
If you are storing temporary files in the /var/crash partition, move them to a larger capacity directory. If you need to keep
the files in the /var/crash partition for some time, quiet the event.
If the event persists, gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to
gather cluster logs, see
.
Software events
35