Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 24 Jun 2017 00:40:00 +0000 (UTC)
From: "Vitaly Brodetskyi (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13082271.1498264799000.96432.1498264800015@Atlassian.JIRA>
In-Reply-To: <JIRA.13082271.1498264799000@Atlassian.JIRA>
References: <JIRA.13082271.1498264799000@Atlassian.JIRA> <JIRA.13082271.1498264799187@jira-lw-us.apache.org>
Subject: [jira] [Created] (AMBARI-21335) Cannot start ambari server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 24 Jun 2017 00:40:05 -0000

Vitaly Brodetskyi created AMBARI-21335:
------------------------------------------

             Summary: Cannot start ambari server
                 Key: AMBARI-21335
                 URL: https://issues.apache.org/jira/browse/AMBARI-21335
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 3.0.0
            Reporter: Vitaly Brodetskyi
            Assignee: Vitaly Brodetskyi
            Priority: Blocker
             Fix For: 3.0.0


ambari-server start fails with following error
{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...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server start.........Unable to determine server PID. Retrying...
......Unable to determine server PID. Retrying...
......Unable to determine server PID. Retrying...
ERROR: Exiting with exit code -1.
REASON: Ambari Server java process died with exitcode 1. Check /var/log/ambari-server/ambari-server.out for more information.
{Code}

logs in /var/log/ambari-server/ambari-server.out  shows
{code}
Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration <init>
INFO: Reading password from existing file
Jun 22, 2017 7:29:55 PM org.apache.ambari.server.configuration.Configuration getHostsMapFile
INFO: Hosts Mapping File null
Jun 22, 2017 7:29:55 PM org.apache.ambari.server.controller.HostsMap setupMap
INFO: Using hostsmap file null
Exception in thread "main" java.lang.NoSuchMethodError: org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String;
        at org.slf4j.impl.JDK14LoggerAdapter.info(JDK14LoggerAdapter.java:303)
        at org.apache.ambari.server.controller.ControllerModule.getPersistenceProperties(ControllerModule.java:221)
        at org.apache.ambari.server.controller.ControllerModule.buildJpaPersistModule(ControllerModule.java:416)
        at org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:343)
        at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
        at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
        at com.google.inject.spi.Elements.getElements(Elements.java:101)
        at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
        at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
        at com.google.inject.Guice.createInjector(Guice.java:95)
        at com.google.inject.Guice.createInjector(Guice.java:72)
        at com.google.inject.Guice.createInjector(Guice.java:62)
        at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1060)
~
{code}

Ambari build used - 3.0.0.0-871


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)