Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2396812.1
Update Date:2018-05-28
Keywords:

Solution Type  Technical Instruction Sure

Solution  2396812.1 :   FS System: How to clear a hung log collection task  


Related Items
  • Oracle FS1-2 Flash Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
  •  




In this Document
Goal
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Some actions include commands that should be run by an Oracle Technician
Created from <SR 3-17453395881>

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

How to clear a stuck log collection task on an FS1-2 system.

Symptom will normally present itself as part of troubleshooting an existing problem.

NOTE:  It is important to note that in some instances, the system may cold start.  Please ensure all components are GREEN before attempting this action plan.

 

Solution

  1. Log into the FS1 GUI as administrator.
  2. Confirm that the FS1-2 is green.
  3. Check tasks to make sure there are no other tasks in the list.  If other tasks exist, wait for them to complete.  If they are not progressing, do NOT continue with this action plan and contact support.
  4. If the only task is a Log Collection task, disable callhome by following instructions in KM article: FS System: How to Disable Call-Home to Prevent Automatic Service Request (ASR) Generation(Doc ID 1942676.1)
  5. Once callhome has been disabled, log into FSCLI as pillar and clear failure history (this is precautionary only).
    # fscli login -u pillar -oraclefs <Pilot IP>
    # fscli controller -reenable
     
  6. Log into FSCLI as administrator and enable SSH
    # fscli login -u administrator -oraclefs <Pilot IP>
    # fscli system -modify -enablessh 240
     
  7. Open a putty or SSH session to the pilot using the shared IP address.
    User: root
    Password: a1s2d3f$
     
  8. Run the following command to restart the services on the Active pilot
    pilot> service pilotcfg restart
     
  9. Ping the IP address to confirm that the standby pilot has taken over as the Active pilot.
  10. Log back into the FS1-2 GUI and check status (System State and Tasks).
  11. If the System is green and the log collection task has disappeared, start a manual log creation and monitor the task to confirm it will finish.
  12. If it completes, re-enable callhome and check the ASR Portal to confirm that the FS1-2 is now heart-beating.

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback