Lattus Troubleshooting Methodologies

Overview  

The troubleshooting methodologies provide Service/Support with a step-by-step approach to identifying root cause and resolution to issues without requiring the individual to become an expert in a particular StorNext or Lattus function. Methodologies lead you through  the basic troubleshooting process of Investigation, Analysis, and Implementation as you learned about in the Troubleshooting Theory and Strategy topic.

 

You can use the following template as a starting point to create new troubleshooting methodologies: Template for a Lattus Troubleshooting Methodology  

 

 


 

 

Current Methodologies

The following categories are in alphabetical order.

AWS S3 Protocol
Bitspread
CLI
CMC GUI
Common Lattus Issues
Customer Configuration Information
Documentation
Hardware
Installation
Metastore
Monitoring & Events
Namespace
Networking
Overview
Performance
Policies
QShell
Scripts
Troubleshooting
Ubuntu
Upgrades
Work To Be Done Notes (WTBDNs)

 

 


 

Notes

 

M662/no media found to satisfy your request ( latticeMedia)

Even though the GUI showed lattusMedia online and happy, John determined it was unavailable using fsmedinfo.

He  changed the state to available and the retrieves are now working again.

# fsmedinfo lattusMedia - Says unavailable

# fsmedchstate -s avail lattusMedia

Logs are being uploaded fromLattus and MDC1 and we'll try to determine why it became unavailable. Case 343266

Note by Chuck Forry on 05/15/2017 12:15 PM

 

First two menus of Lattus

to drop out of this and go to a standard command prompt select Ctrl - z

 

 

 

 

 

 

Note by Chuck Forry on 07/20/2015 11:18 AM

 

Lattus Daily Report Condenser

HOW TO USE THIS TOOL 

 

This tool only works on Linux based platforms for now (SRSCATCH, SPS Lab M440, M660), I will have it ready to run in Windows, Mac Desktops soon.

 

o    Login into the SRSCRATCH, M440 or M660  with your Login UID.

o    Copy the program to your 'bin'  directory as follow :

 

     # cd bin 

     # cp /home/gkrackow/bin/lattDayEventemail.py   .

     # chmod  755  lattDayEventemail.py

     # cd

 

o   Change to a work directory (either SRXXXXX or tmp under your directory)

 

o   Create a copy of the DailyReport  as follow

     In your PC, open the e-mail and take a CUT from the body of the e-mail as sent.

     On the Linux System SSH session :

     #  vi dailyreport.txt          ( -or- any Name you want ).

     #  <Press i  to  insert >

     #  <Paste the content of the e-mail body >

     #  <Press ESC>

     # :wq    <to SAVE and exit  vi>

 

o   Run the utility :   #  lattDayEventemail.py

o   At the prompt enter the workfile You just created  ( dailyreport.txt )

 

o   It takes two seconds to process the file, and you get the condensed report as above.   Done

 

 

To copy the utility to your home directory in the M440 and M660  it is basically the same instructions, BUT the source of the file is :

 

For the M440 :

 

     #  cp  /stornext/unmantgt/gkrackow/bin/lattDayEventemail.py   .

 

For the M660 :

 

     #  cp  /stornext/mdt_fs/gkrackow/bin/lattDayEventemail.py   .

 

The remaining instructions are the same.

 

 

G.K.

Note by Chuck Forry on 07/20/2015 11:16 AM
Attachments
Title Last Updated Updated By
Common Lattus Issues
This document lists common Lattus support issues discovered at Apple MVP, but these errors have also…

This document lists common Lattus support issues discovered at Apple MVP, but these errors have also been discovered at other customer sites. This document is maintained by the SPS Technical Support team and posted here. It has not been edited or reviewed outside of SPS.

02/28/2017 11:23 AM Tom Sajbel


This page was generated by the BrainKeeper Enterprise Wiki, © 2018