Start a new topic

CrushTask - Move logs error but works anyway

I've got a CrushTask that triggers a Move after a user uploads a file. The user has 3 directories, each one has an 'In' and 'Out' subdirectory under them. The user can only upload into the In/ directories.


When the user uploads a file, it registers two failures to move and then it actually succeeds in moving. I don't understand!


Log sample, logged in as 'user1', and dropping the file 'current.time' into the directory 'ColorCorrect/In' :


EVENT|11/26/2015 15:17:50.450|Event:PLUGIN USER-Process:|Thread.java:getStackTrace:1589|Events.java:doEventPlugin:954|Events.java:run:593|Thread.java:run:745

EVENT|11/26/2015 15:17:50.450|Event:PLUGIN USER-Process:CrushTask:1vUzSUFbgk:

GENERAL|11/26/2015 15:17:50.453|tasks.Task.:CrushTask items size=1

GENERAL|11/26/2015 15:17:53.539|tasks.CopyTask.Move to Color Destination:Attempting rename move /mnt/bulk0/user1/ColorCorrect/In/current.time to /mnt/bulk0/user1/ColorCorrect/Out/current.time 

GENERAL|11/26/2015 15:17:53.565|tasks.CopyTask.Move to Color Destination:Attempting rename move /mnt/bulk0/user1/ColorCorrect/In/current.time to /mnt/bulk0/user1/ColorCorrect/Out/current.time

GENERAL|11/26/2015 15:17:53.565|tasks.CopyTask.Move to Color Destination:attempting copy (1) /mnt/bulk0/user1/ColorCorrect/In/current.time to /mnt/bulk0/user1/ColorCorrect/Out/current.time

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:Resetting source and destination connections due to error...

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:Job task:__user1_112615151750451:kbLTcRmxKZcuDJ7KDmqx

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:java.io.FileNotFoundException: /mnt/bulk0/user1/ColorCorrect/In/current.time (No such file or directory)

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:java.io.FileInputStream.open:-2

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:java.io.FileInputStream.<init>:146

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:java.io.FileInputStream.<init>:101

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:com.crushftp.client.FileClient.download3:499

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:com.crushftp.client.GenericClient.download2:360

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:com.crushftp.client.GenericClient.download:202

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:tasks.CopyTask.doTransfer:419

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:tasks.MoveTask.run:50

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:tasks.Task.go:148

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:CrushTask.Start$2.run:541

GENERAL|11/26/2015 15:17:53.581|tasks.CopyTask.Move to Color Destination:java.lang.Thread.run:745


I also have logging on for both success and failure on this task and I get the following:


success.log:

OK : Move to Color Destination-current.time-20151126-151750


failure.log:

FAIL : Move to Color Destination-{stem}{ext}-20151126-151750

FAIL : Move to Color Destination-current.time-20151126-151750



1 Comment

The move first attempts a rename "move".  If that doesn't report success, it then does a copy/delete type of move.  The rename move apparently failed...but in reality succeeded.  So it then did a copy/delete action.


Work around the issue with a copy task, and delete task instead.  I don't know why your filesystem reported the rename failed when it had worked.

Login to post a comment