Simple prefetch and move fails?

Content Authoring
1

(imported topic written by bocNC)

I am implementing a fairly simple action script to download and then move a file to the /tmp directory. The script contents are:

prefetch FP29.tar.bz2 sha1:059d81024da158833fd4bead75a71f39e5617c15 size:100889015 http://server:8080/download/websphere/6.1/linux/UPDI-FP0000029.tar.bz2

move __Download/PF29.tar.bz2 “/tmp/FP29.tar.bz2”

I can see that FP29.tar.bz2 exists in /var/opt/BESClient/__BESData/CustomSite_site/__Download but it never gets moved to /tmp?

I have tried the move command with and without quotes around the source.

Is there something I am missing with the move command? The operating system is SLES Linux.

2

(imported comment written by bocNC)

I also tried changing it from a move to a copy. I turned client debug on and here are the related error messages… But they don’t seem to provide a real good clue as to why its failing:

Fri, 17 Feb 2012 09:11:21 -0900 DebugMessage Command succeeded (Prefetch downloa

d manager collected file) prefetch FP29.tar.bz2 sha1:059d81024da158833fd4bead75a

71f39e5617c15 size:100889015 http://server:8080/download/w

ebsphere/6.1/linux/UPDI-FP0000029.tar.bz2 (fixlet 95)

Fri, 17 Feb 2012 09:11:21 -0900 DebugMessage bumping active action line

Fri, 17 Feb 2012 09:11:23 -0900 DebugMessage Retry error, attempt 8 failed for C

opyFile (/var/opt/BESClient/__BESData/CustomSite_Site/__Download/PF29.tar.

bz2, /tmp/FP29.tar.bz2)

Fri, 17 Feb 2012 09:11:23 -0900 DebugMessage Command failed (Copy of '/var/opt/B

ESClient/__BESData/CustomSite_Site/__Download/PF29.tar.bz2’ to '/tmp/FP29.

tar.bz2’ failed (0)) copy “__Download/PF29.tar.bz2” “/tmp/FP29.tar.bz2” (fixlet

3

(imported comment written by MrFixit)

If a file exists with the same name in that same path a move or copy will fail. You would have to delete that file first.

4

(imported comment written by bocNC)

The file does not exist in the destination directory.

5

(imported comment written by MrFixit)

Then I would look at the permissions of the location in relation to the account the the BESClient runs under. Often duplicating the steps using the same account manually can help identify the problem the BESClient is having.