[Geocoding] error on nominatim updates
Jorge Hequera
jorgehequera at gmail.com
Tue Dec 17 14:51:42 UTC 2019
Hi there, I have an issue when I try to get updates from de cmdline:
./utils/update.php --import-osmosis-all
(...)
Done 330099 in 2463 @ 134.023148 per second - Rank 30 ETA (seconds):
1.417666
Done 330221 in 2464 @ 134.018265 per second - Rank 30 ETA (seconds):
0.507394
Done 330383 in 2465 @ 134.029617 per second - Rank 30 ETA (seconds):
-0.701338
Done 330449 in 2466 @ 134.002029 per second - ETA (seconds): -1.194012
Done 331163 in 2466 @ 134.291565 per second - ETA (seconds): -6.508227
Done 331163 in 2466 @ 134.291565 per second - FINISHED
string(187) "INSERT INTO import_osmosis_log(batchend, batchseq, batchsize,
starttime, endtime, event) values ('2019-11-01
23:58:59+00:00',2607,NULL,'2019-12-17 04:08:12','2019-12-17
05:39:44','index')"
2019-12-17 05:39:44 Completed index step for 2019-11-01 23:58:59+00:00 in
91.53 minutes
2019-12-17 05:39:44 Completed all for 2019-11-01 23:58:59+00:00 in 114.78
minutes
Currently at sequence 2607 (01/11/2019 23:58:59) - 1 indexed
/srv/nominatim/.local/bin/pyosmium-get-changes --server
https://planet.openstreetmap.org/replication/day -o
/srv/nominatim/Nominatim-3.4.0/build/osmosischange.osc -s 30 -I 2607
/srv/nominatim/Nominatim-3.4.0/build/osm2pgsql/osm2pgsql -klas
--number-processes 1 -C 2000 -O gazetteer -S
/srv/nominatim/Nominatim-3.4.0/settings/import-full.style -d nominatim -P
5432 --flat-nodes /srv/nominatim/Nominatim-3.4.0/data/planet.bin
/srv/nominatim/Nominatim-3.4.0/build/osmosischange.osc
osm2pgsql version 1.2.0 (64 bit id space)
Allocating memory for dense node cache
Allocating dense node cache in one big chunk
Allocating memory for sparse node cache
Sharing dense sparse
Node-cache: cache=2000MB, maxblocks=32000*65536, allocation method=11
Mid: loading persistent node cache from
/srv/nominatim/Nominatim-3.4.0/data/planet.bin
Mid: pgsql, cache=2000
Parsing gazetteer style file
'/srv/nominatim/Nominatim-3.4.0/settings/import-full.style'.
Using projection SRS 4326 (Latlong)
Reading in file: /srv/nominatim/Nominatim-3.4.0/build/osmosischange.osc
Using XML parser.
Processing: Node(1916k 10.3k/s) Way(346k 2.44k/s) Relation(9420 24.47/s)
parse time: 713s
Node stats: total(1916176), max(6940299180) in 186s
Way stats: total(346274), max(741344763) in 142s
Relation stats: total(9471), max(10250591) in 385s
result COPY END for place failed: ERROR: value too long for type character
varying(2)
CONTEXT: SQL statement "INSERT INTO import_polygon_error (osm_type,
osm_id, class, type, name, country_code, updated, errormessage,
prevgeometry, newgeometry)
VALUES (NEW.osm_type, NEW.osm_id, NEW.class, NEW.type, NEW.name,
NEW.address->'country', now(),
'Area reduced from '||st_area(existing.geometry)||' to
'||st_area(NEW.geometry), existing.geometry, NEW.geometry)"
PL/pgSQL function place_insert() line 107 at SQL statement
COPY place, line 19: "1943188 R boundary administrative
"alt_name:ar"=>"جامو وكشمير","name"=>"Jammu and Kashmir"..."
DB writer thread failed due to ERROR: Ending COPY mode
Error executing osm2pgsql: 2
Before this execution of the update process, I try to get updates several
times, but some preexistent bugs (fixed) interrupt the process.
For further reference of the commented issues:
https://github.com/openstreetmap/Nominatim/issues/1600
https://github.com/openstreetmap/Nominatim/issues/1550
https://github.com/openstreetmap/Nominatim/issues/1598
https://github.com/openstreetmap/Nominatim/issues/1594
Actually I see a error on the copy (INSERT) step:
*result COPY END for place failed: ERROR: value too long for type
character varying(2)*
But I don't know how if I need to fix that statement manually or if there's
a policy to report this error to the mantainer or the person who does the
commit into the https://planet.openstreetmap.org/replication/day repo.
Thanks in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/geocoding/attachments/20191217/4294a6bc/attachment.html>
More information about the Geocoding
mailing list