atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhay (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ATLAS-303) Atlas Metadata Server Web UI is fails to start on a cluster installed with Ambari
Date Fri, 13 Nov 2015 15:25:11 GMT
Abhay created ATLAS-303:
---------------------------

             Summary: Atlas Metadata Server Web UI is fails to start on a cluster installed
with Ambari
                 Key: ATLAS-303
                 URL: https://issues.apache.org/jira/browse/ATLAS-303
             Project: Atlas
          Issue Type: Bug
    Affects Versions: 0.6-incubating
            Reporter: Abhay


there is an exception logged in /grid/0/log/atlas/application.log file as below.
2015-11-12 21:43:48,289 INFO  - [main:] ~ doAsUser: null (SecureClientUtils:93)
2015-11-12 21:43:48,713 WARN  - [main:] ~ Failed startup of context o.e.j.w.WebAppContext@63235406{/,file:/var/lib/atlas/server/webapp/atlas/,STARTING}{/var/lib/atlas/server/webapp/atlas}
(WebAppContext:514)
java.lang.RuntimeException: java.lang.IllegalStateException: No configuration group id set
for the notification type HOOK
  at org.apache.atlas.service.Services.start(Services.java:49)
  at org.apache.atlas.web.listeners.GuiceServletConfig.startServices(GuiceServletConfig.java:128)
  at org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:122)
  at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
  at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
  at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
  at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
  at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
  at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
  at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
  at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
  at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
  at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
  at org.eclipse.jetty.server.Server.start(Server.java:387)
  at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
  at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
  at org.eclipse.jetty.server.Server.doStart(Server.java:354)
  at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
  at org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:88)
  at org.apache.atlas.Atlas.main(Atlas.java:106)
Caused by: java.lang.IllegalStateException: No configuration group id set for the notification
type HOOK
  at org.apache.atlas.kafka.KafkaNotification.getConsumerProperties(KafkaNotification.java:247)
  at org.apache.atlas.kafka.KafkaNotification.createConsumers(KafkaNotification.java:157)
  at org.apache.atlas.notification.NotificationHookConsumer.start(NotificationHookConsumer.java:58)
  at org.apache.atlas.service.Services.start(Services.java:46)
  ... 19 more
2015-11-12 21:43:48,721 INFO  - [main:] ~ Started ServerConnector@23aa358e{HTTP/1.1}{0.0.0.0:21000}
(ServerConnector:266)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message