Not ready after ten a week of creating graph

[aukfood]

Is there an existing issue for this?

• I have searched the existing issues

Problem description

Hello, I start Openroute last week (Mars 25) with europe-latest.osm.pbf file for creating graphs, but since no change

curl https://url/ors/v2/health
{"status":"not ready"}`

Started logs 
`2024-03-25 14:39:24 INFO [o.h.o.r.RoutingProfileManager           ] - 1 profile configurations submitted as tasks.
2024-03-25 14:39:24 INFO [o.h.o.r.RoutingProfile                  ] - [1] Profiles: 'driving-car', location: '/home/ors/graphs/car'.
2024-03-25 14:39:24 INFO [o.h.o.r.g.e.c.CoreLMPreparationHandler  ] - Loaded landmark splitting collection from 
2024-03-25 14:39:24 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - version v4.9.1|2024-01-17T09:08:46Z (7,20,5,4,5,7)
2024-03-25 14:39:24 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - graph CH|car_ors|RAM_STORE|3D|turn_cost|,,,,, details:edges:0(0MB), nodes:0(0MB), name:(0MB), geo:0(0MB), bounds:1.7976931348623157E308,-1.7976931348623157E308,1.7976931348623157E308,-1.7976931348623157E308,1.7976931348623157E308,-1.7976931348623157E308, shortcuts:0 (0MB), nodesCH:-1 (0MB), shortcuts:0 (0MB), nodesCH:-1 (0MB), shortcuts:0 (0MB), nodesCH:-1 (0MB)
2024-03-25 14:39:24 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - No custom areas are used, custom_areas.directory not given
2024-03-25 14:39:24 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - start creating graph from /home/ors/files/europe-latest.osm.pbf
2024-03-25 14:39:25 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - using CH|car_ors|RAM_STORE|3D|turn_cost|,,,,, memory:totalMB:1024, usedMB:289
2024-03-25 14:39:25 INFO [o.h.o.a.Application                     ] - Started Application in 5.433 seconds (process running for 6.967)
2024-03-25 14:39:25 INFO [o.h.o.a.Application                     ] - openrouteservice {"build_date":"2024-03-21T13:55:54Z","version":"8.0.0"}

Proposed solution

It is normal ?

Additional context

• Linux distro : Debian 12
• docker 25.0.3
• proxy traefik

Thanks for you're help

Forum Topic Link

No response

[sfendrich]

No, this is not normal. If this is all of its output, it seems ORS is not even building the graphs.
Sometimes downloading the elevation tiles is slow.

[aukfood]

@sfendrich there is no progress status information with a curl request for exemple ?

[MatsGej]

I have the same problem. But the container exited without any messages. I have added some data here:https://ask.openrouteservice.org/t/other-v8-problem-exiting-without-explanation/5934

[sfendrich]

There is no option to get more information about the graph building process through the API. You might try enabling debug logging to get more information: https://giscience.github.io/openrouteservice/run-instance/configuration/spring/logging

[MatsGej]

I could not get it to create any debug logs even though I set both root and heigit to DEBUG.

But after fiddling with the file permissions I got it to run. I was using the dach-lastest pbf file and I got two errors in the generation that was strange:
2024-04-04 19:30:39 2024-04-04 17:30:39 ERROR car_ors_fastest_with_turn_costs_highways [ c.g.r.l.LandmarkStorage ] method findLandmarks for 53.3114637,10.1669325 (10149016) resulted in too few visited nodes: 1 vs expected minimum 10000, see #2256
2024-04-04 19:30:42 2024-04-04 17:30:42 ERROR car_ors_fastest_with_turn_costs_highways [ c.g.r.l.LandmarkStorage ] method findLandmarks for 52.4989297,7.9763652 (7147299) resulted in too few visited nodes: 1 vs expected minimum 10000, see #2256

[aukfood]

@sfendrich and @MatsGej I restart my stack with these in configuration :

    environment:
      - BUILD_GRAPHS=False
      - ors.engine.source_file=/home/ors/files/europe-latest.osm.pbf
      - ors.engine.graphs_root_path=/home/ors/graphs
      - ors.engine.elevation.cache_path=/home/ors/elevation_cache
      - ors.engine.profiles.car.enabled=true
      - ors.logging.level.root=DEBUG
      - ors.logging.level.org.heigit=DEBUG

But no more logs.

