[Debian-astro-maintainers] Bug#984555: Fwd: Bug#984555: gavodachs2-server: fails to install/upgrade. breaks on executing SQL script.
James Van Zandt
jim.vanzandt at gmail.com
Fri Mar 12 01:51:31 GMT 2021
On Fri, 5 Mar 2021 12:08:06 +0100 Markus Demleitner <
msdemlei at ari.uni-heidelberg.de> wrote:
> > 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?
>
>
For what it's worth, I had the same error:
Setting up gavodachs2-server (2.3+dfsg-1) ...
createdb: database creation failed: ERROR: database "gavo" already exists
Creation of gavo database failed; assuming it's already there
and carrying on.
createuser: creation of new role failed: ERROR: role "dachsroot" already
exists
/usr/lib/python3/dist-packages/gavo/user/initdachs.py:310: UserWarning: SQL
script file for /usr/share/postgresql/contrib/pg_sphere.sql not found.
There are many reasons why that may be ok, but unless you know what you are
doing, you probably should install the corresponding postgres extension.
warnings.warn("SQL script file for %s not found. There are many"
/usr/lib/python3/dist-packages/gavo/user/initdachs.py:328: UserWarning: SQL
script file /usr/share/postgresql/contrib/pg_sphere.sql failed. Try
running manually using psql. While it hasn't run, the pgSphere extension
is not available.
warnings.warn("SQL script file %s failed. Try running manually"
/usr/lib/python3/dist-packages/gavo/user/initdachs.py:310: UserWarning: SQL
script file for /usr/share/postgresql/contrib/q3c.sql not found. There are
many reasons why that may be ok, but unless you know what you are doing,
you probably should install the corresponding postgres extension.
warnings.warn("SQL script file for %s not found. There are many"
/usr/lib/python3/dist-packages/gavo/user/initdachs.py:328: UserWarning: SQL
script file /usr/share/postgresql/contrib/q3c.sql failed. Try running
manually using psql. While it hasn't run, the q3c extension is not
available.
warnings.warn("SQL script file %s failed. Try running manually"
*** Error: While executing DB query:
select * from dc.rdmeta where sourceRD='__system__/dc_tables'
the database engine reported:
ERROR: schema "dc" does not exist
LINE 1: select * from dc.rdmeta where
sourceRD='__system__/dc_tables...
^
I tried your suggestion, but didn't get very far:
$ psql gavo
psql: error: FATAL: role "jrv" does not exist
Let me know if there's something else you want to cross-check.
(I am a fairly knowledgeable Debian user, but not an SQL user. )
- Jim Van Zandt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-astro-maintainers/attachments/20210311/225a4e97/attachment.htm>
More information about the Debian-astro-maintainers
mailing list