Skip to content

areas update fails after init #169

@zstadler

Description

@zstadler

I've built an Overpass instance without attic/history.

The init phase seems to complete successfully, including an the initial build of the areas:

overpass_tmp-1  | 2026-04-26T00:13:10.045446092Z Update finished with status code: 3
overpass_tmp-1  | 2026-04-26T00:13:10.050201349Z Generating areas...
overpass_tmp-1  | 2026-04-26T00:13:25.164851685Z <?xml version="1.0" encoding="UTF-8"?>
overpass_tmp-1  | 2026-04-26T00:13:25.164877924Z <osm version="0.6" generator="Overpass API 0.7.62 7c32a7d5">
overpass_tmp-1  | 2026-04-26T00:13:25.164892912Z <note>The data included in this document is from www.openstreetmap.org. The data is made available under ODbL.</note>
overpass_tmp-1  | 2026-04-26T00:13:25.164894966Z <meta osm_base="2026-04-26T00:11:54Z" areas="2026-04-26T00:11:54Z"/>
overpass_tmp-1  | 2026-04-26T00:13:25.164896268Z 
overpass_tmp-1  | 2026-04-26T00:13:25.165344578Z After 0h0m15s: in "query", part 4, on line 5. Stack: 0 of 0 0 of 0
overpass_tmp-1  | 2026-04-26T00:13:41.193825935Z After 0h0m31s: in "query", part 1, on line 13. Stack: 0 of 0 0 of 0

followed by

overpass_tmp-1  | 2026-04-26T02:09:13.001112734Z After 1h56m3s: in "recurse", part 0, on line 26. Stack: 0 of 0 1861485 of 0 0 of 0
overpass_tmp-1  | 2026-04-26T02:09:28.001031163Z After 1h56m18s: in "recurse", part 0, on line 26. Stack: 0 of 0 1868434 of 0 0 of 0
overpass_tmp-1  | 2026-04-26T02:09:35.454303364Z 
overpass_tmp-1  | 2026-04-26T02:09:35.454309926Z </osm>
overpass_tmp-1  | 2026-04-26T02:09:35.955876026Z Overpass container initialization complete. Exiting.
overpass_tmp-1 exited with code 0

However, when I started the container, the update succeeds, but the areas update fails with
runtime error: open64: /osm3s_osm_base Dispatcher_Client::request_read_and_idx::protocol_error:

overpass_tmp-1  | 2026-04-26T06:36:42.707092253Z 2026-04-26 06:36:42 DEBUG: https://planet.openstreetmap.org:443 "GET /replication/minute//007/086/708.osc.gz HTTP/1.1" 302 300
overpass_tmp-1  | 2026-04-26T06:36:42.735982369Z 2026-04-26 06:36:42 DEBUG: https://osm-planet-eu-central-1.s3.dualstack.eu-central-1.amazonaws.com:443 "GET /planet/replication/minute/007/086/708.osc.gz HTTP/1.1" 200 24402
overpass_tmp-1  | 2026-04-26T06:36:42.739818029Z 2026-04-26 06:36:42 DEBUG: Downloaded change 7086708. (52396 kB available in download buffer)
overpass_tmp-1  | 2026-04-26T06:36:43.708088978Z Running preprocessing command: 
overpass_tmp-1  | 2026-04-26T06:36:43.708792982Z /app/bin/update_from_dir --osc-dir=/db/diffs --version=2026-04-26T06:35:02Z --flush-size=16 --meta
overpass_tmp-1  | 2026-04-26T06:36:59.158702117Z Reading XML file ... finished reading nodes. 
overpass_tmp-1  | 2026-04-26T06:36:59.158707136Z [NGINX] 127.0.0.1 - - [26/Apr/2026:06:36:59 +0000] "GET /api/interpreter?data=[out:json];node(1);out; HTTP/1.1" 200 722 "-" "curl/7.88.1" "-"
overpass_tmp-1  | 2026-04-26T06:37:01.113048742Z Compute current ... ready. runtime error: open64: /osm3s_osm_base Dispatcher_Client::request_read_and_idx::protocol_error
overpass_tmp-1  | 2026-04-26T06:37:01.115109679Z It took 36 to run the loop. Desired load is: 10%. Sleeping: 324

The docker-compose config is:

  overpass_tmp:
    image: wiktorn/overpass-api
    user: "0:0"
    environment:
      OVERPASS_DIFF_URL: ${OVERPASS_DIFF_URL:-https://planet.openstreetmap.org/replication/minute/}
      # init mode only
      OVERPASS_MODE: init
      OVERPASS_META: yes
      OVERPASS_STOP_AFTER_INIT: true
      OVERPASS_PLANET_URL: ${OVERPASS_PLANET_URL:-https://planet.openstreetmap.org/planet/planet-latest.osm.bz2}
      OVERPASS_PLANET_PREPROCESS: ${OVERPASS_PLANET_PREPROCESS:-}
      OVERPASS_SPACE: ${OVERPASS_SPACE:-2200000000}
      OVERPASS_USE_AREAS: true
      OVERPASS_RULES_LOAD: 10      
      OVERPASS_ALLOW_DUPLICATE_QUERIES: yes
    volumes:
      - ./overpass/:/db
      - ./nginx-overpass/nginx.conf.template:/etc/nginx/nginx.conf.template
    # mem_limit: ${OVERPASS_SPACE:-2200000000}
    ports:
      - 127.0.0.1:8977:80

Any help would be greatly appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions