Can't update OSM data with 3.3 about nominatim-docker HOT 9 CLOSED

I had the same problem and it turned out that pyosmium-get-changes uses /usr/bin/python3 while Python scripts supplied with Nominatim refer to /usr/bin/python which in ubuntu:disco image is Python 2.7. Also, user postgres have no write permission to /app/src/build.

Here's the patch for Dockerfile I've used to workaround it.

--- 3.3/Dockerfile.orig	2019-05-28 13:52:56.347074000 +0200
+++ 3.3/Dockerfile	2019-06-05 16:19:29.442759114 +0200
@@ -40,6 +40,8 @@

 # Load initial data
 RUN curl http://www.nominatim.org/data/country_grid.sql.gz > /app/src/data/country_osm_grid.sql.gz
+RUN sed -i -e 's|bin/python|bin/python3|' /app/src/utils/*.py
+RUN chmod o=rwx /app/src/build

 EXPOSE 5432
 EXPOSE 8080

You can apply it with patch -p0 < patch-Docker.

from nominatim-docker.

Same issue

from nominatim-docker.

The issue here seems to be that the Pyosmium binary cannot be found where the update script is looking for it. Though it should be installed, according to the Dockerfile.

Run the command

whereis pyosmium-get-changes

inside the container and see what it shows.

Now go into your locals.php file and make sure the line

@define('CONST_Pyosmium_Binary', '/usr/local/bin/pyosmium-get-changes');

shows the correct path. I remember having that problem some time ago.

I remember having that problem some time ago and that was the reason why.

Edit:

I just tried it and my solution doesn't seem to work at all. It must have something to do with the fact that osmium is now installed without the --user argument.

from nominatim-docker.

I have the same issue. I have two docker container with postgres and apache but when I trying update db using command docker exec -it nominatim sudo -u postgres ./src/build/utils/update.php --import-osmosis-all I got

Currently at sequence 967 (04/07/2019 20:08:23) - 1 indexed
/usr/local/bin/pyosmium-get-changes --server http://download.geofabrik.de/europe/russia-european-part-updates -o /app/src/build/osmosischange.osc -s 30 -I 967
Traceback (most recent call last):
  File "/usr/local/bin/pyosmium-get-changes", line 243, in <module>
    exit(main(sys.argv[1:]))
  File "/usr/local/bin/pyosmium-get-changes", line 224, in main
    outhandler = WriteHandler(options.outfile)
RuntimeError: Open failed for '/app/src/build/osmosischange.osc': Permission denied

CONST_Pyosmium_Binary have currect path. Someone can help me with this issue?

from nominatim-docker.

@Wilfli you can use the patch I've supplied above. There's also a pull request #71 with that change.

from nominatim-docker.

Yes it work. Thanks

from nominatim-docker.

I had the same problem and it turned out that pyosmium-get-changes uses /usr/bin/python3 while Python scripts supplied with Nominatim refer to /usr/bin/python which in ubuntu:disco image is Python 2.7. Also, user postgres have no write permission to /app/src/build.

Here's the patch for Dockerfile I've used to workaround it.

--- 3.3/Dockerfile.orig	2019-05-28 13:52:56.347074000 +0200
+++ 3.3/Dockerfile	2019-06-05 16:19:29.442759114 +0200
@@ -40,6 +40,8 @@

 # Load initial data
 RUN curl http://www.nominatim.org/data/country_grid.sql.gz > /app/src/data/country_osm_grid.sql.gz
+RUN sed -i -e 's|bin/python|bin/python3|' /app/src/utils/*.py
+RUN chmod o=rwx /app/src/build

 EXPOSE 5432
 EXPOSE 8080

You can apply it with patch -p0 < patch-Docker.

I think better way is to use update-alternatives tool to change default version of python.
Like update-alternatives --install /usr/bin/python python /usr/bin/python3.7 1

from nominatim-docker.

It seems that the PR #71 from @therek has been merged, but it only provides a fix for version 3.3 and not for 3.4 version that has the same problem.
I tested the solution from @theHellDog on the 3.4 version and it worked for me:

# Fix python default version
RUN update-alternatives --install /usr/bin/python python /usr/bin/python3 3
RUN update-alternatives --install /usr/bin/python python /usr/bin/python2 2

from nominatim-docker.

@ErwanTremiot where exactly do you see the problem? I have built 3.4 with no changes regarding that issue and everything works as expected.

from nominatim-docker.