Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 18 Jan 2017 13:55:26 +0000 (UTC)
From: "Vitaly Brodetskyi (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13035874.1484747629000.40772.1484747726441@Atlassian.JIRA>
In-Reply-To: <JIRA.13035874.1484747629000@Atlassian.JIRA>
References: <JIRA.13035874.1484747629000@Atlassian.JIRA> <JIRA.13035874.1484747629795@jira-lw-us.apache.org>
Subject: [jira] [Updated] (AMBARI-19612) ambari-server setup failed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 18 Jan 2017 13:55:38 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-19612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vitaly Brodetskyi updated AMBARI-19612:
---------------------------------------
    Attachment: AMBARI-19612.patch

> 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)