Skip to content
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.

unpack error #2

Open
catkins6 opened this issue Jan 15, 2016 · 7 comments
Open

unpack error #2

catkins6 opened this issue Jan 15, 2016 · 7 comments

Comments

@catkins6
Copy link

Hi Addison,

I was able to successfully sync using the canvas-data-cli but I am receiving an error when using the unpack. It creates the text file with headers but the data is not included. I have received two different errors but the results are still the same.

canvasDataCli -c config.js unpack -f account_dim
outputting account_dim to filepath/account_dim.txt
events.js:141
throw er; // Unhandled 'error' event
^

Error: unknown compression method
at Zlib._handle.onerror (zlib.js:363:17)

canvasDataCli -c config.js unpack -f enrollment_dim
outputting enrollment_dim to filepath/enrollment_dim.txt
events.js:141
throw er; // Unhandled 'error' event
^

Error: incorrect header check
at Zlib._handle.onerror (zlib.js:363:17)

@Mythra
Copy link
Contributor

Mythra commented Apr 9, 2017

😞 Man we really dropped the ball on this one.

As mentioned in #7 we haven't seen this in a long time. Are you still running into this issue after updating the CLI?

@jagobrown
Copy link

I've just hit this same issue but raised it here: #7
Jago

@catkins6
Copy link
Author

Thanks for checking in SecurityInsanity I do not remember how but I was able to fix this problem.

@mcjelewis
Copy link

mcjelewis commented Mar 13, 2018

I am now getting the "Unhandled 'error' event" message. The unpack command works with other tables, but I can't get it to run anymore on the requests data.


canvasDataCli unpack -c canvas-data-cli/config.js -f requests
outputting requests to [path to file]/requests.txt
events.js:154
throw er; // Unhandled 'error' event
^

Error: unknown compression method
at Zlib._handle.onerror (zlib.js:363:17)


Anyone know how this was fixed in the past?

@mcjelewis
Copy link

After deleting all folders and files from dataFiles (the folder where all gz files are synced to) and rerunning the sync command, I was able to get the requests files to unpack.

@Mythra
Copy link
Contributor

Mythra commented Mar 13, 2018

Hey @mcjelewis ,

This can sometimes happen if there's an intermittent network error, or disk error. The CLI doesn't actually verify the downloaded file is the exact same as those being served from S3 (thus ensuring the download completed with no weird faults). So yes if you see this error it probably means that file wasn't downloaded correctly. You should just be able to remove the affected files, and re-run sync (since sync is "smart" in the sense it downloads anything that doesn't exist).

However if you see this for a file across multiple syncs than it is a problem that you should file an issue about, or file a support case for.

@mcjelewis
Copy link

Thanks for the quick response.

The error came back again on the second sync/unpack process. This time I got it to work by updating node to v9.8. I'm not sure what version I was on previously, but I don't think I had updated in a while.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants