ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Loïc Chanel <loic.cha...@telecomnancy.net>
Subject Re: Ambari Manage versions
Date Wed, 04 Nov 2015 10:30:49 GMT
Yes I know, and yes I do confirm that I followed these steps. Still don't
know where these Ganglia related errors come from ... Could they be related
to my initial problem ?

Loïc CHANEL
System & virtualization engineer
TO - XaaS Ind - Worldline (Villeurbanne, France)

2015-11-04 11:24 GMT+01:00 Olivier Renault <orenault@hortonworks.com>:

> As you are probably aware, ganglia has been deprecated from Ambari 2.0 and
> dropped in Ambari 2.1 in favour of Ambari Metrics server. So could you
> confirm that you’ve followed the steps required to migrate to Ambari 2.1
> when using Nagios & Ganglia.
>
> You can find the steps describe in the ambari doc
>
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_upgrading_Ambari/content/_preparing_to_upgrade_ambari.html
>
> Thanks,
> Olivier
>
>
> From: Loïc Chanel <loic.chanel@telecomnancy.net>
> Reply-To: "user@ambari.apache.org" <user@ambari.apache.org>
> Date: Tuesday, 3 November 2015 at 16:09
> To: "user@ambari.apache.org" <user@ambari.apache.org>
> Subject: Re: Ambari Manage versions
>
> 03 Nov 2015 17:06:41,052 ERROR [qtp-client-41] ClusterImpl:2016 - Config
> inconsistency exists: unknown configType=ganglia-env
> 03 Nov 2015 17:06:41,971 ERROR [pool-8-thread-9] ClusterImpl:2016 - Config
> inconsistency exists: unknown configType=ganglia-env
> 03 Nov 2015 17:06:41,971 ERROR [pool-8-thread-14] ClusterImpl:2016 -
> Config inconsistency exists: unknown configType=ganglia-env
> 03 Nov 2015 17:06:41,971 ERROR [pool-8-thread-3] ClusterImpl:2016 - Config
> inconsistency exists: unknown configType=ganglia-env
> 03 Nov 2015 17:06:41,972 ERROR [pool-8-thread-6] ClusterImpl:2016 - Config
> inconsistency exists: unknown configType=ganglia-env
> 03 Nov 2015 17:06:41,990 ERROR [pool-8-thread-9] ClusterImpl:2016 - Config
> inconsistency exists: unknown configType=ganglia-env
> 03 Nov 2015 17:06:41,991 ERROR [pool-8-thread-14] ClusterImpl:2016 -
> Config inconsistency exists: unknown configType=ganglia-env
> 03 Nov 2015 17:06:41,991 ERROR [pool-8-thread-3] ClusterImpl:2016 - Config
> inconsistency exists: unknown configType=ganglia-env
> 03 Nov 2015 17:06:48,569  WARN [qtp-client-73] ServletHandler:563 -
> /views/ADMIN_VIEW/2.1.2/INSTANCE/
> java.lang.IllegalStateException: No WebApplicationContext found: no
> ContextLoaderListener registered?
>         at
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:159)
>         at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
>         at
> org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:47)
>         at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
>         at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)
>         at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
>         at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
>         at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
>         at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
>         at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:429)
>         at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
>         at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
>         at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
>         at
> org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:209)
>         at
> org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:197)
>         at
> org.apache.ambari.server.controller.AmbariHandlerList.handle(AmbariHandlerList.java:132)
>         at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
>         at org.eclipse.jetty.server.Server.handle(Server.java:370)
>         at
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)
>         at
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971)
>         at
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033)
>         at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
>         at
> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
>         at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
>         at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:696)
>         at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53)
>         at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
>         at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
>         at java.lang.Thread.run(Thread.java:744)
>
>
> Loïc CHANEL
> System & virtualization engineer
> TO - XaaS Ind - Worldline (Villeurbanne, France)
>
> 2015-11-03 17:09 GMT+01:00 Loïc Chanel <loic.chanel@telecomnancy.net>:
>
>> I did, and here is an extract from the logs, but I can't understand where
>> the problem is located.
>>
>>
>> Loïc CHANEL
>> System & virtualization engineer
>> TO - XaaS Ind - Worldline (Villeurbanne, France)
>>
>> 2015-11-03 15:46 GMT+01:00 Artem Ervits <artemervits@gmail.com>:
>>
>>> reinstall ambari-server and agents, then run ambari-server upgrade, then
>>> start ambari-server and agents and when you browse to the url, hit control
>>> shift R. Check in /var/log/ambari-server/ambari-server.log for any errors.
>>>
>>> On Tue, Nov 3, 2015 at 8:27 AM, Loïc Chanel <
>>> loic.chanel@telecomnancy.net> wrote:
>>>
>>>> Hi,
>>>>
>>>> As it's been a month since I sent this mail, I repost it because I'm
>>>> still stuck.
>>>> Could someone help me locating the origin of the bug ? And/Or how to
>>>> solve it.
>>>>
>>>> Thanks in advance for your help,
>>>>
>>>>
>>>> Loïc
>>>>
>>>> Loïc CHANEL
>>>> System & virtualization engineer
>>>> TO - XaaS Ind - Worldline (Villeurbanne, France)
>>>>
>>>> 2015-10-16 15:22 GMT+02:00 Loïc Chanel <loic.chanel@telecomnancy.net>:
>>>>
>>>>> Hi all,
>>>>>
>>>>> As I just upgraded my Ambari cluster to Ambari 2.1.2, I was trying to
>>>>> update my cluster to HDP 2.3 when I encountered a major error.
>>>>> Indeed, when I go to Stack and Versions and I click on Manage Version
>>>>> button, I get an HTTP 500 error, with the following stack :
>>>>>
>>>>> HTTP ERROR 500
>>>>>
>>>>> Problem accessing /views/ADMIN_VIEW/2.1.2/INSTANCE/. Reason:
>>>>>
>>>>>     Server Error
>>>>>
>>>>> Caused by:
>>>>>
>>>>> java.lang.IllegalStateException: No WebApplicationContext found: no ContextLoaderListener
registered?
>>>>> 	at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:159)
>>>>> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
>>>>> 	at org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:47)
>>>>> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
>>>>> 	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)
>>>>> 	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
>>>>> 	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
>>>>> 	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
>>>>> 	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
>>>>> 	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:429)
>>>>> 	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
>>>>> 	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
>>>>> 	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
>>>>> 	at org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:209)
>>>>> 	at org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:197)
>>>>> 	at org.apache.ambari.server.controller.AmbariHandlerList.handle(AmbariHandlerList.java:132)
>>>>> 	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
>>>>> 	at org.eclipse.jetty.server.Server.handle(Server.java:370)
>>>>> 	at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)
>>>>> 	at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971)
>>>>> 	at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033)
>>>>> 	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
>>>>> 	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
>>>>> 	at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
>>>>> 	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:696)
>>>>> 	at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53)
>>>>> 	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
>>>>> 	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
>>>>> 	at java.lang.Thread.run(Thread.java:744)
>>>>>
>>>>>
>>>>> What's even more surprising is I can find in the server's architecture
>>>>> the corresponding page, which have been generated by Ambari, but it seems
>>>>> there is a Jetty error preventing me to access this page.
>>>>> Do anyone as an idea about how to solve this ?
>>>>>
>>>>> Thanks in advance for your help,
>>>>> Regards,
>>>>>
>>>>>
>>>>> Loïc
>>>>>
>>>>> Loïc CHANEL
>>>>> System & virtualization engineer
>>>>> TO - XaaS Ind - Worldline (Villeurbanne, France)
>>>>>
>>>>
>>>>
>>>
>>
>

Mime
View raw message