You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@madlib.apache.org by Nikolay Samokhvalov <sa...@gmail.com> on 2017/01/23 05:59:57 UTC
Installation failed on Postgres, Debian
Hi,
I successfully installed MADlib (from git, HEAD) on one of Debian machines,
it worked very well.
But then I needed to install it on the different machine, with the same
Linux version/kernel, but without libc, cmake and so on and policy that
prohibits installing it. So I copied the "/usr/local/madlib" content from
the first machine to the second one, then and tried to install MADlib a
Postgres DB.
And it failed:
root@db2 ~ # /usr/local/madlib/bin/madpack -p postgres -c dbuser@localhost/test
install
madpack.py : INFO : Detected PostgreSQL version 9.6.
madpack.py : INFO : *** Installing MADlib ***
madpack.py : INFO : MADlib tools version = 1.10.0-dev
(/usr/local/madlib/Versions/1.10.0-dev/bin/../madpack/madpack.py)
madpack.py : INFO : MADlib database version = None (host=localhost:5432,
db=test, schema=madlib)
madpack.py : INFO : Testing PL/Python environment...
madpack.py : INFO : > PL/Python environment OK (version: 2.7.9)
madpack.py : INFO : Installing MADlib into MADLIB schema...
madpack.py : INFO : > Creating MADLIB schema
madpack.py : INFO : > Creating MADLIB.MigrationHistory table
madpack.py : INFO : > Writing version info in MigrationHistory table
madpack.py : INFO : > Creating objects for modules:
madpack.py : INFO : > - array_ops
madpack.py : ERROR : Failed executing m4 on
/usr/local/madlib/Versions/1.10.0-dev/ports/postgres/modules/array_ops/array_ops.sql_in
madpack.py : INFO : Rolling back the installation...
madpack.py : INFO : Rollback finished successfully.
madpack.py : ERROR : MADlib installation failed.
In Postgres log at the same time:
2017-01-23 08:53:37 MSK [5240]: [1-1] db=test,user=dbuser NOTICE: function
plpy_version_for_madlib() does not exist, skipping
2017-01-23 08:53:37 MSK [5240]: [2-1] db=test,user= dbuser STATEMENT: DROP
FUNCTION IF EXISTS plpy_version_for_madlib();
2017-01-23 08:53:37 MSK [5280]: [1-1] db=test,user= dbuser ERROR: schema
"madlib" does not exist at character 14
2017-01-23 08:53:37 MSK [5280]: [2-1] db=test,user= dbuser STATEMENT:
CREATE TABLE madlib.__madlib_test_table (A INT);
2017-01-23 08:53:37 MSK [5300]: [1-1] db=test,user= dbuser NOTICE: table
"migrationhistory" does not exist, skipping
2017-01-23 08:53:37 MSK [5300]: [2-1] db=test,user= dbuser STATEMENT: DROP
TABLE IF EXISTS madlib.migrationhistory;
2017-01-23 08:53:38 MSK [5331]: [1-1] db=test,user= dbuser NOTICE: drop
cascades to table madlib.migrationhistory
2017-01-23 08:53:38 MSK [5331]: [2-1] db=test,user= dbuser STATEMENT: DROP
SCHEMA madlib CASCADE;
BTW, it is pretty strange and inconsistent that installation doesn't stop
on ERROR, trying to create something else after that.
Both machines are:
Linux db2 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64
GNU/Linux
Postgres versions are also the same:
PostgreSQL 9.6.1 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10)
4.9.2, 64-bit
Any ideas why is to and how to fix?
Re: Installation failed on Postgres, Debian
Posted by Nikolay Samokhvalov <sa...@gmail.com>.
It seems you're right, the reason is that machine lacks m4. I repeated it
in similar environment but with m4, it works perfectly.
On Monday, January 23, 2017, Satoshi Nagayasu <sn...@uptime.jp> wrote:
> Hi,
>
> > madpack.py : ERROR : Failed executing m4 on /usr/local/madlib/Versions/1.
> 10.0-dev/ports/postgres/modules/array_ops/array_ops.sql_in
>
> I'm not familiar with the installation procedure, but it looks having
> some issue around m4 which is spawned in the procedure.
> Do you have the same configuration for m4 on both boxes?
>
> Regards,
>
>
> 2017-01-23 14:59 GMT+09:00 Nikolay Samokhvalov <samokhvalov@gmail.com
> <javascript:;>>:
> > Hi,
> >
> > I successfully installed MADlib (from git, HEAD) on one of Debian
> machines,
> > it worked very well.
> >
> > But then I needed to install it on the different machine, with the same
> > Linux version/kernel, but without libc, cmake and so on and policy that
> > prohibits installing it. So I copied the "/usr/local/madlib" content from
> > the first machine to the second one, then and tried to install MADlib a
> > Postgres DB.
> >
> > And it failed:
> >
> > root@db2 ~ # /usr/local/madlib/bin/madpack -p postgres -c
> > dbuser@localhost/test install
> > madpack.py : INFO : Detected PostgreSQL version 9.6.
> > madpack.py : INFO : *** Installing MADlib ***
> > madpack.py : INFO : MADlib tools version = 1.10.0-dev
> > (/usr/local/madlib/Versions/1.10.0-dev/bin/../madpack/madpack.py)
> > madpack.py : INFO : MADlib database version = None (host=localhost:5432,
> > db=test, schema=madlib)
> > madpack.py : INFO : Testing PL/Python environment...
> > madpack.py : INFO : > PL/Python environment OK (version: 2.7.9)
> > madpack.py : INFO : Installing MADlib into MADLIB schema...
> > madpack.py : INFO : > Creating MADLIB schema
> > madpack.py : INFO : > Creating MADLIB.MigrationHistory table
> > madpack.py : INFO : > Writing version info in MigrationHistory table
> > madpack.py : INFO : > Creating objects for modules:
> > madpack.py : INFO : > - array_ops
> > madpack.py : ERROR : Failed executing m4 on
> > /usr/local/madlib/Versions/1.10.0-dev/ports/postgres/
> modules/array_ops/array_ops.sql_in
> > madpack.py : INFO : Rolling back the installation...
> > madpack.py : INFO : Rollback finished successfully.
> > madpack.py : ERROR : MADlib installation failed.
> >
> > In Postgres log at the same time:
> >
> > 2017-01-23 08:53:37 MSK [5240]: [1-1] db=test,user=dbuser NOTICE:
> function
> > plpy_version_for_madlib() does not exist, skipping
> > 2017-01-23 08:53:37 MSK [5240]: [2-1] db=test,user= dbuser STATEMENT:
> DROP
> > FUNCTION IF EXISTS plpy_version_for_madlib();
> > 2017-01-23 08:53:37 MSK [5280]: [1-1] db=test,user= dbuser ERROR: schema
> > "madlib" does not exist at character 14
> > 2017-01-23 08:53:37 MSK [5280]: [2-1] db=test,user= dbuser STATEMENT:
> > CREATE TABLE madlib.__madlib_test_table (A INT);
> > 2017-01-23 08:53:37 MSK [5300]: [1-1] db=test,user= dbuser NOTICE: table
> > "migrationhistory" does not exist, skipping
> > 2017-01-23 08:53:37 MSK [5300]: [2-1] db=test,user= dbuser STATEMENT:
> DROP
> > TABLE IF EXISTS madlib.migrationhistory;
> > 2017-01-23 08:53:38 MSK [5331]: [1-1] db=test,user= dbuser NOTICE: drop
> > cascades to table madlib.migrationhistory
> > 2017-01-23 08:53:38 MSK [5331]: [2-1] db=test,user= dbuser STATEMENT:
> DROP
> > SCHEMA madlib CASCADE;
> >
> > BTW, it is pretty strange and inconsistent that installation doesn't
> stop on
> > ERROR, trying to create something else after that.
> >
> > Both machines are:
> > Linux db2 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19)
> x86_64
> > GNU/Linux
> >
> > Postgres versions are also the same:
> > PostgreSQL 9.6.1 on x86_64-pc-linux-gnu, compiled by gcc (Debian
> 4.9.2-10)
> > 4.9.2, 64-bit
> >
> > Any ideas why is to and how to fix?
> >
> >
>
>
>
> --
> Satoshi Nagayasu <snaga@uptime.jp <javascript:;>>
>
Re: Installation failed on Postgres, Debian
Posted by Satoshi Nagayasu <sn...@uptime.jp>.
Hi,
> madpack.py : ERROR : Failed executing m4 on /usr/local/madlib/Versions/1.10.0-dev/ports/postgres/modules/array_ops/array_ops.sql_in
I'm not familiar with the installation procedure, but it looks having
some issue around m4 which is spawned in the procedure.
Do you have the same configuration for m4 on both boxes?
Regards,
2017-01-23 14:59 GMT+09:00 Nikolay Samokhvalov <sa...@gmail.com>:
> Hi,
>
> I successfully installed MADlib (from git, HEAD) on one of Debian machines,
> it worked very well.
>
> But then I needed to install it on the different machine, with the same
> Linux version/kernel, but without libc, cmake and so on and policy that
> prohibits installing it. So I copied the "/usr/local/madlib" content from
> the first machine to the second one, then and tried to install MADlib a
> Postgres DB.
>
> And it failed:
>
> root@db2 ~ # /usr/local/madlib/bin/madpack -p postgres -c
> dbuser@localhost/test install
> madpack.py : INFO : Detected PostgreSQL version 9.6.
> madpack.py : INFO : *** Installing MADlib ***
> madpack.py : INFO : MADlib tools version = 1.10.0-dev
> (/usr/local/madlib/Versions/1.10.0-dev/bin/../madpack/madpack.py)
> madpack.py : INFO : MADlib database version = None (host=localhost:5432,
> db=test, schema=madlib)
> madpack.py : INFO : Testing PL/Python environment...
> madpack.py : INFO : > PL/Python environment OK (version: 2.7.9)
> madpack.py : INFO : Installing MADlib into MADLIB schema...
> madpack.py : INFO : > Creating MADLIB schema
> madpack.py : INFO : > Creating MADLIB.MigrationHistory table
> madpack.py : INFO : > Writing version info in MigrationHistory table
> madpack.py : INFO : > Creating objects for modules:
> madpack.py : INFO : > - array_ops
> madpack.py : ERROR : Failed executing m4 on
> /usr/local/madlib/Versions/1.10.0-dev/ports/postgres/modules/array_ops/array_ops.sql_in
> madpack.py : INFO : Rolling back the installation...
> madpack.py : INFO : Rollback finished successfully.
> madpack.py : ERROR : MADlib installation failed.
>
> In Postgres log at the same time:
>
> 2017-01-23 08:53:37 MSK [5240]: [1-1] db=test,user=dbuser NOTICE: function
> plpy_version_for_madlib() does not exist, skipping
> 2017-01-23 08:53:37 MSK [5240]: [2-1] db=test,user= dbuser STATEMENT: DROP
> FUNCTION IF EXISTS plpy_version_for_madlib();
> 2017-01-23 08:53:37 MSK [5280]: [1-1] db=test,user= dbuser ERROR: schema
> "madlib" does not exist at character 14
> 2017-01-23 08:53:37 MSK [5280]: [2-1] db=test,user= dbuser STATEMENT:
> CREATE TABLE madlib.__madlib_test_table (A INT);
> 2017-01-23 08:53:37 MSK [5300]: [1-1] db=test,user= dbuser NOTICE: table
> "migrationhistory" does not exist, skipping
> 2017-01-23 08:53:37 MSK [5300]: [2-1] db=test,user= dbuser STATEMENT: DROP
> TABLE IF EXISTS madlib.migrationhistory;
> 2017-01-23 08:53:38 MSK [5331]: [1-1] db=test,user= dbuser NOTICE: drop
> cascades to table madlib.migrationhistory
> 2017-01-23 08:53:38 MSK [5331]: [2-1] db=test,user= dbuser STATEMENT: DROP
> SCHEMA madlib CASCADE;
>
> BTW, it is pretty strange and inconsistent that installation doesn't stop on
> ERROR, trying to create something else after that.
>
> Both machines are:
> Linux db2 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64
> GNU/Linux
>
> Postgres versions are also the same:
> PostgreSQL 9.6.1 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10)
> 4.9.2, 64-bit
>
> Any ideas why is to and how to fix?
>
>
--
Satoshi Nagayasu <sn...@uptime.jp>