[
https://issues.apache.org/jira/browse/MADLIB-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978704#comment-15978704
]
Kris Avi commented on MADLIB-1068:
----------------------------------
I do not agree with it working fine.
It seems some of the functions work fine, some do not work and cause the server
to crash, at least in the not working list seems to be kmanspp and elastic_net
functions.
I tried running madpack install-check with -t linalg (that one seems to use
kmeanspp function) and it ends up segfaulting the Postgres server, just like
the elsatic_net testcase.
Same conditions here as John Grant had: Ubuntu 16.04.2, Postgres 9.6, madlib
1.10. From the functions and extensions I use only madlib is able to cause
segmentation faults and not with all the functions.
> madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2
> ----------------------------------------------------------------
>
> Key: MADLIB-1068
> URL: https://issues.apache.org/jira/browse/MADLIB-1068
> Project: Apache MADlib
> Issue Type: Question
> Components: Madpack
> Reporter: John Grant
> Attachments: elastic_net_install_check.sql_in.log
>
>
> I am installing MADlib from source and concerned about the errors *madpack
> ... install-check* reports. Here are the commands used:
> {code}
> apt install postgresql-server-dev-9.6
> apt install postgresql-plpython-9.6
> apt install cmake g++ libkrb5-dev m4 libboost-dev
> git clone https://github.com/apache/incubator-madlib
> cd incubator-madlib
> ./configure
> cd build/
> make
> make install
> src/bin/madpack -s madlib -c postgres/*@localhost/revit -p postgres install
> ...
> ...
> ...
> madpack.py : INFO : MADlib 1.10.0 installed successfully in MADLIB schema.
> {code}
> Next I run *madpack ... install-check* but it fails. Should I be concerned or
> is this possibly a bug? See attached log file:
> {code}
> root@pg203:/home/john/incubator-madlib/build# src/bin/madpack -s madlib -c
> postgres/*@localhost/revit -p postgres install-check
> madpack.py : INFO : Detected PostgreSQL version 9.6.
> TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 303
> milliseconds
> TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 862
> milliseconds
> TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 2674 milliseconds
> TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 1725
> milliseconds
> TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 2920
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 1377
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 1470
> milliseconds
> madpack.py : ERROR : Failed executing
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.tmp
> madpack.py : ERROR : Check the log at
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.log
> TEST CASE RESULT|Module:
> elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 522 milliseconds
> madpack.py : ERROR : SQL command failed:
> SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> FATAL: the database system is in recovery mode
> FATAL: the database system is in recovery mode
> Traceback (most recent call last):
> File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py",
> line 1574, in <module>
> main(sys.argv[1:])
> File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py",
> line 1505, in main
> _internal_run_query("DROP SCHEMA IF EXISTS %s CASCADE;" % (test_schema),
> True)
> File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py",
> line 182, in _internal_run_query
> return run_query(sql, show_error, con_args)
> File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py",
> line 147, in run_query
> raise Exception
> Exception
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
