Other v8 problem-exiting without explanation

MatsGej · April 1, 2024, 8:08am

I am trying to run openroutesservice v8 locally. But it exits in docker without any messages at all at this point:

2024-04-01 00:34:42 #################
2024-04-01 00:34:42 # Container ENV #
2024-04-01 00:34:42 #################
2024-04-01 00:34:42 ✓ CONTAINER_LOG_LEVEL: INFO. Set CONTAINER_LOG_LEVEL=DEBUG for more details.
2024-04-01 00:34:42 ⓘ Any config file settings can be overwritten by environment variables.
2024-04-01 00:34:42 ⓘ Use ‘CONTAINER_LOG_LEVEL=DEBUG’ to see the full list of active environment variables for this container.
2024-04-01 00:34:42 ###########################
2024-04-01 00:34:42 # Container sanity checks #
2024-04-01 00:34:42 ###########################
2024-04-01 00:34:42 ⓘ Running container as user root with id 0 and group 0
2024-04-01 00:34:42 ✓ ORS_HOME: /home/ors exists and is writable.
2024-04-01 00:34:42 ✓ The file /home/ors/config/example-ors-config.env is up to date
2024-04-01 00:34:42 ✓ The file /home/ors/config/example-ors-config.yml is up to date
2024-04-01 00:34:42 ✓ Using the existing ors-config.yml from: /home/ors/config/ors-config.yml
2024-04-01 00:34:42 ✓ Using graphs folder /home/ors/graphs
2024-04-01 00:34:42 ⓘ Any ENV variables will have precedence over configuration variables from config files.
2024-04-01 00:34:42 ✓ All checks passed. For details set CONTAINER_LOG_LEVEL=DEBUG.
2024-04-01 00:34:42 #####################################
2024-04-01 00:34:42 # Container file system preparation #
2024-04-01 00:34:42 #####################################
2024-04-01 00:34:42 ✓ The file /home/ors/files/example-heidelberg.osm.gz is up to date
2024-04-01 00:34:42 ✓ Removed graphs at /home/ors/graphs/*.
2024-04-01 00:34:42 ✓ Container file system preparation complete. For details set CONTAINER_LOG_LEVEL=DEBUG.
2024-04-01 00:34:42 #######################################
2024-04-01 00:34:42 # Prepare CATALINA_OPTS and JAVA_OPTS #
2024-04-01 00:34:42 #######################################
2024-04-01 00:34:42 ✓ CATALINA_OPTS and JAVA_OPTS ready. For details set CONTAINER_LOG_LEVEL=DEBUG.
2024-04-01 00:34:42 #####################
2024-04-01 00:34:42 # ORS startup phase #
2024-04-01 00:34:42 #####################
2024-04-01 00:34:42 ✓ 🙭 Ready to start the ORS application 🙭
2024-04-01 00:34:44
2024-04-01 00:34:44 . ____ _ __ _ _
2024-04-01 00:34:44 /\ / ’ __ _ () __ __ _ \ \ \
2024-04-01 00:34:44 ( ( )__ | '_ | '| | ’ / ` | \ \ \
2024-04-01 00:34:44 \/ )| |)| | | | | || (| | ) ) ) )
2024-04-01 00:34:44 ’ || .__|| ||| |_, | / / / /
2024-04-01 00:34:44 =========||==============|/=////
2024-04-01 00:34:44 :: Spring Boot :: (v3.1.6)
2024-04-01 00:34:44
2024-04-01 00:34:44 2024-03-31 22:34:44 INFO main [ o.h.o.a.Application ] Starting Application v8.0.0 using Java 21.0.2 with PID 1 (/ors.jar started by root in /home/ors)
2024-04-01 00:34:44 2024-03-31 22:34:44 INFO main [ o.h.o.a.Application ] The following 1 profile is active: “default”
2024-04-01 00:34:44 2024-03-31 22:34:44 INFO main [ o.h.o.a.ORSEnvironmentPostProcessor ]
2024-04-01 00:34:44 2024-03-31 22:34:44 INFO main [ o.h.o.a.ORSEnvironmentPostProcessor ] Configuration lookup started.
2024-04-01 00:34:44 2024-03-31 22:34:44 INFO main [ o.h.o.a.ORSEnvironmentPostProcessor ] Configuration file set by environment variable.
2024-04-01 00:34:44 2024-03-31 22:34:44 INFO main [ o.h.o.a.ORSEnvironmentPostProcessor ] Loaded file ‘/home/ors/config/ors-config.yml’
2024-04-01 00:34:44 2024-03-31 22:34:44 INFO main [ o.h.o.a.ORSEnvironmentPostProcessor ] Configuration lookup finished.
2024-04-01 00:34:44 2024-03-31 22:34:44 INFO main [ o.h.o.a.ORSEnvironmentPostProcessor ]
2024-04-01 00:34:45 2024-03-31 22:34:45 INFO ORS-Init [ o.h.o.a.s.l.ORSInitContextListener ] Initializing ORS…
2024-04-01 00:34:45 2024-03-31 22:34:45 INFO ORS-Init [ o.h.o.r.RoutingProfileManager ] Total - 1024 MB, Free - 941.11 MB, Max: 25 GB, Used - 82.89 MB
2024-04-01 00:34:45 2024-03-31 22:34:45 INFO ORS-Init [ o.h.o.r.RoutingProfileManager ] ====> Initializing profiles from ‘/home/ors/files/dach-latest.osm.pbf’ (1 threads) …
2024-04-01 00:34:45 2024-03-31 22:34:45 INFO ORS-Init [ o.h.o.r.RoutingProfileManager ] 2 profile configurations submitted as tasks.
2024-04-01 00:34:45 2024-03-31 22:34:45 INFO ORS-pl-walking [ o.h.o.r.RoutingProfile ] [1] Profiles: ‘foot-walking’, location: ‘/home/ors/graphs/walking’.
2024-04-01 00:34:46 2024-03-31 22:34:46 INFO ORS-pl-walking [ o.h.o.r.g.e.ORSGraphHopper ] version v4.9.1|2024-01-17T09:08:46Z (7,20,5,4,5,7)
2024-04-01 00:34:46 2024-03-31 22:34:46 INFO ORS-pl-walking [ o.h.o.r.g.e.ORSGraphHopper ] graph pedestrian_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
2024-04-01 00:34:46 2024-03-31 22:34:46 INFO ORS-pl-walking [ o.h.o.r.g.e.ORSGraphHopper ] No custom areas are used, custom_areas.directory not given
2024-04-01 00:34:46 2024-03-31 22:34:46 INFO ORS-pl-walking [ o.h.o.r.g.e.ORSGraphHopper ] start creating graph from /home/ors/files/dach-latest.osm.pbf
2024-04-01 00:34:46 2024-03-31 22:34:46 INFO ORS-pl-walking [ o.h.o.r.g.e.ORSGraphHopper ] using pedestrian_ors|RAM_STORE|3D|turn_cost|, memory:totalMB:1024, usedMB:287
2024-04-01 00:34:46 2024-03-31 22:34:46 INFO main [ o.h.o.a.Application ] Started Application in 3.076 seconds (process running for 4.21)
2024-04-01 00:34:46 2024-03-31 22:34:46 INFO main [ o.h.o.a.Application ] openrouteservice {“build_date”:“2024-03-21T13:55:54Z”,“version”:“8.0.0”}
2024-04-01 00:40:56 2024-03-31 22:40:56 INFO ORS-pl-walking [ o.h.o.r.g.e.ORSGraphHopper ] call cleanUp for ‘/home/ors/graphs/walking’
2024-04-01 00:40:56 2024-03-31 22:40:56 INFO ORS-pl-walking [ o.h.o.r.g.e.ORSGraphHopper ] graph pedestrian_ors|RAM_STORE|3D|turn_cost|7,20,5,4,5, details:edges:31 479 706(1081MB), nodes:24 667 832(471MB), name:(72MB), geo:163 872 290(626MB), bounds:5.8630797,25.1965582,45.8149497,60.2200367,-86.0,3799.0
2024-04-01 00:42:01 2024-03-31 22:42:01 INFO ORS-pl-walking [ o.h.o.r.g.e.ORSGraphHopper ] nodes: 24 667 832, edges: 31 479 706
2024-04-01 00:42:04 2024-03-31 22:42:04 INFO ORS-pl-walking [ o.h.o.r.g.e.ORSGraphHopper ] Bridge interpolation 1s, tunnel interpolation 1s, ferry interpolation 0s

MatsGej · April 1, 2024, 1:40pm

This is the docker-compose.yml file I am using:

Docker Compose file for the openrouteservice (ORS) application

Documentation and examples can be found on Running with Docker | openrouteservice backend documentation

version: ‘3.8’

services:

----------------- ORS application configuration -------------------

ors-app:
# Activate the following lines to build the container from the repository
# You have to add --build to the docker compose command to do so
build:
context: ./
container_name: ors-app
ports:
- “8080:8082” # Expose the ORS API on port 8080
- “9001:9001” # Expose additional port for monitoring (optional)
image: openrouteservice/openrouteservice:v8.0.0
# Advanced option! If you different ids to 0:0 and 1000:1000, you have to rebuild the container with the build args UID,GID.
# The user command is useful if you want easier bind mount access or better security.
#user: “1000:1000” # Run “mkdir -p ors-docker/config ors-docker/elevation_cache ors-docker/files ors-docker/graphs ors-docker/logs && sudo chown -R 1000:1000 ors” before starting the container!
volumes: # Mount relative directories. ONLY for local container runtime. To switch to docker managed volumes see ‘Docker Volumes configuration’ section below.
- /home/gmt_mats/openrouteservice_new/ors-docker:/home/ors # Mount the ORS application directory (for logs, graphs, elevation_cache, etc.) into its own directory
- graphs:/home/ors/graphs # Mount graphs directory individually
- elevation_cache:/home/ors/elevation_cache # Mount elevation cache directory individually
- config:/home/ors/config # Mount configuration directory individually
- logs:/home/ors/logs # Mount logs directory individually
# - .files:/home/ors/files # Mount files directory individually
- /home/mats_gmt/openrouteservice_new:/home/ors/files
environment:
REBUILD_GRAPHS: True # Set to True to rebuild graphs on container start.
CONTAINER_LOG_LEVEL: INFO # Log level for the container. Possible values: DEBUG, INFO, WARNING, ERROR, CRITICAL
# If you don’t want the default ors-config.yml you can specify a custom file name, that should match the file in
# your ‘config’ volume mount.
#ORS_CONFIG_LOCATION: /home/ors/config/my-ors-config.yml # Location of your ORS configuration file in the docker container

  # ------------------ JAVA OPTS ------------------ #
  # Configure the memory settings for JAVA or pass additional opts
  # Fore more available ENV properties see Prepare CATALINA_OPTS and JAVA_OPTS
  # in https://github.com/GIScience/openrouteservice/blob/main/docker-entrypoint.sh
  XMS: 1g  # start RAM assigned to jav
  XMX: 25g  # max RAM assigned to java. Rule of Thumb: <PBF-size> * <profiles> * 2
  # Example: 1.5 GB pbf size, two profiles (car and foot-walking)
  # -> 1.5 * 2 * 2 = 6. Set xmx to be AT LEAST `-Xmx6g`
  ADDITIONAL_JAVA_OPTS: ""  # further options you want to pass to the java command

  # ----------------- Properties configuration ------------------- #
  # Configure your whole container with only property ENVs.
  # These can be set alternatively or additionally to the yml configuration file.
  # Note, that any values set will override the corresponding values from the yml configuration file.
  # See the ors-config.env file for more options.
  # To have a configuration file-less container, uncomment at least the following properties.
  # The values are examples and provide the default configuration.
  ors.engine.source_file: /home/ors/files/dach-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.engine.profiles.walking.enabled: true
  # ors.engine.profiles.car.enabled: true
  # ors.engine.profiles.foot-walking.enabled: true

# ----------------- ENV file configuration ------------------- #
# Too many variables for your 'environment:' section?
# Use an env_file with the ENV properties instead and define everything in there:
# Values will be overwritten if set in the 'environment' section.
#env_file: ors-config.env

# ----------------- Healthcheck configuration ------------------- #
# The healthcheck is disabled by default. Uncomment the following lines to enable it.
# The healthcheck allows you to monitor the status of the ORS application.
# Be careful with long graph builds, as the healthcheck will fail and show 'unhealthy' during this time.
# This is especially useful if you run your ORS container in a production environment.
#healthcheck:
#  test: wget --no-verbose --tries=1 --spider http://localhost:8082/ors/v2/health || exit 1
#  start_period: 1m
#  interval: 10s
#  timeout: 2s
#  retries: 3
#  disable: false

----------------- Docker Volumes configuration -------------------

Define the Docker managed volumes for the ORS application. For more info on Docker Volumes see Volumes top-level elements | Docker Docs

Volumes are used to persist the data and configuration of the ORS application.

If you want to use volumes, uncomment the following lines and remove the ./ prefix from the volume paths in ‘services.ors-app.volumes’.

volumes:
graphs:
elevation_cache:
config:
logs:
files:
ors-docker: