projectbismark/bismark-passive

Files occasionally get tarred twice

Closed this issue · 1 comments

For example, OWC43DC78EE081-1338829308451006-119723.gz in OWC43DC78EE081_2012-07-16_08-15-10.tar is actually a tar file containing several gzipped updates itself (not including 119723, so there's a file missing.)

Seems to happen when there's a backlog of data on the router. In this case, there was an hour of data in the tarfile. The corrupted gzip was the first sequence number in the tarfile.

Might be a race condition with staging the updates on either the client or server?

After migration to bismark-data-transmit, we no longer tar files on the router.