Unable to read the state from the server. with connection timeout

Help and support
1

HI All

I need help on following error

Case:

I am using docker deployment using overv/openstreetmap-tile-server : latest (Digest 8685e981fd97).

As per the document, my import process worked fine with the command below

docker run
-e UPDATES=enabled
-v /home/map-latest/map-pbf-data/great-britain-latest.osm.pbf:/data/region.osm.pbf
-v /home/map-latest/map-pbf-data/great-britain.poly:/data/region.poly
-v /home/map-latest/openstreetmap-postgresql-data:/data/database/
-v /home/map-latest/openstreetmap-rendered-tiles:/data/tiles/
-d
–name openstreetmap-tile-server
overv/openstreetmap-tile-server:latest
import

But failing command to run

docker container run
-p 6081:80
-p 7432:5432
-e PGPASSWORD=qaIACxO6wMR3
-e ALLOW_CORS=enabled
-e UPDATES=enabled
-e THREADS=24
-e HTTP_PROXY=xx/
-e HTTPS_PROXY=xx/
-e http_proxy=xx /
-e https_proxy=xx /
-e REPLICATION_URL=’ ’
-e MAX_INTERVAL_SECONDS=3600
-v /home/map-latest/openstreetmap-postgresql-data:/data/database/
-v /home/map-latest/openstreetmap-rendered-tiles:/data/tiles/
–name map-latest
–restart always
-d overv/openstreetmap-tile-server:latest
run

Error log is please advice

** INFO: 07:00:37.600: Initialising unix server socket on /run/renderd/renderd.sock
** INFO: 07:00:37.605: Renderd is using mapnik version 3.1.0
** INFO: 07:00:38.706: Running in foreground mode…
** INFO: 07:00:38.707: Loading parameterization function for
** INFO: 07:00:38.707: Loading parameterization function for
** INFO: 07:00:38.707: Loading parameterization function for
** INFO: 07:00:38.710: Loading parameterization function for
** INFO: 07:00:38.710: Loading parameterization function for
** INFO: 07:00:38.711: Loading parameterization function for
** INFO: 07:00:38.713: Loading parameterization function for
** INFO: 07:00:38.713: Loading parameterization function for
** INFO: 07:00:38.714: Loading parameterization function for
** INFO: 07:00:38.714: Loading parameterization function for
** INFO: 07:00:38.713: Loading parameterization function for
** INFO: 07:00:38.715: Loading parameterization function for
** INFO: 07:00:38.714: Loading parameterization function for
** INFO: 07:00:38.714: Loading parameterization function for
** INFO: 07:00:38.716: Loading parameterization function for
** INFO: 07:00:38.716: Loading parameterization function for
** INFO: 07:00:38.716: Loading parameterization function for
** INFO: 07:00:38.716: Loading parameterization function for
** INFO: 07:00:38.716: Loading parameterization function for
** INFO: 07:00:38.716: Loading parameterization function for
** INFO: 07:00:38.716: Loading parameterization function for
** INFO: 07:00:38.716: Loading parameterization function for
** INFO: 07:00:38.716: Loading parameterization function for
** INFO: 07:00:38.715: Loading parameterization function for
** INFO: 07:00:40.454: Updating max_connection parameter for mapnik layers to reflect thread count
[2026-09-25 07:01:01] 486 start import from seq-nr 122582, replag is 1591261s
[2026-09-25 07:01:01] 486 downloading diff
Sep 25, 2026 7:01:03 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.48.3
Sep 25, 2026 7:01:05 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Preparing pipeline.
Sep 25, 2026 7:01:05 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Launching pipeline execution.
Sep 25, 2026 7:01:05 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Pipeline executing, waiting for completion.
[2026-09-25 07:02:01] 953 pid 486 still running
** INFO: 07:02:05.160: Updating max_connection parameter for mapnik layers to reflect thread count
** INFO: 07:02:08.028: Updating max_connection parameter for mapnik layers to reflect thread count
** INFO: 07:02:08.604: Updating max_connection parameter for mapnik layers to reflect thread count
** INFO: 07:02:12.394: Updating max_connection parameter for mapnik layers to reflect thread count
** INFO: 07:02:34.072: Updating max_connection parameter for mapnik layers to reflect thread count
** INFO: 07:02:57.079: Updating max_connection parameter for mapnik layers to reflect thread count
[2026-09-25 07:03:02] 1637 pid 486 still running
Sep 25, 2026 7:03:20 AM org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager waitForCompletion
SEVERE: Thread for task 1-read-replication-interval failed
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Unable to read the state from the server.
at org.openstreetmap.osmosis.replication.common.ServerStateReader.getServerState(ServerStateReader.java:95)
at org.openstreetmap.osmosis.replication.common.ServerStateReader.getServerState(ServerStateReader.java:46)
at org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.runImpl(BaseReplicationDownloader.java:273)
at org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.run(BaseReplicationDownloader.java:372)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.net.ConnectException: Connection timed out (Connection timed out)
at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)

2

It looks like that’s using Osmosis to set up the download of minutely diffs from planet.osm.org

This is just speculation, but it’s possible that either your deployment of this or new Osmosis-based setups in general are struggling because something has changed in the way that the things stored on planet.osm.org are referenced.

The docker setup hasn’t been touched for 11 months. At switch2osm.org you can see three “Updating your database as people edit OpenStreetMap” options - osm2pgsql (easy to set up, and best for most people), PyOsmium (flexible and recommended for everyone else) and Osmosis (not really recommended, but documented as it still worked when I last tested it)

If you absolutely must use Docker I’d suggest creating a new Dockerfile based the Debian 13 Flex setup and either the osm2pgsql or PyOsmium updates. If Docker isn’t a hard requirement and you’re using infrastructure with some support for virtual machines create a minimal Debian VM and use that.

3

We haven’t changed anything in the last 11 months. Since the user has indicated they’ve set HTTP Proxy options there’s a good chance it’s connected to that.

4

I have confirmed this issue has been occurring since tag 2.2.0. how to get this working if I have to go with docker docker container run
-p 6081:80
-p 7432:5432
-e PGPASSWORD=‘pass’
-e ALLOW_CORS=enabled
-e UPDATES=enabled
-e MAX_INTERVAL_SECONDS=86400
-v /home/map-luxembourg/openstreetmap-postgresql-data:/data/database/
-v /home/map-luxembourg/openstreetmap-rendered-tiles:/data/tiles/
-v /home/map-luxembourg/logs:/var/log/tiles/
–name map-lux
–restart always
-d overv/openstreetmap-tile-server:2.2.0
run I am missing anything
I can see the postgres folder structure been changed since this tag. is this commend ok?