OSM Import Error about openstreetmap HOT 5 CLOSED

Hey @KentJacobs,
I haven't seen this error before, but it looks like it might be related to an issue in the elasticsearch NPM module. Could you dig in and find a couple versions for me? First the version of Elasticsearch itself (can be found at http://localhost:9200/), then the git revision of our osm importer (/home/vagrant/openstreetmap), and finally the elasticsearch NPM module (can be found at /home/vagrant/openstreetmap/node_modules/pelias-dbclient/node_modules/elasticsearch).

I also wasn't able to reproduce this issue locally myself but if you can manage to try a newer version of the elasticsearch NPM module, that might help. Let me know how it goes, and hopefully we can figure it out based on that info.

from openstreetmap.

vagrant@pelias:~/openstreetmap$ curl http://localhost:9200/
{
  "status" : 200,
  "name" : "pelias",
  "cluster_name" : "elasticsearch",
  "version" : {
    "number" : "1.7.0",
    "build_hash" : "929b9739cae115e73c346cb5f9a6f24ba735a743",
    "build_timestamp" : "2015-07-16T14:31:07Z",
    "build_snapshot" : false,
    "lucene_version" : "4.10.4"
  },
  "tagline" : "You Know, for Search"
}

/home/vagrant/openstreetmap
File: package.json
{
   "name": "pelias-openstreetmap",
   "author": "mapzen",
   "version": "3.1.1"....

/home/vagrant/openstreetmap/node_modules/pelias-dbclient/node_modules/elasticsearch
File: package.json
{
....
   "_npmVersion": "1.4.14"
...
}

Hopefully this helps!

from openstreetmap.

Hmm, other than reminding me to upgrade the vagrant image's Elasticsearch version to 1.7.3, unfortunately not really. I just spun up a vagrant image but can't reproduce. How old is your Vagrant image? Things change frequently, especially with NPM modules.

Two more things to try though:

1. delete the node_modules directory for openstreetmap: rm -rf ~/openstreetmap/node_modules. It fixes way more problems than it should unfortunately
2. Send along your entire ~/pelias.json. Presumably it looks something like the one in the docs, which I just tested and works fine (after changing the datapath to /opt/pelias/data/osm to match where the vagrant image stores data). It's possible there's some combination of config settings our code doesn't like.

from openstreetmap.

Running an import seems to work now. I ran node index.js and it finished without error in 2-3 minutes. I can curl and specify osm as a source now.

I deleted node_modules in openstreetmap, then I created a new ~/pelias.json file in case and re-installed node_modules with npm install in openstreetmap. This seemed to fix the issue. 👍

Thank you for your help!

from openstreetmap.

Deleting node_modules is the NPM equivalent of rebooting a computer: it fixes many problems but no one knows why. Enjoy :)

from openstreetmap.