-
Notifications
You must be signed in to change notification settings - Fork 53
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
/api/interpreter does not respond after initial clone, times out with 504 #130
Comments
Does it work, if you try with very small extract, like Monaco? |
Thank you for your timely reply. I used the 0.7.56.9 version of the image before, changed it to the latest image, and then accessed /api/interpreter, and then reported the error open64: 13 Permission denied /db/db//osm3s_osm_base Unix_Socket::7, Later, enter the container and run the chmod og+rx /db command. The problem is solved and you can access and use it normally. I hope OVERPASS_PLANET_URL can be modified to read local files, otherwise downloading data will be too slow. thank you |
Now I am encountering new problems, visit http://172.16.10.65:12345/api/interpreter?data=[out:xml][bbox:30.52116,104.04774,30.54482,104.07829]; ( node; way; relation; ); out meta;, error runtime error: open64: 2 No such file or directory /db/db/user_data.bin File_Blocks::File_Blocks::1 |
` public class OverpassAPI {
// String url = "http://overpass-api.de/api/interpreter";
I have been trying to solve this problem all day, but still haven't gained anything. I don't know which step went wrong, please help me. Thank you very much, I entered the container and indeed did not have the user_data.bin file,Where can I download the user_data.bin file? |
With the following docker-compose.yml file, after initially cloning and then restarting the service, the logs indicate that everything starts up correctly.

When I make an API call however, the service only responds with an HTTP 504 gateway timeout.
The logs after the second startup of the service (after clone)

The text was updated successfully, but these errors were encountered: