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

No Rendered Tiles #59

Closed
gareth-johnstone opened this issue Sep 10, 2019 · 5 comments
Closed

No Rendered Tiles #59

gareth-johnstone opened this issue Sep 10, 2019 · 5 comments

Comments

@gareth-johnstone
Copy link

Setup
Cores: 8
RAM: 32gb
SWAP: 120Ggb
Disk Space: ~7tb

Import
europe.osm.pbf imported by running the following command:

docker run \
    -v /home/pbf/europe-latest.osm.pbf:/data.osm.pbf \
    -v openstreetmap-data:/var/lib/postgresql/10/main \
    overv/openstreetmap-tile-server \
    import

This exited after 27 days saying it had managed to import.

Running the tile server
I've ran the following command:

docker run \
    -p 80:80 \
    -e ALLOW_CORS=1 \
    -e AUTOVACUUM=off \
    -e THREADS=6 \
    -v openstreetmap-data:/var/lib/postgresql/10/main \
    -v openstreetmap-rendered-tiles:/var/lib/mod_tile \
    -d overv/openstreetmap-tile-server \
    run

However, when i visit http://145.239.252.99/tile/0/0/0.png it shows a 404 - I'm kinda lost as to where to check next, any suggestions?

@Overv
Copy link
Owner

Overv commented Sep 10, 2019

Could you check the logs of the container to see if your requests are actually handled by it rather than something else? Also to see if there are possibly errors.

@gareth-johnstone
Copy link
Author

What command(s) and where should I check for these logs?

@Overv
Copy link
Owner

Overv commented Sep 10, 2019

To get the container name, run:

docker ps

And then view the logs with:

docker logs containername

@Istador
Copy link
Contributor

Istador commented Sep 10, 2019

This exited after 27 days saying it had managed to import.

Whoa, 27 days looks extreme. I thought you'd fixed the slow import, because you closed issue #16.

As mentioned in the other issue, I don't remember the exact duration, but when I imported Europe and Africa together, it only took about ~10-20 hours. (48 cores, 128 GB RAM, 1 TB SSD.)

stevo01 reported in #26 (comment) a runtime of 17.2 hours for importing Europe, that is more similar to your hardware specs. (8 cores, 64 GB RAM, 1 TB NVMe.)

Do you use HDD or SSD/NVMe disk space?

@gareth-johnstone
Copy link
Author

This exited after 27 days saying it had managed to import.

Whoa, 27 days looks extreme. I thought you'd fixed the slow import, because you closed issue #16.

As mentioned in the other issue, I don't remember the exact duration, but when I imported Europe and Africa together, it only took about ~10-20 hours. (48 cores, 128 GB RAM, 1 TB SSD.)

stevo01 reported in #26 (comment) a runtime of 17.2 hours for importing Europe, that is more similar to your hardware specs. (8 cores, 64 GB RAM, 1 TB NVMe.)

Do you use HDD or SSD/NVMe disk space?

its HDD not SSD - i think thats the biggest issue, they are in RAID 0 though

But yea, i did think it was kinda excessive, but im running the docker image as instructed!

To get the container name, run:

docker ps

And then view the logs with:

docker logs containername

Will run this today and report back!

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

3 participants