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-72-2112483.1
Update Date:2017-06-20
Keywords:

Solution Type  Problem Resolution Sure

Solution  2112483.1 :   SBC can not tar the logfiles, giving tar ball: I/O error  


Related Items
  • Acme Packet 3820
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
  •  




In this Document
Symptoms
Cause
Solution


Created from <SR 3-12154757031>

Applies to:

Acme Packet 3820 - Version S-Cx6.3.x to S-Cz7.3.0 [Release S-Cx6.0 to S-Cz7.0]
Information in this document applies to any platform.

Symptoms

While trying to archive the logs, getting following error and the tar is failing:-

ACME(archives)# create LOGS 20160209_CierreDeProyectoCallCenterBBVA
Error in creating the tar ball: I/O error

ACME# package-logfiles
Tar/gzip file /opt/logs/logs-160209.tar.gz to include 300 files of 245 MiB (uncompressed)
Proceed? [y/n]?: y
Error tar'ing file list: I/O error

Cause

Suspected log files corruption, advised customer to delete-logfiles.

Solution

Performed the following troubleshooting steps to find the resolution :-

1) Advised customer to get us the entire logfiles without taring. Moved the files to the lab system and then tried taring the files, no issues observed.

2) Since in lab everything was working fine, suspected an issue related to file system corruption or bad sectors.

3) Advised customer to run the following command and check which one fails :-

(i) package-logfiles name /opt/logs/5dlogs.tar.gz newer-than 5 -

(ii) package-logfiles name /opt/logs/5dlogs.tar.gz newer-than 10

The above commands will help us to isolate the issue as the files may be corrupted after a certain date and time,.

4) Found that newer-than 5 works fine but newer-than 10 was failing which means there is no issue with process - tar and maye files are corrupted.

5) Check the amount of free space for the following directories :- show directory /opt/archives ; show  dirctory /code/logs ; show directoy /ramdrv and show directory /ramdrv/logs

6) Advised customer to move the logfiles to an external server and perform delete-logfiles.

7) We can also advise customer to run diagnostic command on hard disk which can help us to find bad sectors.

Issue resolved after deleting log files.

 


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