Not installing in my digitalocean box about node-geoip

[bluesmoon]

any change you could try with node 0.10.24? That's the one I tested with the last time this error was reported and it works. See the last few comments in issue #43

[GUI]

I believe this issue was fixed by #36. Since that hasn't been released to npm yet, the current version is still erroring out when "Washington, D.C" is encountered in the CSV parsing (due to the extra comma). If I run this updatedb command against 1.1.2 from npm, I run into this error every time, but if I run it from master, everything appears to work. Any chance you can release a new version on npm to fix this?

[bluesmoon]

@GUI I just pushed out 1.1.3, let me know if that fixes it.

[reinaldorauch]

I was trying to install with npm install geoip-lite, but:

[reinaldorauch]

The npm log: https://www.dropbox.com/s/evha27ho31ycm0l/npm-debug.log.tar.7z

[Amatewasu]

I have the same problem.

[Meroje]

Looks like you're low on ram.

[Amatewasu]

Thank you @Meroje, it works well after an upgrade of my VPS (512MB -> 2G).

[AlbertoRico]

Also on a Digital Ocean machine, but this error doesn't appear to relate to RAM.

Any idea?

[bluesmoon]

This looks like a problem with npm. You'll need to contact the npm
maintainers.

[paulleephp]

I was also getting error with installation with Exit status 137. After upgrading my digital ocean instance with 2 gigs of ram, I was able to install node-geoip successfully. During the installation process it looks like there is a lot of data being processed(1.9m rows).

[bluesmoon]

yes, the installation downloads and converts the city data.