[
https://issues.apache.org/jira/browse/AMBARI-19612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828252#comment-15828252
]
Hadoop QA commented on AMBARI-19612:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12848061/AMBARI-19612.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10126//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10126//console
This message is automatically generated.
> ambari-server setup failed
> --------------------------
>
> Key: AMBARI-19612
> URL: https://issues.apache.org/jira/browse/AMBARI-19612
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19612.patch
>
>
> ambari-server setup failed
> found this issue in logs
> {noformat}
> sing python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> WARNING: Could not run /usr/sbin/sestatus: OK
> Customize user account for ambari-server daemon [y/n] (n)? Adjusting
> ambari-server permissions and ownership...
> Checking firewall status...
> Checking JDK...
> Do you want to change Oracle JDK [y/n] (n)? input not recognized, please try
> again:
> Do you want to change Oracle JDK [y/n] (n)? Completing setup...
> Configuring database...
> Enter advanced database configuration [y/n] (n)? Configuring database...
> Default properties detected. Using built-in database.
> Configuring ambari database...
> Checking PostgreSQL...
> Configuring local database...
> Configuring PostgreSQL...
> Backup for pg_hba found, reconfiguration not required
> Creating schema and user...
> ERROR: Failed to execute command:['ambari-sudo.sh', 'su', 'postgres', '-',
> '--command=psql -f
> /var/lib/ambari-server/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql -v
> username=\'"ambari"\' -v password="\'bigdata\'" -v dbname="ambari"']
> ERROR: stderr:could not change directory to "/root"
> psql: could not connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
> ERROR: stdout:
> process_pid=28571
> failed to execute queries ...retrying (1)
> Creating schema and user...
> ERROR: Failed to execute command:['ambari-sudo.sh', 'su', 'postgres', '-',
> '--command=psql -f
> /var/lib/ambari-server/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql -v
> username=\'"ambari"\' -v password="\'bigdata\'" -v dbname="ambari"']
> ERROR: stderr:could not change directory to "/root"
> psql: could not connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
> ERROR: stdout:
> process_pid=28580
> failed to execute queries ...retrying (2)
> Creating schema and user...
> ERROR: Exiting with exit code 2.
> REASON: Running database init script failed. Exiting.{noformat}
> The same result when try to do it manually
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)