search

sverhoeven / docker-cartodb

Dockerized CartoDB
BSD 3-Clause "New" or "Revised" License
148 stars 116 forks source link

Problems filling the internal geocoder #57

Closed christophekey closed 6 years ago

christophekey commented 6 years ago

Docker image all set up, tested and working. Go to fill the internal geocoder Run:

docker exec -ti bash -c /cartodb/script/fill_geocoder.sh

from clean docker container Varnish error - log - https://gist.github.com/christophekey/853ad3df5e9d1d83550aa13c724b726b

problem seems to result from Varnish and not respecting timeouts, so kill running varnish processes run again, completes and reports - Everything OK

log - https://gist.github.com/christophekey/5805653cab2ba4b40c503d5c7a6171f9

restart the container - geocoder only returns null in the geom table when running a geocode of IP to lat, lon.

Tried with a new clean build, issue persists.

sverhoeven commented 6 years ago

It has been a while since I used the geocoder. Just started a freshly build imager and ran the fill_geocoder.sh script I ignored the varnish warnings.

I tried 151.101.0.81 in the name column of a empty map and it got geocoded to {"type":"Point","coordinates":[-71.4652,42.9885]}.

How did you restart? Stop/start or kill+rm/run?

christophekey commented 6 years ago

Hey Stefan, Started from scratch, new VM on hypervisor, added --pull into the docker compose when building, ran the geocoder scripts again, reboot of the VM and things are working. I must have had a hiccup along the way ! thank you.