UNIX for Dummies Questions & Answers

It looks like it's trying to report an error.

What is the entire command used to run tar from inside the script?

What else does the script do?

Is the script run remotely, for example via ssh?

Is the script run by cron or at?

A few more thoughts:-Does that give you anything?


Robin

You can trace it while running using tusc/truss/strace, properly optioned up for long and full output and the tar pid, to see what it is up to.

The shell script runs remotely with aim is to extract tar content and remove the tar files from remote host machine

Code:

extract_scripts()
{
  cd $SCRIPT_PATH/scripts/
  su new -c "tar --no-overwrite-dir -hxzf $SCRIPTS_TAR_FILE"
  su new -c "gzip -fd script.tar.gz"
  su new -c "tar --no-overwrite-dir -hxf script.tar"
  if [ -f abs_path_file.tar.gz ]; then
    su new -c "mv abs_path_file.tar.gz /tmp"
    cd /
    su new -c "gzip -fd /tmp/abs_path_file.tar.gz"
    su new -c "tar --no-overwrite-dir -hxf /tmp/abs_path_file.tar"
  fi
  echo $?
}

This tar file size may vary, on host machine these script directories are created and then bundled in tar. FTP tar to remote host and later initiate extraction.

@Robin -This behavior (tar command stuck) is rare and I have observed CPU, server was not busy and once it happen again will provide the output (iostat 3 3)

Thanks all for help and advice will get back with details.

As a "standard user" the script seems to be untarring from the root (/) directory. The paths contained in the tars are relative paths that start with logs/. So that would means a a regular user, the script is trying to create a directory /logs which I suspect may be failing?

The script is ran from superuser and in order to extract tar files I change directory to target and then un-tar files.

Hence tar path will be created without any error

OK, but in post #5 you said you were running the script as a "standard user". Which version is correct?