Unexpected EOF while installing/downloading large packages

[yogeshwar-20]

My reason:

Installing larger packages (this one in this scenario) fails consistently from verdaccio with an unexpected EOF. The package is published to the local verdaccio server, not a redirection to the public registry. It installs fine from the public registry at https://registry.npmjs.org.

Even a simple wget ends abruptly

HTTP request sent, awaiting response... 
  HTTP/1.1 200 OK
  X-Powered-By: verdaccio/2.3.4
  Access-Control-Allow-Origin: *
  Content-Type: application/octet-stream
  Content-Length: 137211454
  X-Status-Cat: http://flic.kr/p/aVuVsF
  Date: Mon, 21 Aug 2017 11:43:35 GMT
  Connection: keep-alive
Length: 137211454 (131M) [application/octet-stream]
Saving to: ‘react-native-awesome-card-io-0.6.6.tgz.2’

react-native-awesome-card-io-0.6.6.tgz.2        65%[======================================================================>                                      ]  85.73M  13.6MB/s    in 6.1s    

2017-08-21 17:15:23 (14.1 MB/s) - Connection closed at byte 89897191. Retrying.

Steps to reproduce:

• Publish the package to Verdaccio
• Try installing it with yarn or npm

Issue is occurring when running the latest docker image, or on the host system with verdaccio installed through npm. Issue has persisted on both a Linux host and a macOS host.

It seems to occur on an erratic timeout basis (~7-10 seconds) because the download completes successfully if the download speed is high enough. The byte at which the connection closes is also not constant.

App Version:

2.3.4

Config file:

Default config file with only max_body_size increased to 300mb allow publishing packages of this size.

[juanpicado]

I will take a look it along the week.

[juanpicado]

Sorry, but I couldn't reproduce it. I doubt is an issue with verdaccio itself.

➜ npm install react-native-awesome-card-io                                         
npm WARN saveError ENOENT: no such file or directory, open '/Users/user/projects/hello_world_npm/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/Users/user/projects/hello_world_npm/package.json'
npm WARN hello_world_npm No description
npm WARN hello_world_npm No repository field.
npm WARN hello_world_npm No README data
npm WARN hello_world_npm No license field.

+ react-native-awesome-card-io@0.6.9
updated 1 package in 16.797s

I tried multiple ways to simulate network latency, packages drop, uplink delays etc. I would you suggest clean your cache or review your local environment. My tests were from a local Docker container, local instance via cli with v2.3.6.

I'll close this, feel free to reopen if the issue persists and try to provide more verbose output.

[yogeshwar-20]

Alright, thanks for your time! Already tried cleaning cache and fresh installs and there's nothing obvious that stands out in the local environment, but will dig deeper to try and identify the issue.

[cesarfd]

I've reproduced the same issue in this case with geoip-lite which is a fairly large package (~30MiB). It doesn't work no matter what I try, even after npm cache clean --force. I have verdaccio 2.3 running in an aws hosted Docker container.

It works perfectly with the standard npm registry.

This is the npm log:

1777 http fetch GET 200 https://npm.foo.bar/geoip-lite/-/geoip-lite-1.2.1.tgz 12714ms
1778 silly fetchPackageMetaData error for geoip-lite@~1.2 unexpected end of file
1779 verbose stack Error: unexpected end of file
1779 verbose stack     at Gunzip.zlibOnError (zlib.js:152:15)
1780 verbose cwd /Users/me/work/my-project
1781 verbose Darwin 16.7.0
1782 verbose argv "/Users/me/.nvm/versions/node/v8.5.0/bin/node" "/Users/me/.nvm/versions/node/v8.5.0/bin/npm" "i"
1783 verbose node v8.5.0
1784 verbose npm  v5.3.0
1785 error code Z_BUF_ERROR
1786 error errno -5
1787 error unexpected end of file
1788 verbose exit [ -5, true ]

geoip-lite-1.2.1.tgz is consistently well downloaded in verdaccio, though.

Edit, I've also tried it with a simple curl -O https://npm.foo.bar/geoip-lite/-/geoip-lite-1.2.1.tgz and the download ends up abruptly, same as @yogeshwar-20 case.

[yogeshwar-20]

Fwiw we weren't able to identify the actual cause, we were able to work around it however by setting up an nginx reverse proxy to verdaccio on the same host machine and accessing the registry through the proxy.

[cesarfd]

Thanks for the help, @yogeshwar-20 . Did you use any specific setting? Timeouts or anything like that? I tried with a squid proxy with no luck.

[yogeshwar-20]

Only keepalive and proxypass.

[pward123]

Running into the same issue when trying to pull ares-webos-sdk (> 42mb)