Hello.

I am using IO::Uncompress::Gunzip to read zipped log files
from my web server. About 3/4 of these files fail with
"data error-3". The rest of the zipped files are processed
without difficulty.

Any ideas what might be going on here? Perhaps there is
a RFC1952 compliance issue with some of the files?

Thanks
-Mark

"Mark" <anon40629 [at] hotmail.com> wrote in message
news:1162850161.582686 [at] bubbleator.drizzle.com...
> Hello.
>
> I am using IO::Uncompress::Gunzip to read zipped log files
> from my web server. About 3/4 of these files fail with
> "data error-3". The rest of the zipped files are processed
> without difficulty.
>
> Any ideas what might be going on here? Perhaps there is
> a RFC1952 compliance issue with some of the files?

A "data error" usually means corruption of the compressed data stream.

An easy first step is to check if IO::Uncompress::Gunzip is telling the
truth is to see if the command line gunzip utility thinks there is a problem
with them as well. Can you try testing some of the log files that fail with
gunzup - the "-t" option will test the integrity of the file for you.

If gunzip thinks that the files are ok, can you contact me directly please?

Paul

"Paul Marquess" <Paul.Marquess [at] btinternet.com> wrote:
>
> If gunzip thinks that the files are ok, can you contact me directly
> please?

Paul:

My apologies for the false alarm. After a good night's sleep, I found
that I was not specifying FTP binary mode when downloading the
zipped files from the web server. I didn't pick up on this right away
since some of the zipped files appeared to decompress without
complaint despite the inadvertent ascii-mode transfer.

Of course everything now works as it should.

Thank you for your fine work and continued support on the
Compress::Zlib module.

-Mark