Overpass Installation fails: broken pipe

Hello,

I would like to setup a small private OSM Server in the cloud for testing an application. To achieve this, I've launched an AWS EC2 t2.micro instance and followed the installation steps from the Official OSM Install Guide.

In general the installation worked fine, at least for very small countries. I've successfully installed Andorra (Geofabrik-Link) and Faroe Islands (Geofabrik-Link) and was able to run queries on the instance.

When trying to do same with a little bit larger country, in this case Austria (Geofabrik-Link), i receive a "broken pipe" error:

Reading XML file ...terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc src/bin/init_osm3s.sh: line 44: 29086 Broken pipe bunzip2 < $PLANET_FILE 29087 Aborted (core dumped) | $EXEC_DIR/bin/update_database --db-dir=$DB_DIR/ $META $COMPRESSION

Can someone help me to get this fixed?

The resources of my EC2 instance currently are the following: - Ubuntu Server 16.04 LTS (HVM) - 1 GB RAM - ~25-30GB of free disk space (using AWS EBS)

My simple guess is that the resources are too low, especially the Memory of 1GB. Before I upgrade to more resources (I want to avoid costs as much as possible) and test again, I would like to how likely this would fix my problem? Also, can anybody tell me how much RAM and Disk Space I approximately need for a ~900MB OSM-file like Austria?

Update 1: In the meantime I've upgraded my machine and now have the following resources:

• Ubuntu 16.04 LTS
• 2vCPUs
• 7.5 GB RAM
• ~50 GB of free SSD disk space

I tried to run the Austria Import again. Unfortunately it failed again (shortly after starting the import) with a slightly different error:

Reading XML file ... elapsed node 1559520430. ./exec/bin/init_osm3s.sh: line 44: 18530 Broken pipe $ 18531 Killed | $EXEC_DIR/bin/update_database --db-dir=$DB_DIR/ $META $COMPRESSION

Again, I was able to import the very small country export Faroe-Island. I also tried importing a "medium" large country in terms of file size: Belgium. Running the import with Belgium showed no errors. (I manually canceled the import after around 5-10mins).

Is 7.5GB RAM still not enough? Or can it be another problem?

Update 2: Now I also tested importing a larger country, Czech Republic with a file size of ~1.1GB. Interestingly, the import again seemed to run without problems and I saw the import progress without any errors (i.e. many lines with "Reading XM L file...elapsed node xxxx. Flushing to databse ... done.) I cancelled after around 10min.

To summarize my import approaches:

• country | filesize | status
• austria | ~900MB | failed (both on 1GB RAM and 7.5GB RAM)
• faroe | ~3MB | worked (both)
• belgium | ~500MB | worked (on 7.5GB RAM)
• czechrep | ~1.1GB | worked (on 7.5GB RAM)

I can only guess, but since importing all countries (even larger one's) except for Austria seemed to work, I suspect there might be something wrong with the export hosted at Geofabrik? Anyone had similar problems before? Someone knows another server that hosts country files, or is there a way how I can find out if the file is "OK"?