-
Notifications
You must be signed in to change notification settings - Fork 25
Libpostal errors #9
Comments
Errors show up in the build process. Docker version 17.06.0-ce, build 02c1d87 Distributor ID: Ubuntu First set of no:
First set of errors:
|
These errors are very helpful. Is there a log of errors coming from the API container which uses libpostal? |
Logs from docker-compose up: |
I usually see a bunch of colorful warnings when compiling $ cat /etc/issue
Ubuntu 16.10 \n \l looking at your attached log file there seem to be other errors which need to be resolved such as:
@dianashk could you explain the process for downloading the |
Looking through the log file, it seems there are 2 issues:
I'm not sure what could cause such issues other than intermittent connectivity issues or lack of space on the mounted directory. When you started up the build script, what was DATA_DIR environment variable set to? If you list all the things in that directory after the build was finished what do you see? The data directory should look like this: $ ls -al /pelias/data/
drwxr-xr-x 3 systemd-resolve systemd-timesync 4096 Jul 28 19:53 elasticsearch
drwxr-xr-x 2 root root 4096 Jul 28 20:23 interpolation
drwxr-xr-x 3 root root 4096 Jul 28 19:54 openaddresses
drwxr-xr-x 2 root root 4096 Jul 28 19:54 openstreetmap
drwxr-xr-x 2 root root 4096 Jul 28 19:55 placeholder
drwxr-xr-x 2 root root 4096 Jul 28 19:55 polylines
drwxr-xr-x 4 root root 4096 Jul 28 19:54 tiger
drwxr-xr-x 4 root root 4096 Jul 28 19:54 whosonfirst And looking at the whosonfirst data subdirectory you should see this: $ ls -al /pelias/data/whosonfirst/data/
drwxr-xr-x 3 root root 4096 Jul 28 19:54 101
drwxr-xr-x 4 root root 4096 Jul 28 19:54 102
drwxr-xr-x 4 root root 4096 Jul 28 19:54 110
drwxr-xr-x 4 root root 4096 Jul 28 19:54 420
drwxr-xr-x 3 root root 4096 Jul 28 19:54 538
drwxr-xr-x 5 root root 4096 Jul 28 19:54 554
drwxr-xr-x 4 root root 4096 Jul 28 19:54 856
drwxr-xr-x 30 root root 4096 Jul 28 19:54 858 If you don't see the data in your data directory as mentioned above then something went wrong during data download steps. Last week I provisioned a new EC2 machine and tested the build script start to finish and did not run into any issues. The build script ran end-to-end and once it was done I was able to query the Pelias API and all the services were up and running. The machine was setup with the following:
|
I'm rebuilding and seeing something different this time. My original deployment didn't have all the data you show (maybe it got deleted since I used tmp? or my environment variable got unset?). I'll update when I know more. Not sure why my instance got suppperrr sloww. May I suggest you store the DATA_DIR in a different way? Perhaps inputted from a .env file or put it into the json config? And then maybe not suggest using /tmp/data/ and instead /pelias/data/ . |
@3vivekb, how are your setup efforts going? We've made some updates to the docker images, so be sure to pull down the latest from dockerhub before attempting another build. |
Hi all, with the recently merged PR #42, we've now switched completely over to using a pre-built service that provides libpostal. Thus I believe any issues like this are no longer possible. If there are questions or issues, don't hesitate to comment or re-open this issue. |
I've been trying a deployment on Ubuntu 16 (using the default config) and the build process around libpostal shows a lot of errors. The whole container does build successfully but when you try to run it error messages surround how libpostal is missing.
The text was updated successfully, but these errors were encountered: