Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

[AMBARI-SERVER] : failed to fully started after upgrade

Highlighted

[AMBARI-SERVER] : failed to fully started after upgrade

Explorer

hi all,

I've upgrade ambari to 2.2 to 2.4.2.0-136.

ambari-server start seems ok. but i've received HTTP 503

[root@node03 conf]# 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.
Ambari database consistency check finished
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....................
Ambari Server 'start' completed successfully.

I got a lot of messages :

24 Apr 2017 16:50:39,397  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:173 - Setting component state to UNKNOWN for component METRICS_MONITOR on node01
24 Apr 2017 16:50:39,397  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:173 - Setting component state to UNKNOWN for component ZKFC on node01
24 Apr 2017 16:50:39,398  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:173 - Setting component state to UNKNOWN for component JOURNALNODE on node01
24 Apr 2017 16:50:39,398  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:173 - Setting component state to UNKNOWN for component NAMENODE on node01
24 Apr 2017 16:50:39,399  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:173 - Setting component state to UNKNOWN for component RESOURCEMANAGER on node01
24 Apr 2017 16:50:39,400  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:173 - Setting component state to UNKNOWN for component ZOOKEEPER_SERVER on node01

24 Apr 2017 16:50:49,281  WARN [main] WebAppContext:503 - Failed startup of context o.e.j.w.WebAppContext{/views/CAPACITY-SCHEDULER/1.0.0/AUTO_CS_INSTANCE,file:/var/opt/hosting/ambari-server/resources/views/work/CAPACITY-SCHEDULER%7B1.0.0%7D/},/var/lib/ambari-server/resources/views/work/CAPACITY-SCHEDULER{1.0.0}
java.io.EOFException: Unexpected end of ZLIB input stream
        at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:240)
        at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
        at java.util.zip.ZipInputStream.read(ZipInputStream.java:194)
        at java.util.jar.JarInputStream.read(JarInputStream.java:207)
        at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:140)
        at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:118)
        at java.util.jar.JarInputStream.getNextEntry(JarInputStream.java:142)
        at java.util.jar.JarInputStream.getNextJarEntry(JarInputStream.java:179)
        at org.eclipse.jetty.webapp.JarScanner.matched(JarScanner.java:162)
        at org.eclipse.jetty.util.PatternMatcher.matchPatterns(PatternMatcher.java:100)
        at org.eclipse.jetty.util.PatternMatcher.match(PatternMatcher.java:82)
        at org.eclipse.jetty.webapp.JarScanner.scan(JarScanner.java:84)
        at org.eclipse.jetty.webapp.MetaInfConfiguration.preConfigure(MetaInfConfiguration.java:84)
        at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:457)
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:493)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
        at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
        at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
        at org.eclipse.jetty.server.Server.doStart(Server.java:282)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
        at org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:617)
        at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:927)
24 Apr 2017 16:50:49,281  WARN [main] WebAppContext:503 - Failed startup of context o.e.j.w.WebAppContext{/views/CAPACITY-SCHEDULER/1.0.0/AUTO_CS_INSTANCE,file:/var/opt/hosting/ambari-server/resources/views/work/CAPACITY-SCHEDULER%7B1.0.0%7D/},/var/lib/ambari-server/resources/views/work/CAPACITY-SCHEDULER{1.0.0}
java.io.EOFException: Unexpected end of ZLIB input stream

24 Apr 2017 16:50:55,001 ERROR [qtp-ambari-agent-57] HeartBeatHandler:200 - CurrentResponseId unknown for node0" - send register command



thanks for you helps

1 REPLY 1

Re: [AMBARI-SERVER] : failed to fully started after upgrade

@mayki wogno, this could be because the View work folder was not expanded properly. Can you try these steps,

ambari-server stop
rm -rf /var/lib/ambari-server/resources/views/work/
ambari-server start
Once Ambari Server starts, it will unzip the views again and recreate those artifacts.
Don't have an account?
Coming from Hortonworks? Activate your account here