<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
We have a client running a ----------------------------- application on three linux servers running <BR>
<BR>
Linux HDISATBE3 2.6.32-696.1.1.el6.x86_64 #1 SMP Tue Apr 11 17:13:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux<BR>
<BR>
The two primary event servers accumulate a file of connection/heartbeat activity, and once a week, a crontab job does an SCP of this file to the backend server, which imports these two files to calculate uptime. The respective user has ssh host equivalence, so this proceeds without password challenge. <BR>
<BR>
This has worked for about 10 years. <BR>
<BR>
Very occasionally, like, once in 3 months, we will find the copied file on the backend server is garbled, to wit: <BR>
<BLOCKQUOTE>
- total size is correct; matches source<BR>
- the first XXX bytes of the file is NULL characters. <BR>
<BR>
</BLOCKQUOTE>
Which hoses up everything. I usually figure out which file is boogered, re-do the scp by hand, and re-do the import. Then all is well. <BR>
<BR>
I am just bumfuzzled as to what would cause this. It's always on the front of the file. <BR>
<BR>
I should check and see exactly how many NULLS, but usually when it happens my hair is on fire. I'm guessing about 512 or 1K. <BR>
<BR>
Neal Rhodes<BR>
MNOP Ltd<BR>
<BR>
</BODY>
</HTML>