Pillar Axiom 600 Storage System
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
 

In this Document

Symptoms

Changes

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Limited to internal and partners as some of the steps involve modifying critical system files

Applies to:

Symptoms

In Axiom Manager GUI, the user initiated or Axiom initiated log collection task(s) gets hung and fail to progress.
Attempts to clear the stuck task by performing a Pilot failover may not help sometimes.
This issue is observed in R5 version.

Changes

 NOT APPLICABLE

Cause

Log collection task(s) gets hung for several reasons. One of them being if pilot is running out of space in the /var partition due to which the system won't log, store, or transmit any records of events since the events are stored in the database on /var partition.
Other cause is that the pilot can run out of space if the system has generated numerous core files, or if slammer logs are filling up the directory /var/images/tds with logs and console files.

Solution

Check for space available in pilots /var partition and clean up the space by following the below steps:

Step 1:

This requires SSH access to Axiom pilot.

Check for the free and used space on each file system from the output of command "df -h" on both the pilots.

If /var filesystem is almost full, we can clear old core files and old logs from both active and standby pilot.

If the ssh session is on active pilot (default pilot up on SSH when enabled and logged in), login to passive pilot by running [root@pilot1 root]# ssh pilot2 from it.

Look for core files in /var/log partition and delete the old core files generated by Java or other running processes.

Examples of such files are mentioned below:

core.pilot2.java.6.1396867443.4651
core.pilot2.pilotcfgproc.6.1396867472.3947

Example: rm core.pilot2.java.6.1396867443.4651

After deleting the core files if any, proceed to next step where we can delete old logs from the GUI.

Step 2:

Reduce /var filesystem utilization by deleting the old logs generated by Axiom via GUI as given below:

1.Login to GUI as "pillar". Default password will be a1s2d3f$
2.Navigate to Support Tab
3.Under Tools , go to System Logs
4.Select all the old logs which are no longer needed.
5.Right Click and select Delete.
6.Click OK when prompted.

References

This solution has no attachment