[Geocoding] Nominatim data import error: ERROR: DB Error: no such table

[Gabriel Rossetti]

On 07/20/2012 08:45 PM, datendelphin wrote:
> On 18.07.2012 00:17, Gabriel Rossetti wrote:
>> /opt/Nominatim/osm2pgsql/osm2pgsql -lsc -O gazetteer --hstore -C 84 
>> -d nominatim /home/ubuntu/tmp/switzerland.osm.bz2
>> Using projection SRS 4326 (Latlong)
>> NOTICE:  table "place" does not exist, skipping
>> NOTICE:  type "keyvalue" does not exist, skipping
>> NOTICE:  type "wordscore" does not exist, skipping
>> NOTICE:  type "stringlanguagetype" does not exist, skipping
>> NOTICE:  type "keyvaluetype" does not exist, skipping
>> NOTICE:  function get_connected_ways(pg_catalog.int4[]) does not 
>> exist, skipping
>> 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=84MB, maxblocks=10753*8192, allocation method=11
>> Mid: pgsql, scale=10000000 cache=84
>> Setting up table: planet_osm_nodes
>> NOTICE:  table "planet_osm_nodes" does not exist, skipping
>> NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
>> "planet_osm_nodes_pkey" for table "planet_osm_nodes"
>> Setting up table: planet_osm_ways
>> NOTICE:  table "planet_osm_ways" does not exist, skipping
>> NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
>> "planet_osm_ways_pkey" for table "planet_osm_ways"
>> Setting up table: planet_osm_rels
>> NOTICE:  table "planet_osm_rels" does not exist, skipping
>> NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index 
>> "planet_osm_rels_pkey" for table "planet_osm_rels"
>>
>> Reading in file: /home/ubuntu/tmp/switzerland.osm.bz2
>> Segmentation fault (core dumped)
>> ERROR: DB Error: no such table
>> DB Error: no such table
> Hi
>
> So the problem above arises from a failed allocation. Osm2pgsql 
> allocates 1GB of memory (hard coded, see node-ram-cache.c:390) which 
> is not checked if the allocation succeeded.
>
> So that means for you: this ec2 instance has just too few memory (only 
> 600MB in total in the micro incarnation). There is the osm2pgsql 
> option --cache-strategy sparse, with which it works. But that is not 
> supported with the setup.php script (you could easily add this option 
> in setup.php on line 129, if you want to use it on the tiny ec2)
>
> And I certainly can not recommend running nominatim on Amazons cloud 
> computing. Nominatim is too demanding with I/O and caching and all to 
> run on that infrastructure.
>
> Hope that explains it for you, even if it won't help you too much.
>
> Datendelphin
>
>

Hi Datendelphin,

Thanks for looking into this. I see, I was using the Tiny version of 
their VMs since they are free, so that I can test and dev on them 
without being charged an arm and a leg. I will take into account what 
you said and see if I can find something else, is there any cloud 
service you would recommend for this? Again, than you for looking into 
this and finding the issue.

Thanks,
Gabriel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/geocoding/attachments/20120722/333e55a1/attachment.html>