[
https://issues.apache.org/jira/browse/AMBARI-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15616765#comment-15616765
]
Matt commented on AMBARI-18725:
-------------------------------
[~rlevas] Robert, I've uploaded the Ambari 2.4.x build, where I saw the error
earlier today.
https://s3-us-west-2.amazonaws.com/pivotal-public/AMBARI-branch-2.4-2.4.1.0-73.tar.gz
It was built from the following commit (HEAD of branch-2.4 about 6 hours ago):
{code}
author
Siddharth Wagle
author_date
2016-09-08 10:20:23 -0700
branch
branch-2.4
commit
b0a80fdd9df1095273e920d058e184baf87fe57a
message
AMBARI-18290. Ambari does not support HBase on HTTPS mode. (amarnathreddy via
swagle)
using version of resource found in cache
{code}
I was testing on:
CentOS release 6.8 (Final)
Using default postgres DB for intsallation
Steps to reproduce:
yum install ambari-server -y
ambari-server setup (Follow through commands below)
ambari-server start
{code}
ambari-server setup
Using python /usr/bin/python
Setup ambari-server
Checking SELinux...
SELinux status is 'disabled'
Customize user account for ambari-server daemon [y/n] (n)? Enter user account
for ambari-server daemon (root):Adjusting ambari-server permissions and
ownership...
Checking firewall status...
Checking JDK...
[1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
[2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7
[3] Custom JDK
==============================================================================
Enter choice (1):
JDK already exists, using
/var/lib/ambari-server/resources/jdk-8u77-linux-x64.tar.gz
Installing JDK to /usr/jdk64/
Successfully installed JDK to /usr/jdk64/
JCE Policy archive already exists, using
/var/lib/ambari-server/resources/jce_policy-8.zip
Installing JCE policy...
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...
Running initdb: This may take up to a minute.
Initializing database: [ OK ]
About to start PostgreSQL
Configuring local database...
Connecting to local database...done.
Configuring PostgreSQL...
Restarting PostgreSQL
Extracting system views...
ambari-admin-2.4.1.0-73.jar
.
Adjusting ambari-server permissions and ownership...
Ambari Server 'setup' completed successfully.
ambari-server start
Using python /usr/bin/python
Starting ambari-server
Ambari Server running with administrator privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Ambari database consistency check started...
No errors were found.
ERROR: Exiting with exit code 1.
REASON: Database check failed to complete. Please check
/var/log/ambari-server/ambari-server.log and
/var/log/ambari-server/ambari-server-check-database.log for more information.
{code}
> Ambari Database Check failed to Complete Error
> ----------------------------------------------
>
> Key: AMBARI-18725
> URL: https://issues.apache.org/jira/browse/AMBARI-18725
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk, 2.5.0, 2.4.2
> Reporter: Matt
> Assignee: Robert Levas
> Priority: Blocker
> Fix For: 2.5.0, 2.4.2
>
>
> Built Ambari from branch-2.4, branch-2.5 and trunk. All the builds have the
> same issue when the start command is run.
> {code}> ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> No errors were found.
> ERROR: Exiting with exit code 1.
> REASON: Database check failed to complete. Please check
> /var/log/ambari-server/ambari-server.log and
> /var/log/ambari-server/ambari-server-check-database.log for more
> information.{code}
> The database.log says {code}Error preallocating sequence numbers{code}
> Nothing suspicious on ambari-server.log.
> Log file ambari-server-check-database.log attached with this JIRA for
> reference.
> *Update*
> Reverting
> https://github.com/apache/ambari/commit/b632b33bc35afc5a01354e8916fdcdf698e49e19
> on a local copy of branch-2.4 fixed the issue on branch-2.4 build
> Reverting
> https://github.com/apache/ambari/commit/49f58e8402b543875c61f8d74a052bd6cd45a788
> on a local copy of branch-2.5 fixed the issue on branch-2.5 build
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
