Start a new topic

Crush job corrupts text file

Scott Metoyer @ Tue Sep 23 15:36:03 EEST 2014
I have a simple Crush job that copies a text file from an SFTP server using the Find and Copy tasks. I've noticed some strange behavior:

When the file shrinks (has fewer lines than the file it is replacing) in the source, the file that is written to the destination has the original file size and has duplicated lines to account for the difference. Here is an example before the sync:

860236746 Acero, Jame Jerica 59.00 59.00
862350106 Acevedo, Alex Marie 59.00 .00
861531918 Acevedo, Arrow Ken 59.00 59.00
861223543 Acevedo, Dog Giselle 59.00 59.00
861345356 Acevedo, Kevin Greg 59.00 59.00

Then, after the source shrinks by three lines, I would expect to see this in the destination:

860236746 Acero, Jame Jerica 59.00 59.00
862350106 Acevedo, Alex Marie 59.00 .00

Instead, what I see is this:

860236746 Acero, Jame Jerica 59.00 59.00
862350106 Acevedo, Alex Marie 59.00 .00
860236746 Acero, Jame Jerica 59.00 59.00
862350106 Acevedo, Alex Marie 59.00 .00
860236746 Acero, Jame Jerica 59.00 59.00

Do I have something misconfigured?

Thanks!

spinkb @ Tue Sep 23 16:02:42 EEST 2014
Please update now to get 7.1.0_146. Then try this again.

Let me know,
Ben
Philip.Vuong @ Tue Sep 23 17:30:45 EEST 2014
[quote=spinkb]Please update now to get 7.1.0_146. Then try this again.

Let me know,
Ben[/quote]

Hi, I am working with Scott on this issue.

We discovered this issue in our production environment and it will take a little bit of time to get the upgrade going. In the mean time, the file we are copying over is critical to our operations.

Would performing a find/delete operation on the destination folder before the find/copy operations be a feasible temporary solution?

Could you point me to any patch notes listed that addresses this issue specifically?

Also - we are running into an issue in which, when we click "Test & Run Job", the job is running twice. Is this also something that would be addressed in updating?
spinkb @ Tue Sep 23 17:43:44 EEST 2014
We aren't aware of any test and run job issues...so this must have been fixed at some point in the past. I don't know your current version your using though.

But as you mentioned in the other email, first clearing the target location before writing to it is the easiest solution to implement without updating.

Thanks,
Ben
Scott Metoyer @ Tue Sep 23 18:05:26 EEST 2014
Our version is 6.2.
spinkb @ Wed Sep 24 04:24:12 EEST 2014
Then you are *very* out of date. 1.5 years of changes in CrushFTP is a significant amount. You might be exposed to exploits too staying on an old version, things we have fixed, things we have updated, etc. There isn't anything known...but staying on an old version is not a good method for security.

v7 has a majorly improved "Jobs" system. This along would improve what your doing, allowing you to see details as the job runs, etc. v6 had our first pass at making a job scheduler. v7 drastically improved on that system.

I can't stress enough...plan to upgrade to v7 as soon as you can...especially since your using Jobs. At the very least, move to v6.5. Its a one button press and it auto updates and restarts CrushFTP update. Most people can do this in under 1 to 2 minutes.

Thanks,
Ben
Login to post a comment