Difference between revisions of "Troubleshooting"

From Research Computing Center Wiki
Jump to navigation Jump to search
(Created page with "===Introduction=== This page provides the common errors and solutions for job at GACRC cluster. The examples are made from Sapelo2, but it applies to other GACRC clusters as...")
 
Line 3: Line 3:
 
This page provides the common errors and solutions for job at GACRC cluster. The examples are made from Sapelo2, but it applies to other GACRC clusters as well.   
 
This page provides the common errors and solutions for job at GACRC cluster. The examples are made from Sapelo2, but it applies to other GACRC clusters as well.   
  
==File format ===
+
===File format===
  
 
The text files, such as submission script, fasta file or other text data files at Linux should be in ASCII format. If the files are generated under other operating system or copied from web, there could introduce hidden characters which cannot be recognized by Linux. Hence bring the error for the job. There are many posts elaborating this problmes, such as [https://www.editpadpro.com/tricklinebreak.html editpadpro]
 
The text files, such as submission script, fasta file or other text data files at Linux should be in ASCII format. If the files are generated under other operating system or copied from web, there could introduce hidden characters which cannot be recognized by Linux. Hence bring the error for the job. There are many posts elaborating this problmes, such as [https://www.editpadpro.com/tricklinebreak.html editpadpro]

Revision as of 16:13, 9 July 2018

Introduction

This page provides the common errors and solutions for job at GACRC cluster. The examples are made from Sapelo2, but it applies to other GACRC clusters as well.

File format

The text files, such as submission script, fasta file or other text data files at Linux should be in ASCII format. If the files are generated under other operating system or copied from web, there could introduce hidden characters which cannot be recognized by Linux. Hence bring the error for the job. There are many posts elaborating this problmes, such as editpadpro

Here is the command to check on the file format, using sub,sh as an example file name below:

file sub.sh

The expected the correct format is ASCII. There could be a variation of response, such as python script, ASCII with long lines. All these response are acceptable as long as it is ASCII text format without wrong endings:

sub.sh: Bourne-Again shell script, ASCII text

Here are common wrong formats:

sub.sh: Bourne-Again shell script, UTF-8 Unicode text executable
sub.sh: Bourne-Again shell script,  ASCII text, with CRLF line terminators

Most time it is easily to be fixed by saving the file in unix format or using the following command at cluster:

dos2unix sub.sh

For the file in UTF-8 Unicode encoding, the easiest way is to manually remove the weird characters in a Linux text editor, such as vi, nano or pico.


Back to Top