...

This came up with delivery 180409011.  In this case the launchL1 task was started simultaneously on two different hosts in the batch queue.  The first on ran successfully but since the second one failed with an error saying the L1 stream already existed, the process was marked as failed.  To clean up the data display do the following:1)

1. Create a lock file in the appropriate downlink directory: /nfs/farm/g/glast/u42/ISOC-flight/Downlinks/<downlink id>/haltL1

...

1. Check to see if the input directory has moved. It is normally at /nfs/farm/g/glast/u28/stage/<downlink id> but L1 may have moved it to /nfs/farm/g/glast/u41/L1/deliveries/<YYMM>/<downlink id> where YYMM is just the first 4 digits of the downlink id.  If it has moved, just create a symbolic link at the old location. e.g. ln -s /nfs/farm/g/glast/u41/L1/deliveries/1804/180409011 /nfs/farm/g/glast/u28/stage/180409011

...

1. Rollback the launchL1 process so it runs properly.

...

1. Remove the lock file and the symbolic link.

Files missing from NFS and xrootd servers

...