Open MThurm opened 1 year ago
HINT: Check free disk space.
Have you checked the free disk space?
Sure.
I see. ext4.vhdx
is an auto-expanding virtual volume and there's plenty of disk space available.
Can you check the postgresql server logfile for errors?
This part of the Nominatim import is not recoverable, you'd have to start the import from the beginning. Usually errors I've seen with Postgresql crashing is disk space, network issues, virtual machine instability (if network mounted for example) and hardware (faulty RAM hardware). All outside of the control of the Nominatim software, only trying to rerun the process might work.
and get the following error: (its the second time, after days)
The osm2pgsql
step should take a couple of hours. Slow harddrive (HDD instead of SSD/Nvme) is significantly slower. If this step already took days for you then expect the full import to take weeks.
If this step already took days for you then expect the full import to take weeks.
That would not be a problem. I will try to install a 2TB NVME and run it again in the next days.
Thx for help
500GB should be enough. The whole planet needs 800-900GB.
Hi,
now I have a 1TB m2 NVME and there is a new Error:
ERROR: DB copy thread failed: Ending COPY mode for 'planet_osm_ways' failed: ERROR: could not extend file "base/16386/19931.87": No space left on device HINT: Check free disk space. CONTEXT: COPY planet_osm_ways, line 383892342 .
I added --shm-size=2g to the prompt, same Error.
"No space left on device" is pretty clear, isn't it? I would check how much space there is left on your partitions.
Hi, I found a solution. The problem was Docker under Windows.
Disable "use the WSL 2 based engine" under settings -> General and increase the virtual Disk Limit to maximum.
MFG
Hi, ignore my last post ... its not working... now I tried it in docker on ubuntu. Same Error ...
After trying some settings the Terminal now runs 3 days and ended with:
2023-05-29 12:25:27: Done 1073294/1073294 in 1113 @ 964.215 per second - FINISHED postcodes (location_postcode)
2023-05-29 12:26:25: Post-process tables /app/init.sh: line 81: 104 Killed sudo -E -u nominatim nominatim import --osm-file $OSMFILE --threads $THREADS
What happened now? Please help me :(
MFG
"Post-process tables" runs a lot of SQL queries. Check the postgresql logs for hints.
The Docker container now stopped two times, when I restart it, I can see that size still rising. Is there a chance it still work? sqllog.txt dockerlog.txt
Hello, how did you solve this please?? I have the same problem
Not at all. I now have it installed on Ubuntu without Docker.
@MThurm So it does work on Ubuntu without Docker? I have the same problem with docker (on Debian). My 2TB free disk space doesn't seem enough. I already created a script that logs the remaining disk space every 30 seconds to look back. It seems like the container hits a limit around 975GB usage.
Hi,
I used this prompt:
docker run -it -e PBF_URL=https://download.geofabrik.de/europe-latest.osm.pbf -e REPLICATION_URL=https://download.geofabrik.de/europe-updates/ -e NOMINATIM_FLATNODE_FILE=/nominatim/flatnode.file -e THREADS=8 -e POSTGRES_SHARED_BUFFERS=4GB -e POSTGRES_MAINTAINENCE_WORK_MEM=4GB -e POSTGRES_AUTOVACUUM_WORK_MEM=4GB -e POSTGRES_WORK_MEM=1GB -e POSTGRES_EFFECTIVE_CACHE_SIZE=1GB -e POSTGRES_SYNCHRONOUS_COMMIT=off -e POSTGRES_MAX_WAL_SIZE=1GB -e POSTGRES_CHECKPOINT_TIMEOUT=20min -e POSTGRES_CHECKPOINT_COMPLETITION_TARGET=0.9 -p 8080:8080 --name nominatim mediagis/nominatim:4.2
and get the following error: (its the second time, after days)
Its a 2 TB HDD, i3-8100 and 24Gb Ram maschine. Please help :/
MFG
PS: Sorry for bad english