Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Another geoip-lite installation failure #59

Closed
tonyjchong opened this issue Jun 19, 2014 · 4 comments
Closed

Another geoip-lite installation failure #59

tonyjchong opened this issue Jun 19, 2014 · 4 comments

Comments

@tonyjchong
Copy link

Hi Everyone,

Yes, another issue but my case is a little different than the other issues.

  • Running vagrant + ubuntu 12.04 + virtualbox
  • the VM has 3gb ram allocated

Most of the time I get this error when provision new machines

> geoip-lite@1.1.3 postinstall /vagrant/vungle/node_modules/geoip-lite
> npm run-script updatedb


> geoip-lite@1.1.3 updatedb /vagrant/vungle/node_modules/geoip-lite
> node scripts/updatedb.js

Retrieving GeoIPCountryCSV.zip ... DONE
Extracting GeoIPCountryCSV.zip ... DONE
Processing Data (may take a moment) ...
Still working (47700) ... DONE

Retrieving GeoIPv6.csv ... DONE
Processing Data (may take a moment) ... DONE

Retrieving GeoLiteCity-latest.zip ... DONE
Extracting GeoLiteCity-latest.zip ... DONE
Processing Data (may take a moment) ...
events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: ENOENT, open '/vagrant/vungle/node_modules/geoip-lite/tmp/GeoLiteCity/GeoLiteCity-Blocks.csv'

npm ERR! geoip-lite@1.1.3 updatedb: `node scripts/updatedb.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the geoip-lite@1.1.3 updatedb script.
npm ERR! This is most likely a problem with the geoip-lite package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/updatedb.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls geoip-lite
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.8.0-42-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "run-script" "updatedb"
npm ERR! cwd /vagrant/vungle/node_modules/geoip-lite
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /vagrant/vungle/node_modules/geoip-lite/npm-debug.log
npm ERR! not ok code 0
npm ERR! geoip-lite@1.1.3 postinstall: `npm run-script updatedb`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the geoip-lite@1.1.3 postinstall script.
npm ERR! This is most likely a problem with the geoip-lite package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run-script updatedb
npm ERR! You can get their info via:
npm ERR!     npm owner ls geoip-lite
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.8.0-42-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /vagrant/vungle
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /vagrant/vungle/npm-debug.log
npm ERR! not ok code 0

Sometimes I get this:

Retrieving GeoIPCountryCSV.zip ...ERROR: HTTP Request Failed [403 Forbidden]

Do you think you can help me with this? thanks a lot!

Tony

@RohovDmytro
Copy link

+1

@oschwald
Copy link

MaxMind rate limits downloads of GeoLite. You most likely are receiving this because you exceeded the limit.

@bluesmoon
Copy link
Collaborator

I'm tempted to turn off the update on install feature due to this.

@msimerson
Copy link

Turning off the update on install feature would have other benefits. Every project that installs node-geoip as a dependency ends up having to wait much longer for Travis CI tests to run. Humans installing the software also end up waiting much longer as well.

bluesmoon pushed a commit that referenced this issue Dec 4, 2014
This affects several issues, most notably Issue #59, Issue #72, Issue #67,
Issue #58, Issue #43.

This doesn't actually fix the issue since the user will have the same problem
when they try to update their db, but it gives them the option of installing
the package and manually updating the db.
STRML pushed a commit to STRML/node-geoip-country-only that referenced this issue Sep 12, 2016
This affects several issues, most notably Issue geoip-lite#59, Issue geoip-lite#72, Issue geoip-lite#67,
Issue geoip-lite#58, Issue geoip-lite#43.

This doesn't actually fix the issue since the user will have the same problem
when they try to update their db, but it gives them the option of installing
the package and manually updating the db.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants