[jira] [Commented] (AMBARI-18725) Ambari Database Check failed to Complete Error

["Robert Levas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615873#comment-15615873 ] 

Robert Levas commented on AMBARI-18725:
---------------------------------------

[~mithmatt], does the issue occur on clean install or after an upgrade?

My clean install of Ambari 2.5.0, did not seem to show any issues.


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