> createdb: database creation failed: ERROR: database "gavo" already exists > Creation of gavo database failed; assuming it's already there > and carrying on.
This means that there has been a DaCHS on that machine before, i.e., that this is an upgrade. Is that right? If so, then this message is expected (and we ought to hide it one of these days). > /usr/lib/python3/dist-packages/gavo/user/initdachs.py:310: UserWarning: SQL > script file for /usr/share/postgresql/contrib/pg_sphere.sql not found. This is where things go wrong. DaCHS should not even try to load the pgsphere SQL, as all pgspheres that can possibly in use now already use the new Postgres extension system. So, why does it try this? This: > Versions of packages gavodachs2-server depends on: > ii postgresql-pgsphere [postgresql-11-pgsphere] 1.1.1+2018.10.13-1 is essentially as it should be. I wonder if it has been like this at the time of the DaCHS installation. But let's see if things are properly there now. Could you run psql gavo and then in psql select * from pg_available_extensions where name='pg_sphere'; What does that say?
