https://github.com/openstreetmap/Nominatim/issues/409 I met the same error in postgres_10.3 and my server details: CentOS7.4, 128GB RAM, 3TB HD. As suggested using following cmd to indexing: ./utils/setup.php --index --create-search-indices How to fix the same permenently? Is there any postgres config to solve the same? asked 08 Oct '18, 11:52  Rajavelu_M edited 08 Oct '18, 11:55 |
One Answer:
Error "buffer 82340 is not owned by resource owner" That issue also came up in https://github.com/openstreetmap/Nominatim/issues/1168 again. See my answer there. Root cause is still a mystery. Restarting the import with less threads seems to work. answered 08 Oct '18, 12:51  mtmail showing 5 of 6 show 1 more comments |
@mtmail: Thanks for your answer. 1 doubt: i just running ./utils/setup.php --index --create-search-indices after met that err. Is it enough?
OR Need to run ./utils/setup.php --index --create-country-names --index-noanalyse (From Lonvia's reply in that thread #1168) ?
Depends at which step our import failed. See http://nominatim.org/release-docs/latest/admin/Faq/#can-a-stoppedkilled-import-process-be-resumed
@mtmail Thanks & sorry for asking again. My initial import failed while indexing 30th rank. now i am running ./utils/setup.php --index --create-search-indices Is it enough? or need to run ./utils/setup.php --index --create-country-names --index-noanalyse again ?
Note: Its running for more than 6+ hrs. Checked my old setup logs(import planet data few weeks before), Create Search indices takes less than 3 hrs only
(7h later) Is the index creation still running, do you see CPU (top) and disc access (iotop). Do you see index related queries blocked by other sessions in
select pid, usename, pg_blocking_pids(pid) as blocked_by, query as blocked_query from pg_stat_activity where cardinality(pg_blocking_pids(pid)) > 0;?Reason for slowness is drop index is waiting for autovacuum completion.
blocked_pid | blocked_user | blocking_pid | blocking_user | blocked_statement | current_statement_in_blocking_process
-------------+--------------+--------------+---------------+----------------------------------------------+------------------------------------------------------------------ 721 | nomiuser | 6839 | | DROP INDEX IF EXISTS idx_placex_rank_search; | autovacuum: VACUUM ANALYZE public.placex (to prevent wraparound)
You can kill the autovacuum. It runs regularly in the background (well, foreground in this case it seems) and will restart automatically. https://blog.sleeplessbeastie.eu/2014/07/23/how-to-terminate-postgresql-sessions/