2024-04-09 08:53:04 INFO [o.h.o.a.Application                     ] - The following 1 profile is active: "default"
2024-04-09 08:53:04 INFO [o.h.o.a.ORSEnvironmentPostProcessor     ] - 
2024-04-09 08:53:04 INFO [o.h.o.a.ORSEnvironmentPostProcessor     ] - Configuration lookup started.
2024-04-09 08:53:04 INFO [o.h.o.a.ORSEnvironmentPostProcessor     ] - Configuration file set by environment variable.
2024-04-09 08:53:04 INFO [o.h.o.a.ORSEnvironmentPostProcessor     ] - Loaded file '/home/ors/config/ors-config.yml'
2024-04-09 08:53:04 INFO [o.h.o.a.ORSEnvironmentPostProcessor     ] - Configuration lookup finished.
2024-04-09 08:53:04 INFO [o.h.o.a.ORSEnvironmentPostProcessor     ] - 
2024-04-09 08:53:07 INFO [o.h.o.a.s.l.ORSInitContextListener      ] - Initializing ORS...
2024-04-09 08:53:07 INFO [o.h.o.r.RoutingProfileManager           ] - Total - 1024 MB, Free - 953.57 MB, Max: 2 GB, Used - 70.93 MB
2024-04-09 08:53:07 INFO [o.h.o.r.RoutingProfileManager           ] - ====> Initializing profiles from '/home/ors/files/europe-latest.osm.pbf' (1 threads) ...
2024-04-09 08:53:07 INFO [o.h.o.r.RoutingProfileManager           ] - 1 profile configurations submitted as tasks.
2024-04-09 08:53:07 INFO [o.h.o.r.RoutingProfile                  ] - [1] Profiles: 'driving-car', location: '/home/ors/graphs/car'.
2024-04-09 08:53:08 INFO [o.h.o.r.g.e.c.CoreLMPreparationHandler  ] - Loaded landmark splitting collection from 
2024-04-09 08:53:08 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - version v4.9.1|2024-01-17T09:08:46Z (7,20,5,4,5,7)
2024-04-09 08:53:08 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - graph CH|car_ors|RAM_STORE|3D|turn_cost|,,,,, details:edges:0(0MB), nodes:0(0MB), name:(0MB), geo:0(0MB), bounds:1.7976931348623157E308,-1.7976931348623157E308,1.7976931348623157E308,-1.7976931348623157E308,1.7976931348623157E308,-1.7976931348623157E308, shortcuts:0 (0MB), nodesCH:-1 (0MB), shortcuts:0 (0MB), nodesCH:-1 (0MB), shortcuts:0 (0MB), nodesCH:-1 (0MB)
2024-04-09 08:53:08 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - No custom areas are used, custom_areas.directory not given
2024-04-09 08:53:08 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - start creating graph from /home/ors/files/europe-latest.osm.pbf
2024-04-09 08:53:08 INFO [o.h.o.r.g.e.ORSGraphHopper              ] - using CH|car_ors|RAM_STORE|3D|turn_cost|,,,,, memory:totalMB:1024, usedMB:276
2024-04-09 08:53:09 INFO [o.h.o.a.Application                     ] - Started Application in 5.567 seconds (process running for 7.105)
2024-04-09 08:53:09 INFO [o.h.o.a.Application                     ] - openrouteservice {"build_date":"2024-03-21T13:55:54Z","version":"8.0.0"}

[MichaelsJP]

@aukfood thanks for opening the issue. You need to remove the ors. part from the logging config. The reason is that the logging part is handled by a library that listens to the logging.* namespace only. Be careful, it becomes very noisy in DEBUG ;).

So valid should be:

    environment:
      - BUILD_GRAPHS=False
      - ors.engine.source_file=/home/ors/files/europe-latest.osm.pbf
      - ors.engine.graphs_root_path=/home/ors/graphs
      - ors.engine.elevation.cache_path=/home/ors/elevation_cache
      - ors.engine.profiles.car.enabled=true
      - logging.level.root=DEBUG
      - logging.level.org.heigit=DEBUG

Here are two links for you with hopefully helpful information:

• The related documentation: https://giscience.github.io/openrouteservice/run-instance/configuration/spring/logging
• A raw list of all possible env parameters with their correct notation: https://github.com/GIScience/openrouteservice/blob/v8.0.0/ors-config.env

[qaniqani]

There must be an easier way to do this. 2 days passed until Heidelberg changed its data. I want to punch the monitor. There is a very complicated configuration. I'm tired of reading docs and forums.
It's hard not to go crazy for a custom configuration.
Still, if it works, I might punch the monitor with joy.
I wish everyone patience and success!

[MichaelsJP]

@qaniqani Sorry, for your frustration!
We have peak holiday season currently, I appreciate your patience with this.

Please share your docker-compose.yml with us. The complete one (without unrelated parts). There might be something inherently wrong or just not clear enough with it. Hard to judge, without looking into your setup.