• Compress and ftp the files to the Quantum ftp from the DXi.
• Compress the files and download them to the customer’s computer, then ftp the files to the Quantum ftp.
• Dispatch a technician to gather the core files via SCP with the technician ftp’ing the files to the Quantum ftp.
• Dispatch a technician to gather the core files on a USB flash drive and ship the USB drive to Quantum.

You will also need to gather the DXi system collect, storage array log and if applicable the DSET log from the system. (See "Step 2: Collect Support Data" in the DXi-Series Status and Log Collection  job aid for instructions).

 

---

 

 

1. The core file(s) generated by the DXi are automatically placed in the /scratch/core directory. Log into the DXi via ssh or thru the serial connection and change to the directory where the cores are located (If a core file in this directory has '-deleted' at the end of the file it is no longer on the system). Gather the directory listing of the /scratch/core directory as this may be needed later.

# cd /scratch/core

 

# ls -lah

Example of core file:      -rw-------   1 root root 23G Sep 14 13:49 generatesystemc-1316004544-21790-reported

 

 

 

2. The backtrace may be in the collect logs, but if it isn't, then it might be good to get the backtrace at this point. If the backtrace is not located in the core_backtrace.out file in the collect log or it not being heavily used you should be able to get the backtrace at this time.  Please make note of the ‘Caution’ following this step. Instructions on how to gather the backtrace are located in the  Gather Data on a Core Dump topic Step 6. After gathering the backtrace, come back to this step and continue with this procedure to gather the data that would be needed if the issue needs to be escalated. 

 Caution: Using gdb to gather the backtrace on a live customers DXi can use up the available memory and cause the DXi to have problems and possibly crash. This should be performed on another Quantum internal DXi system.

 

3. Copy the core file out of the /scratch/core directory. 

# mkdir /scratch/qtmtmp             (This directory may have already been created)

 

# cp <nameofcorefile-reported> /scratch/qtmtmp

 Note: Creating a new file in the /scratch/core directory will result in a new RAS ticket for a core. If a new file is created or copied into this directory, the copied or created file will be renamed to <filename>-reported and a RAS ticket will be generated. The core file must be moved to another directory prior to being zipped up. 

 

4. Collect the md5sum of the core file prior to zipping up the core file.

               # md5sum <nameofcorefile-reported> > /scratch/qtmtmp/md5sum-<nameofcorefile-reported>.txt

 

5. gzip the core file to compress the size and make it easier to transfer. 

 # cd /scratch/qtmtmp

# gzip -9 <nameofcorefile-reported>

 Note: The -9 option gives you the best compression rate with gzip. 

 

6. Collect the md5sum of the core file after being compressed.

# md5sum <nameofcorefile-reported>.gz > md5sum-<nameofcorefile-reported>-gz.txt

 

7. Locate the daemon that cored. This can give you many files and daemons, but usually the ones needed are in the /opt/DXi/ or /etc/init.d/ directories. The output from this command will give you the path of the daemon that cored. (The cored_daemon will be the process that cored i.e. winbindd, replicationd, ostd, etc. and is found in the name of the core file.)  Look in the backtrace for a line that says Core was generated by.

                    [Thread debugging using libthread_db enabled]
        Core was generated by `/hurricane/ostd'.
        Program terminated with signal 6, Aborted.
        #0 0x00002b8a785e5265 in raise () from /lib64/libc.so.6

 

 Note: The Locate command should not be used and may be installed on the DXi, running updatedb can cause heavy load and disturb operations. locate and updatedb has been removed and will be removed in future releases.

 

8. Copy the core_daemon file to the /scratch/qtmtmp directory.   

9. gzip the cored_daemon file to compress the size and make it easier to transfer. 

10. Collect the md5sum of the core file.

11.  If the customer allows ftp from the DXi and the files aren’t too large to be ftp’ed due to customer bandwidth constraints, FTP the zipped core file, zipped cored_daemon and the md5sum files to the Quantum ftp site gps.quantum.com.  If you are unable to ftp the files see the later 'Alternatively' section about accessing the files via scp, web browser or dispatching a technician to gather the core files.

             # ftp gps.quantum.com

 

Logon as user: anonymous

Password: Your email address

# ftp> cd incoming/SR<ServiceRequestNumber>

 

 Note: If you haven't previously made the SR directory you can use the mkdir command to create the directory (i.e. mkdir /incoming/SR<ServiceRequestNumber>.

 

Change to Binary mode.

# ftp> bin

# ftp> hash                      (Optional command prints #'s as it is uploading.)

# ftp> put <nameofcorefile-reported>.gz

 

# ftp> put md5sum-<nameofcorefile-reported>.txt

 

# ftp> put md5sum-<nameofcorefile-reported>-gz.txt

 

# ftp> put <cored_daemon>.gz

 

# ftp> put md5sum-<cored_daemon>.txt

 

(You should also upload the DXi collect files at this time if they have not been uploaded.)

 

# ftp> quit

 

 

12. After you have verified that the files have downloaded properly to the ftp site and are they are valid by verifying the md5sum is the same as it was before the transfer, you will need to remove the files from the /scratch/qtmtmp directory.

# rm /scratch/qtmtmp/<nameofcorefile-reported>.gz

# rm /scratch/qtmtmp/md5sum-<nameofcorefile-reported>.txt

Alternatively:  If you cannot ftp the core file directly from the DXi due to ftp being blocked, upload the files from the DXi to a customer PC. You can do this with SCP or via the GUI, the customer can then transfer them to our ftp site from a computer that allows FTP access. To do this, complete either of the following steps:

 

SCP:

 

 

 

WebGUI:

 

1. Copy the files to /hurricane/www/html. 

cp /scratch/qtmtmp/<nameofcorefile-reported>.gz /hurricane/www/html

cp /scratch/qtmtmp/md5sum-<nameofcorefile-reported>.txt /hurricane/www/html

 

2. After you have copied the files, you will need to remove them from the /scratch/qtmtmp directory.
   
   # rm /scratch/qtmtmp/<nameofcorefile-reported>.gz

# rm /scratch/qtmtmp/md5sum-<nameofcorefile-reported>.txt

 

3. Verify that the file has proper permission to allow downloading.

# chmod 775  /hurricane/www/html/<nameofcorefile-reported>.gz

# chmod 775  /hurricane/www/html/md5sum-<nameofcorefile-reported>.txt

 

4. Go to the DXi GUI using the following:

http://<IPofDXi>/<nameofcorefile-reported>.gz

http://<IPofDXi>/md5sum-<nameofcorefile-reported>.txt

 

5. This will prompt you to save the core file to the local computer.

6. Remove files from the directory when done.

   
   # rm /hurricane/www/html/nameofcorefile-reported.gz

# rm /hurricane/www/html/md5sum-<nameofcorefile-reported>.txt

 

Tech dispatch:

 

 

 

---

What's Next?

Gather Data on a Core Dump >