(Not sure this is the right forum category…)
Updates for our instance stopped working at some point. I believe it’s due to disk space on our server root drive. Can the base directory used by OSM for daily updates be changed from /tmp to a regular attached drive? Are there consequences?
Here are the relevant details. I believe the update is in process but failing…
Update File:
1123978372 May 5 18:36 /tmp/osm-3s_update_VHX3S0/osm-3s_update_VHX3S0/000003290.osc
Disk Space: (cannot easily change root drive, unfortunately)
$ df -kl /tmp
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/xvda1 8105416 7664288 340880 96% /
OSM Processes:
ec2-user 3577 1 0 May05 ? 00:00:57 /opt/sizzlescene/osm/overpass/osm-3s_v0.7.56.7/bin/dispatcher --osm-base --attic --rate-limit=2 --space=10737418240 --db-dir=/opt/sizzlescene/osm/overpass/db
ec2-user 3578 1 0 May05 ? 00:00:19 bash /opt/sizzlescene/osm/overpass/osm-3s_v0.7.56.7/bin/fetch_osc.sh 3289 Index of /replication/day /opt/sizzlescene/osm/overpass/replicate
ec2-user 3580 1 0 May05 ? 00:00:00 bash /opt/sizzlescene/osm/overpass/osm-3s_v0.7.56.7/bin/apply_osc_to_db.sh /opt/sizzlescene/osm/overpass/replicate 3289 --meta
ec2-user 4023 2377 0 14:18 pts/0 00:00:00 grep --color=auto osm
ec2-user 7737 3580 0 May05 ? 00:00:00 ./update_from_dir --osc-dir=/tmp/osm-3s_update_VHX3S0 --version=2021-09-15T00:00:00Z --meta --flush-size=0
Thanks for any pointers or requests for more info.
Jmelvin