Open devopsnot opened 1 year ago
Checking these logs I found that the tiles are not being updated
Always informing that the amount of update was equal to 0
Are the updates working?
I have the same issue:
[2023-04-18 07:28:01] 1954 start import from seq-nr , replag is
map_1 | [2023-04-18 07:29:01] 1977 start import from seq-nr , replag is
map_1 | [2023-04-18 07:30:01] 2000 start import from seq-nr , replag is
map_1 | [2023-04-18 07:31:01] 2023 start import from seq-nr , replag is
map_1 | [2023-04-18 07:32:01] 2046 start import from seq-nr , replag is
map_1 | [2023-04-18 07:33:01] 2069 start import from seq-nr , replag is
map_1 | [2023-04-18 07:34:01] 2092 start import from seq-nr , replag is
map_1 | [2023-04-18 07:35:01] 2215 start import from seq-nr , replag is
map_1 | [2023-04-18 07:36:01] 2276 start import from seq-nr , replag is
map_1 | [2023-04-18 07:37:01] 2383 start import from seq-nr , replag is
map_1 | [2023-04-18 07:38:01] 2406 start import from seq-nr , replag is
map_1 | Mapnik LOG> 2023-04-18 07:38:33: SVG PARSING ERROR:"SVG support error: <enable-background> attribute is not supported"
map_1 | Mapnik LOG> 2023-04-18 07:38:40: SVG PARSING ERROR:"SVG support error: <enable-background> attribute is not supported"
map_1 | Mapnik LOG> 2023-04-18 07:38:40: SVG PARSING ERROR:"SVG support error: <enable-background> attribute is not supported"
map_1 | Mapnik LOG> 2023-04-18 07:38:40: SVG PARSING ERROR:"SVG support error: <overflow> attribute is not supported"
map_1 | Mapnik LOG> 2023-04-18 07:38:40: SVG PARSING ERROR:"SVG support error: <enable-background> attribute is not supported"
map_1 | Mapnik LOG> 2023-04-18 07:38:40: SVG PARSING ERROR:"SVG support error: <enable-background> attribute is not supported"
map_1 | [2023-04-18 07:39:01] 2478 start import from seq-nr , replag is
map_1 | [2023-04-18 07:40:01] 2501 start import from seq-nr , replag is
map_1 | [2023-04-18 07:41:01] 2536 start import from seq-nr , replag is
No update information, replag and it start update every minute (never stops) with no result.
@IvanShift I had the same issue. Turned out the /data/.osmosis directory had not been migrated when I moved my data, and so the state required for the update job to run was missing. The result was exactly what you see here.
To resolve it, I connected to the container and ran the commands that are run initially when you set up updates during import:
REPLICATION_TIMESTAMP=osmium fileinfo -g header.option.osmosis_replication_timestamp /data/region.osm.pbf
sudo -E -u renderer openstreetmap-tiles-update-expire.sh $REPLICATION_TIMESTAMP
This restored the missing state in /data/.osmosis and allowed updates to resume. It didn't fix the entire issue, though. Not all changes that had happened were merged into my local db, so I ended up doing a full re-import anyway.
May be related to this case I just opened:
May be related to this case I just opened: #383
That's interesting. It seems it would completely void any config changes when running openstreetmap-tiles-update-expire.sh.
In my case, the required state was missing from disk, not from env. That's not to say your env issue didn't affect others in other ways.
I keep getting these logs below in a way, which are generated non-stop, getting complicated when I need to be performing a log analysis
I changed the updates in my 'docker-compose.yaml' file to this one below, but it keeps getting updates every minute