Re: MIT Kerberos - how are you dealing with non-renewable TGTs?

2018-10-10 Thread Loïc Chanel
Hi Maxim,

I think your answer is here : https://access.redhat.com/solutions/22956 .
But if what you're looking for is to minimize the ticket renewal operation,
then you can customize 2 parameters :
- Kerberos ticket lifetime
- Hadoop ticket renewal interval

Hope this helps.
Regards,


Loïc CHANEL
System Big Data engineer
Vision 360 Degrés (Lyon, France)


Le mar. 9 oct. 2018 à 20:02, Maxim Neaga  a écrit :

> When Kerberizing the cluster with MIT KDC, all tickets are generated as
> non-renewable by default (renewable flag is not set). Without the renewal,
> new tickets are re-generated upon expiration, but renewal is important
> because some long running jobs might actually take advantage of renewing
> the ticket so they can continue running.
>
> How are you dealing with the fact that the tickets are issued as
> non-renewable? Is anyone aware of a way to make all tickets generated as
> renewable by default? The only way I am aware of is by using "kadmin" as
> modprinc -maxrenewlife "1 week" +allow_renewable
> hive/example@example.com
> but this needs to be done for each principal/host.
>


Re: AuthenticationFilter throws ClassNotFoundException: kerberos

2018-05-24 Thread Loïc Chanel
Hi,

What is your version of Java ? Does it support Kerberos ?
Regards,


Loïc

Loïc CHANEL
System Big Data engineer
Vision 360 Degrés (Lyon, France)

2018-05-10 18:49 GMT+02:00 Lian Jiang :

> Thanks for any hint.
>
> On Tue, May 8, 2018 at 4:25 PM, Lian Jiang  wrote:
>
>> Hi,
>>
>> I am enable Spnego per https://docs.hortonworks.com/H
>> DPDocuments/Ambari-2.2.1.1/bk_Ambari_Security_Guide/content/
>> _configuring_http_authentication_for_HDFS_YARN_MapReduce2_
>> HBase_Oozie_Falcon_and_Storm.html.
>>
>> However, my name node cannot start due to exception:
>>
>> java.lang.ClassNotFoundException:  kerberos
>> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppC
>> lassLoader.java:401)
>> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppC
>> lassLoader.java:363)
>> at org.apache.hadoop.security.authentication.server.Authenticat
>> ionFilter.initializeAuthHandler(AuthenticationFil
>> ter.java:245)
>> at org.apache.hadoop.security.authentication.server.Authenticat
>> ionFilter.init(AuthenticationFilter.java:233)
>> at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.
>> java:97)
>> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCy
>> cle.java:50)
>> at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletH
>> andler.java:713)
>> at org.mortbay.jetty.servlet.Context.startContext(Context.java:
>> 140)
>> at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppCo
>> ntext.java:1282)
>> at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHand
>> ler.java:518)
>> at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext
>> .java:499)
>> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCy
>> cle.java:50)
>> at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerC
>> ollection.java:152)
>> at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(C
>> ontextHandlerCollection.java:156)
>> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCy
>> cle.java:50)
>> at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrap
>> per.java:130)
>> at org.mortbay.jetty.Server.doStart(Server.java:224)
>> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCy
>> cle.java:50)
>> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:938)
>> at org.apache.hadoop.hdfs.server.namenode.NameNodeHttpServer.st
>> art(NameNodeHttpServer.java:170)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.startHttpSer
>> ver(NameNode.java:942)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(N
>> ameNode.java:755)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameN
>> ode.java:1001)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameN
>> ode.java:985)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNo
>> de(NameNode.java:1710)
>> at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNod
>> e.java:1778)
>>
>>
>> The related core-site config is:
>>
>> "hadoop.http.authentication.simple.anonymous.allowed" : "false",
>> "hadoop.http.authentication.signature.secret.file" :
>> "/etc/security/http_secret",
>> "hadoop.http.authentication.type" : "kerberos",
>> "hadoop.http.authentication.kerberos.keytab" :
>> "/etc/security/keytabs/spnego.service.keytab",
>> "hadoop.http.authentication.kerberos.principal" : "HTTP/_
>> HOST@test_kdc.com",
>> "hadoop.http.filter.initializers" : "
>> org.apache.hadoop.security.AuthenticationFilterInitializer",
>> "hadoop.http.authentication.cookie.domain" : "
>> subnet1.hadoop.oraclevcn.com"
>>
>> Any idea? Appreciate!
>>
>
>


Re: does kerberos 1.15.1 need renew initial tickets to avoid GSSException?

2018-05-23 Thread Loïc Chanel
Hi,

As far as I remember, that error may be linked to the duration of ticket
renewability. Just check that "renew_lifetime" is the same for every
configuration linked to Kerberos (krb5.conf & krb5kdc.conf for example). I
think if they don't match, the system assume there is a mistake somewhere
and therefore tickets should not be renewable for a wrong period.
Hope this helps, and good luck to you with Kerberos.

Regards,


Loïc

Loïc CHANEL
System Big Data engineer
Vision 360 Degrés (Lyon, France)

2018-05-06 3:46 GMT+02:00 Lian Jiang :

> https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_
> files/krb5_conf.html#libdefaults does not show "renewable" action. Is
> this setting deprecated? My krb5.conf already has renew_lifetime = 7d but
> the tickets are still not renewable:
>
> [hdfs@test-namenode ~]$ klist -f
> Ticket cache: KEYRING:persistent:1012:1012
> Default principal: hdfs-spark_cluster@test_kdc.com
>
> Valid starting   Expires  Service principal
> 05/05/2018 16:36:45  05/06/2018 16:36:45  HTTP/test-namenode.subnet1.
> hadoop.oraclevcn.com@test_kdc.com
> Flags: FT
> 05/05/2018 16:36:45  05/06/2018 16:36:45  krbtgt/test_kdc.com@test_kdc.com
> Flags: FI
>
> Any idea? Thanks.
>
> On Fri, May 4, 2018 at 10:58 PM, Lian Jiang  wrote:
>
>> Hi,
>>
>> I got GSSException when using hdfs command in my kerberonized HDP2.6
>> cluster.
>>
>> java.io.IOException: Failed on local exception: java.io.IOException:
>> javax.security.sasl.SaslException: GSS initiate failed [Caused by
>> GSSException: No valid credentials provided (Mechanism level: Failed to
>> find any Kerberos tgt)]; Host Details : local host is: "
>> test-namenode.subnet1.hadoop.oraclevcn.com/10.0.1.68"; destination host
>> is: "test-namenode.subnet1.hadoop.oraclevcn.com":8020;
>>
>>  According to https://www.cloudera.com/documentation/enterprise/5-8-x/
>> topics/cm_sg_sec_troubleshooting.html, it is because the initial tickets
>> generated by kerberos >= 1.8.1 do not work for Oracle JDK 6 Update 26 and
>> earlier.
>>
>> Is this still an issue for java1.8 used in my cluster? Do I still need
>> "renewable = true" in my krb5.conf to generate renewable initial tickets
>> and then manually renew them to work with java 1.8?
>>
>> Thanks for any hint.
>>
>
>


Re: making sure you have proper disk space in install

2017-07-19 Thread Loïc Chanel
Hi Bob,

Yes, in Ambari you can specify what folder HDFS should use to write its
data. This is very basic configuration in HDFS service.
Regards,


Loïc

Loïc CHANEL
System Big Data engineer
MS&T - Worldline Analytics Platform - Worldline (Villeurbanne, France)

2017-07-19 4:05 GMT+02:00 Adaryl Wakefield :

> I’ve seen several post about the fact that HDFS isn’t taking up the whole
> disk. Is there a way in the install process to specify which mount points
> HDFS should use so you don’t have to go change it later? I have a total of
> three nodes with 1TB each. I’d prefer that HDFS take up the lion share of
> that.
>
>
>
> Adaryl "Bob" Wakefield, MBA
> Principal
> Mass Street Analytics, LLC
> 913.938.6685 <(913)%20938-6685>
>
> www.massstreet.net
>
> www.linkedin.com/in/bobwakefieldmba
> Twitter: *@BobLovesData*
>


Metrics collector not starting

2017-06-29 Thread Loïc Chanel
01190}
2017-06-29 11:17:35,361 DEBUG org.apache.zookeeper.ClientCnxn: Reading
reply sessionid:0x15cf2f282460011, packet:: clientPath:null serverPath:null
finished:false header:: 13,4  replyHeader:: 13,7301192,-101  request::
'/ams-hbase-unsecure/master,F  response::
2017-06-29 11:17:35,361 DEBUG org.apache.hadoop.hbase.zookeeper.ZKUtil:
hconnection-0x6d0b5baf-0x15cf2f282460011,
quorum=server01:2181,server02:2181,server03:2181,
baseZNode=/ams-hbase-unsecure Unable to get data of znode
/ams-hbase-unsecure/master because node does not exist (not an error)
2017-06-29 11:17:37,369 DEBUG org.apache.zookeeper.ClientCnxn: Reading
reply sessionid:0x15cf2f282460011, packet:: clientPath:null serverPath:null
finished:false header:: 14,3  replyHeader:: 14,7301192,0  request::
'/ams-hbase-unsecure,F  response::
s{68719476743,68719476743,1498721274392,1498721274392,0,37,0,0,0,9,7301190}
2017-06-29 11:17:37,370 DEBUG org.apache.zookeeper.ClientCnxn: Reading
reply sessionid:0x15cf2f282460011, packet:: clientPath:null serverPath:null
finished:false header:: 15,4  replyHeader:: 15,7301192,-101  request::
'/ams-hbase-unsecure/master,F  response::

I tried to dig into ZooKeeper, and it seems indeed that znode
/ams-hbase-unsecure/master does not exist, but as it's not an error I don't
know what is.
I checked Metrics collector and AMS HBase configuration : everything seems
correct, and the AMS HBase ZooKeeper part looks like HBase Zookeeper native
configuration.

I saw a "solution" consisting in deleting Ambari Metrics Service then
installing it again, but I'm in a production cluster and that seems very
painfull and risky for a bug like this, so I'd like to avoid that kind of
"solution".

Did someone encouter that issue ? Is it solved ?
Does anyone has an idea about where that might come from ?

Thanks for your help,


Loïc

Loïc CHANEL
System Big Data engineer
MS&T - Worldline Analytics Platform - Worldline (Villeurbanne, France)


Re: Atlas Metadata Server Install timing out

2016-11-18 Thread Loïc Chanel
Did you try restarting Ambari Metrics before installing ?

Loïc CHANEL
System Big Data engineer
MS&T - WASABI - Worldline (Villeurbanne, France)

2016-11-18 3:49 GMT+01:00 Adaryl Wakefield :

> Ok, I’m getting the message “metrics collector host or host component is
> not live”.
>
>
>
> Adaryl "Bob" Wakefield, MBA
> Principal
> Mass Street Analytics, LLC
> 913.938.6685
>
> www.massstreet.net
>
> www.linkedin.com/in/bobwakefieldmba
> Twitter: @BobLovesData
>
>
>
> *From:* Adaryl Wakefield [mailto:adaryl.wakefi...@hotmail.com]
> *Sent:* Thursday, November 17, 2016 10:25 AM
> *To:* user@ambari.apache.org
> *Subject:* Re: Atlas Metadata Server Install timing out
>
>
>
> That was half the problem. I wasn't sure where to find the logs. It
> suggest that there might be a log file named error-212.text but it's not on
> the server in the indicated location. Sorry if I could have found it over
> Google. I didn't think to look before I left my home office to head to a
> client site.
>
> B.
>
>
> --
>
> *From:* Loïc Chanel 
> *Sent:* Thursday, November 17, 2016 11:02 AM
> *To:* user@ambari.apache.org
> *Subject:* Re: Atlas Metadata Server Install timing out
>
>
>
> Can you show us some logs from Ambari ? To see what the actual error is ?
>
>
> Loïc CHANEL
> System Big Data engineer
> MS&T - WASABI - Worldline (Villeurbanne, France)
>
>
>
> 2016-11-17 16:42 GMT+01:00 Adaryl Wakefield 
> :
>
> I’m attempting to install HDP 2.5 with Ambari 2.4.1.0. When it gets to
> atlas metadata server install, it times out. I’m not sure how to
> troubleshoot this. I’m not even sure what the problem is.
>
>
>
> Adaryl "Bob" Wakefield, MBA
> Principal
> Mass Street Analytics, LLC
> 913.938.6685
>
> www.massstreet.net
>
> www.linkedin.com/in/bobwakefieldmba
> Twitter: @BobLovesData
>
>
>
>
>


Re: Atlas Metadata Server Install timing out

2016-11-17 Thread Loïc Chanel
Can you show us some logs from Ambari ? To see what the actual error is ?

Loïc CHANEL
System Big Data engineer
MS&T - WASABI - Worldline (Villeurbanne, France)

2016-11-17 16:42 GMT+01:00 Adaryl Wakefield :

> I’m attempting to install HDP 2.5 with Ambari 2.4.1.0. When it gets to
> atlas metadata server install, it times out. I’m not sure how to
> troubleshoot this. I’m not even sure what the problem is.
>
>
>
> Adaryl "Bob" Wakefield, MBA
> Principal
> Mass Street Analytics, LLC
> 913.938.6685
>
> www.massstreet.net
>
> www.linkedin.com/in/bobwakefieldmba
> Twitter: @BobLovesData
>
>
>


Re: Ambari Java Version

2016-08-31 Thread Loïc Chanel
As far as I remember (I tried this a year ago, so the behavior might differ
now) you have to install it manually on the agent nodes.
But they will be aware of the fact that they have to use JAVA 8 with the
same location than on the ambari server.

I let Ambari team confirm or not.
Regards,


Loïc

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

2016-08-31 12:11 GMT+02:00 Satyanarayana Jampa :

> Hi Loïc,
>
>
>
> I did the same, but it is installing java on ambari server node alone. I
> want java to be installed on all other ambari-agent nodes also.
>
> Should we do that manually on all the agent nodes or will ambary take care
> of it during host registration?
>
>
>
> Thanks,
>
> Satya.
>
> *From:* Loïc Chanel [mailto:loic.cha...@telecomnancy.net]
> *Sent:* 31 August 2016 15:12
> *To:* user@ambari.apache.org
> *Subject:* Re: Ambari Java Version
>
>
>
> Hi Satya,
>
>
>
> You can do ambari-server setup –j  or simply do 
> ambari-server
> setup and follow the options, as there is a prompt asking you what Java
> version you want to use.
>
>
>
> Hope this helps,
>
>
>
>
>
> Loïc
>
>
> Loïc CHANEL
> System & virtualization engineer
> TO - XaaS Ind - Worldline (Villeurbanne, France)
>
>
>
> 2016-08-31 11:13 GMT+02:00 Satyanarayana Jampa :
>
> Hi,
>
>
>
> What is the property that needs to be set, so that Ambari installs JDK1.8
> on all the cluster hosts and not java 1.7
>
>
>
> Thanks,
>
> Satya.
>
>
>
>
>


Re: Ambari Java Version

2016-08-31 Thread Loïc Chanel
Hi Satya,

You can do ambari-server setup –j  or simply do ambari-server
setup and follow the options, as there is a prompt asking you what Java
version you want to use.

Hope this helps,


Loïc

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

2016-08-31 11:13 GMT+02:00 Satyanarayana Jampa :

> Hi,
>
>
>
> What is the property that needs to be set, so that Ambari installs JDK1.8
> on all the cluster hosts and not java 1.7
>
>
>
> Thanks,
>
> Satya.
>
>
>


Re: ambari permission for users

2016-06-27 Thread Loïc Chanel
I guess this line would do :
ALL=(ALL)   NOPASSWD:/usr/sbin/ambari-server

Regards,


Loïc

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

2016-06-27 11:14 GMT+02:00 Mahmood N :

> >You can do this in the sudoers file. There you can specify which user can
> run which command.
>
> Which commands should I specify?
>
> Regards,
> Mahmood
>
>
> On Monday, June 27, 2016 12:08 PM, Loïc Chanel <
> loic.cha...@telecomnancy.net> wrote:
>
>
> Hi Mahmood,
>
> You can do this in the sudoers file. There you can specify which user can
> run which command.
> Regards,
>
>
> Loïc
>
> Loïc CHANEL
> System & virtualization engineer
> TO - XaaS Ind - Worldline (Villeurbanne, France)
>
> 2016-06-26 11:15 GMT+02:00 Mahmood N :
>
> Hello,
> How can I grant permissions to specific users to run ambari-server?
> Currently, I get
>
> mahmood@cluster:~$ ambari-server
> /usr/sbin/ambari-server: line 47: /var/lib/ambari-server/ambari-env.sh: 
> Permission denied
> Using python  /usr/bin/python
> Usage:
> 
> {start|stop|restart|setup|setup-jce|upgrade|status|upgradestack|setup-ldap|sync-ldap|set-current|setup-security|setup-sso|refresh-stack-hash|backup|restore|update-host-names|check-database|db-cleanup|enable-stack}
>   [options]
> Use   --help to get details on options available.
> Or, simply invoke ambari-server.py --help to print the options.
>
>
> Regards,
> Mahmood
>
>
>
>
>


Re: ambari permission for users

2016-06-27 Thread Loïc Chanel
Hi Mahmood,

You can do this in the sudoers file. There you can specify which user can
run which command.
Regards,


Loïc

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

2016-06-26 11:15 GMT+02:00 Mahmood N :

> Hello,
> How can I grant permissions to specific users to run ambari-server?
> Currently, I get
>
> mahmood@cluster:~$ ambari-server
> /usr/sbin/ambari-server: line 47: /var/lib/ambari-server/ambari-env.sh: 
> Permission denied
> Using python  /usr/bin/python
> Usage:
> 
> {start|stop|restart|setup|setup-jce|upgrade|status|upgradestack|setup-ldap|sync-ldap|set-current|setup-security|setup-sso|refresh-stack-hash|backup|restore|update-host-names|check-database|db-cleanup|enable-stack}
>   [options]
> Use   --help to get details on options available.
> Or, simply invoke ambari-server.py --help to print the options.
>
>
> Regards,
> Mahmood
>


Re: how to change knox topology config using configs.sh

2016-04-21 Thread Loïc Chanel
Hi Fay,

I think the topology you're looking for is the file located
in /etc/knox//0/topologies/default.xml .
It describes the Knox gateway configuration in XML format. Give it a look
eventually.

Regards,


Loïc

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

2016-04-20 19:45 GMT+02:00 Amanda Moran :

> Disregard... I quickly saw my error after sending!
>
> Sorry to not be of any help!
>
> On Wed, Apr 20, 2016 at 10:44 AM, Amanda Moran 
> wrote:
>
>> HI there-
>>
>> I use config.sh to change HBase setting and I don't need a config file to
>> do that maybe Knox is different?
>>
>> This is how I use it:
>>
>> "$AMBARI_DIR"'/configs.sh -u' "$ADMIN" '-p' "$PASSWORD"  '-port' "$PORT"
>> 'set' "$AMBARI_HOST" "$CLUSTER_NAME" 'hbase-site
>> hbase.master.distributed.log.splitting false'
>>
>> Maybe this helps :)
>>
>> Thanks!
>>
>> Amanda
>>
>>
>> On Tue, Apr 19, 2016 at 12:18 PM, Fay Wang  wrote:
>>
>>> Hi,
>>> I need to change knox topolgy config after the cluster is created.
>>> Instead of using Ambari UI, I want to call config.sh, but not sure what
>>> knox-topology-config-file should be (see below).
>>>
>>> /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p admin
>>> -port 8080 -s set localhost MyCluster 
>>> "main.ldapRealm.contextFactory.url" "$new_ldap_server:636"
>>>
>>> Any help is highly appreciated!
>>> Fay
>>>
>>>
>>
>>
>> --
>> Thanks,
>>
>> Amanda Moran
>>
>
>
>
> --
> Thanks,
>
> Amanda Moran
>


Re: [ANNOUNCE] Alexander Denissov as a new committer for Ambari

2016-04-13 Thread Loïc Chanel
Congratulations Alex !

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

2016-04-13 0:56 GMT+02:00 Newton Alex :

> Congratulations Alex!
>
> -
> Newton
>
> On Tue, Apr 12, 2016 at 3:43 PM, Bhuvnesh Chaudhary  > wrote:
>
>> Congratulations Alex :)
>>
>> Thanks,
>> Bhuvnesh Chaudhary
>> Email: bchau dh...@pivotal.io
>> Desk: +1-650-846-1696 | Mobile: +1-973-906-6976
>>
>> On Tue, Apr 12, 2016 at 2:35 PM, jun aoki  wrote:
>>
>> > Congrats Alex. Well deserved!
>> >
>> > On Tue, Apr 12, 2016 at 2:11 PM, Oleksandr Diachenko <
>> > odiache...@pivotal.io>
>> > wrote:
>> >
>> > > Hi all,
>> > >
>> > > It is my pleasure to announce that Alexander Denissov has become a
>> > > committer for Ambari.
>> > > He did significant contribution in HAWQ and PXF support and will
>> continue
>> > > doing his best.
>> > >
>> > > Congratulations, Alexander!
>> > >
>> > > Regards, Alex.
>> > >
>> >
>> >
>> >
>> > --
>> > -jun
>> >
>>
>
>


Re: [ANNOUNCE] Sandor Magyari as Ambari committer

2016-03-03 Thread Loïc Chanel
Congratulations ! :)

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

2016-03-03 17:22 GMT+01:00 Siddharth Wagle :

> Hi all,
>
>
> It's my pleasure to announce Sandor Magyari as a new Apache Ambari
> committer. He has made valuable contributions to the project and we hope he
> will continue to do so.
>
>
> Congratulations Sandor.
>
>
> Best Regards,
>
> Sid
>


Re: [ANNOUNCE] Sebastian Toader as a new Apache Ambari Committer

2016-03-03 Thread Loïc Chanel
Congrats !

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

2016-03-03 1:44 GMT+01:00 Sumit Mohanty :

> It is my pleasure to announce that Sebastian Toader has become a committer for
> Apache Ambari.
>
> Welcome Sebastian.
>
> thanks
> Sumit
>
>
>


Re: [ANNOUNCE] Mithun Mathew as a new committer for Ambari

2016-03-03 Thread Loïc Chanel
Congrats !

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

2016-03-02 23:16 GMT+01:00 jun aoki :

> He goes by Matt, just in case you don't recognize him. Congrats! You well
> deserved!
>
> On Wed, Mar 2, 2016 at 2:11 PM, Newton Alex  wrote:
>
>> Congratulations Mithun!
>>
>> -
>> Newton
>>
>> On Wed, Mar 2, 2016 at 2:09 PM, Oleksandr Diachenko <
>> odiache...@pivotal.io> wrote:
>>
>>> Hi all,
>>>
>>> It is my pleasure to announce that Mithun Mathew has become a committer
>>> for Ambari.
>>> He did significant contribution in HAWQ and PXF support and will
>>> continue doing his best.
>>>
>>> Congratulations, Mithun!
>>>
>>> Regards, Alex.
>>>
>>
>>
>
>
> --
> -jun
>


Re: [ANNOUNCE] Bhuvnesh Chaudhary as a new committer for Ambari

2016-03-03 Thread Loïc Chanel
Congrats !

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

2016-03-02 23:15 GMT+01:00 jun aoki :

> Bhuvnesh, congrats! you well deserved!!
>
> On Wed, Mar 2, 2016 at 2:09 PM, Oleksandr Diachenko  > wrote:
>
>> Hi all,
>>
>> It is my pleasure to announce that Bhuvnesh Chaudhary has become a
>> committer for Ambari.
>> He did significant contribution in HAWQ and PXF support and will continue
>> doing his best.
>>
>> Congratulations, Bhuvnesh!
>>
>> Regards, Alex.
>>
>
>
>
> --
> -jun
>


Re: incorrect version displayed after upgrade

2015-12-24 Thread Loïc Chanel
Hi Brian,

If this is just a display problem (the version shown by Ambari for the
component is not the right one, and Ambari keeps displaying that the
upgrade hasn't finished yet), I think you can solve it using the final
steps of manual upgrade documentation.

But before doing so, please really insure that all your components have
been properly upgraded by running for example hdfs version on all your
hosts.

Regards,


Loïc

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

2015-12-24 13:24 GMT+01:00 Brian Jeltema :

> I just upgraded to Ambari 2.1.2.1, and then did a rolling upgrade from HDP
> 2.2 to HDP 2.3.2.
>
> Because of internal name changes, I had to configure my cluster to use
> customized names for
> some nodes, as described in
>
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_reference_guide/content/_how_to_customize_the_name_of_a_host.html
>
> It appears that the rolling upgrade does not support this. During the
> ‘core component’ portion of the upgrade Ambari warned
> about problems upgrading the nodes with the custom names. Ambari claimed
> that the upgrade of those
> nodes failed, though by inspection of the directories and links it seems
> correct. So I chose to
> continue with the upgrade.
>
> After finishing the upgrade, All nodes and services appear to be running
> correctly, and from the logs it’s clear that
> the HDP 2.3.2 services are running. However, the Ambari ‘Stack and
> Versions’ page show HDP 2.2 as ‘Current’,
> and HDP 2.3.2 as “Upgrade: in Process’. Also, the Version column on the
> Hosts page shows the incorrect version
> on every node.
>
> Is there a fix for this?
>
> Brian


Re: [ANNOUNCE] Di Li as a new committer for Ambari

2015-12-16 Thread Loïc Chanel
Congrats !

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

2015-12-16 2:46 GMT+01:00 Eric Yang :

> Congratulation Di!
>
> regards,
> Eric
>
> On Tue, Dec 15, 2015 at 5:13 PM, Jeff Zhang  wrote:
>
>> Congratulation Di
>>
>> On Wed, Dec 16, 2015 at 4:39 AM, Yusaku Sako 
>> wrote:
>>
>>> Hi all,
>>>
>>> It is my pleasure to announce that Di Li has become a committer for Ambari.
>>>
>>> Di has been providing meaningful contributions in areas that tend to get 
>>> overlooked
>>> (usability, getting the details right, pluggability, etc.) in a full-stack 
>>> manner to improve
>>> various aspects of Ambari, including Ambari Agent, Ambari Web, and Ambari 
>>> Server.
>>>
>>> Congratulations, Di!
>>>
>>> Yusaku  
>>>
>>>
>>
>>
>> --
>> Best Regards
>>
>> Jeff Zhang
>>
>
>


Re: Ambari Manage versions

2015-12-09 Thread Loïc Chanel
Hi all,

As I didn't manage to fix this specific problem, I finally injected
manually HDP 2.3 repository data directly in Ambari's database, and it
allowed me to resume the upgrade I was trying to perform without calling
the page causing the HTTP 500 error.

Regards,


Loïc

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

2015-11-19 10:31 GMT+01:00 Loïc Chanel :

> As I don't have any input for two weeks, I ask again for your help. Can
> someone help me with my problem ?
>
> Loïc CHANEL
> System & virtualization engineer
> TO - XaaS Ind - Worldline (Villeurbanne, France)
>
> 2015-11-04 11:30 GMT+01:00 Loïc Chanel :
>
>> 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 :
>>
>>> 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 
>>> Reply-To: "user@ambari.apache.org" 
>>> Date: Tuesday, 3 November 2015 at 16:09
>>> To: "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
>

Re: Ambari Manage versions

2015-11-19 Thread Loïc Chanel
As I don't have any input for two weeks, I ask again for your help. Can
someone help me with my problem ?

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

2015-11-04 11:30 GMT+01:00 Loïc Chanel :

> 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 :
>
>> 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 
>> Reply-To: "user@ambari.apache.org" 
>> Date: Tuesday, 3 November 2015 at 16:09
>> To: "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.serv

Re: Ambari Manage versions

2015-11-04 Thread Loïc Chanel
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 :

> 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 
> Reply-To: "user@ambari.apache.org" 
> Date: Tuesday, 3 November 2015 at 16:09
> To: "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)
>

Re: Ambari Manage versions

2015-11-03 Thread Loïc Chanel
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 :

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

Re: Ambari Manage versions

2015-11-03 Thread Loïc Chanel
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 :

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


Re: Ambari Manage versions

2015-11-03 Thread Loïc Chanel
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 :

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


Ambari Manage versions

2015-10-16 Thread Loïc Chanel
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)


Re: Ambari upgrade

2015-09-01 Thread Loïc Chanel
All right. Thanks !

Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne

2015-09-01 17:39 GMT+02:00 Jeff Sposetti :

> I checked and those instructions should not be used. The link is going to
> be removed from the 2.1.0.
>
>
> Follow the guidance of first going to HDP 2.1 -> 2.2, then HDP 2.2 -> 2.3.
>
>
> ------
> *From:* Loïc Chanel 
> *Sent:* Tuesday, September 01, 2015 11:07 AM
> *To:* user@ambari.apache.org
> *Subject:* Re: Ambari upgrade
>
> As I need to upgrade a cluster from HDP 2.1 to HDP 2.3, which one should I
> trust ?
> Thanks,
>
> Loïc
>
> Loïc CHANEL
> Engineering student at TELECOM Nancy
> Trainee at Worldline - Villeurbanne
>
> 2015-09-01 16:02 GMT+02:00 Jeff Sposetti :
>
>> Thanks for pointing this out. I don’t think that section was meant to be
>> there in the 2.1.0 doc set. It’s not there in the 2.1.1 doc set.
>>
>> From: Loïc Chanel 
>> Reply-To: "user@ambari.apache.org" 
>> Date: Tuesday, September 1, 2015 at 3:41 AM
>> To: "user@ambari.apache.org" 
>> Subject: Re: Ambari upgrade
>>
>> Here it is :
>> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.0.0/bk_upgrading_Ambari/content/_upgrading_the_hdp_stack_from_21_to_23.html
>>
>>
>> Loïc CHANEL
>> Engineering student at TELECOM Nancy
>> Trainee at Worldline - Villeurbanne
>>
>> 2015-08-31 18:42 GMT+02:00 Jeff Sposetti :
>>
>>> Hi, in the Ambari 2.1.1 Upgrade Guide, where do you see the section that
>>> is dedicated to HDP 2.1 -> 2.3 upgrade?
>>>
>>>
>>> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.1.0/bk_upgrading_Ambari/content/_upgrading_hdp_stack.html
>>>
>>>
>>>  I don’t see a section for it. Can you share the link?
>>>
>>> From: Loïc Chanel 
>>> Reply-To: "user@ambari.apache.org" 
>>> Date: Monday, August 31, 2015 at 11:02 AM
>>> To: "user@ambari.apache.org" 
>>> Subject: Ambari upgrade
>>>
>>> Hi all,
>>>
>>> As I was reading the documentation for upgrading to HDP 2.3 and Ambari
>>> 2.1, I noticed this sentence :
>>> "Important : Ambari 2.1 does *not* support directly upgrading from HDP
>>> 2.0 or HDP 2.1 to HDP 2.3. In order to upgrade from HDP 2.0 or HDP 2.1, *you
>>> must first upgrade to HDP 2.2 using either Ambari 1.7 or 2.0*. Once
>>> completed, upgrade your current Ambari to Ambari 2.1. Then, leverage Ambari
>>> 2.1 to complete the upgrade from HDP 2.2 to HDP 2.3."
>>>
>>> But in this exact same documentation, there is a whole paragraph
>>> dedicated to the upgrade from HDP 2.1 to HDP 2.3.
>>>
>>> Can someone please explain what I should understand ?
>>> Because I have to upgrade a HDP 2.1 & Ambari 1.7 to HDP 2.3 & Ambari
>>> 2.1, and I would like to know the surest way to do it.
>>>
>>> Thanks in advance for your help,
>>> Regards,
>>>
>>>
>>> Loïc
>>>
>>> Loïc CHANEL
>>> Engineering student at TELECOM Nancy
>>> Trainee at Worldline - Villeurbanne
>>>
>>
>>
>


Re: Ambari upgrade

2015-09-01 Thread Loïc Chanel
As I need to upgrade a cluster from HDP 2.1 to HDP 2.3, which one should I
trust ?
Thanks,

Loïc

Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne

2015-09-01 16:02 GMT+02:00 Jeff Sposetti :

> Thanks for pointing this out. I don’t think that section was meant to be
> there in the 2.1.0 doc set. It’s not there in the 2.1.1 doc set.
>
> From: Loïc Chanel 
> Reply-To: "user@ambari.apache.org" 
> Date: Tuesday, September 1, 2015 at 3:41 AM
> To: "user@ambari.apache.org" 
> Subject: Re: Ambari upgrade
>
> Here it is :
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.0.0/bk_upgrading_Ambari/content/_upgrading_the_hdp_stack_from_21_to_23.html
>
>
> Loïc CHANEL
> Engineering student at TELECOM Nancy
> Trainee at Worldline - Villeurbanne
>
> 2015-08-31 18:42 GMT+02:00 Jeff Sposetti :
>
>> Hi, in the Ambari 2.1.1 Upgrade Guide, where do you see the section that
>> is dedicated to HDP 2.1 -> 2.3 upgrade?
>>
>>
>> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.1.0/bk_upgrading_Ambari/content/_upgrading_hdp_stack.html
>>
>>
>>  I don’t see a section for it. Can you share the link?
>>
>> From: Loïc Chanel 
>> Reply-To: "user@ambari.apache.org" 
>> Date: Monday, August 31, 2015 at 11:02 AM
>> To: "user@ambari.apache.org" 
>> Subject: Ambari upgrade
>>
>> Hi all,
>>
>> As I was reading the documentation for upgrading to HDP 2.3 and Ambari
>> 2.1, I noticed this sentence :
>> "Important : Ambari 2.1 does *not* support directly upgrading from HDP
>> 2.0 or HDP 2.1 to HDP 2.3. In order to upgrade from HDP 2.0 or HDP 2.1, *you
>> must first upgrade to HDP 2.2 using either Ambari 1.7 or 2.0*. Once
>> completed, upgrade your current Ambari to Ambari 2.1. Then, leverage Ambari
>> 2.1 to complete the upgrade from HDP 2.2 to HDP 2.3."
>>
>> But in this exact same documentation, there is a whole paragraph
>> dedicated to the upgrade from HDP 2.1 to HDP 2.3.
>>
>> Can someone please explain what I should understand ?
>> Because I have to upgrade a HDP 2.1 & Ambari 1.7 to HDP 2.3 & Ambari 2.1,
>> and I would like to know the surest way to do it.
>>
>> Thanks in advance for your help,
>> Regards,
>>
>>
>> Loïc
>>
>> Loïc CHANEL
>> Engineering student at TELECOM Nancy
>> Trainee at Worldline - Villeurbanne
>>
>
>


Re: Problem with HBase + Kerberos

2015-09-01 Thread Loïc Chanel
As someone advised me to do so, I made a kinit with the keytabs on all the
hosts where HBase component are running, and restarted HDFS and HBase, as
when restarting HBase the first time I had an error linked to hdfs keytab.

Once this is done, the errors are gone for some time, but I would bet my
paycheck that tomorrow I'll have the same errors again.
Therefore, this is most certainly related to a Kerberos expiration, but why
doesn't HBase try to renew the ticket which seems to be expired ?

As this is highly linked to Ambari deployment of Kerberos, I added the
corresponding mailing list to the discussion, hoping that someone may have
a clear idea on how to solve this problem.
Thanks in advance for your help,


Loïc

Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne

2015-09-01 10:15 GMT+02:00 Loïc Chanel :

> But how could the credentials be invalid, as they were created and managed
> only by Ambari ?
> Also I tried to connect manually with the keytab, and it works :
>
> kinit -k -t /etc/security/keytabs/hbase.service.keytab
> hbase/vm-regionser...@realm.wl
> [root@vm-regionserver /]# klist
> Ticket cache: FILE:/tmp/krb5cc_0
> Default principal: hbase/vm-regionser...@realm.wl
>
> Valid starting ExpiresService principal
> 09/01/15 10:02:18  09/02/15 10:02:18  krbtgt/realm...@realm.wl
> renew until 09/01/15 10:02:18
>
> But I still have the errors in HBase RegionServer logs :
>
> 2015-09-01 10:04:41,616 DEBUG [regionserver60020]
> security.HBaseSaslRpcClient: Creating SASL GSSAPI client. Server's Kerberos
> principal name is hbase/vm-mas...@realm.wl
> 2015-09-01 10:04:41,617 WARN  [regionserver60020] ipc.RpcClient: Couldn't
> setup connection for hbase/vm-regionser...@westeros.wl to
> hbase/vm-mas...@realm.wl
> 2015-09-01 10:04:41,618 WARN  [regionserver60020]
> regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.io.IOException: Couldn't setup
> connection for hbase/vm-regionser...@realm.wl to hbase/vm-mas...@realm.wl
> at
> org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1739)
> at
> org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1777)
> at
> org.apache.hadoop.hbase.protobuf.generated.RegionServerStatusProtos$RegionServerStatusService$BlockingStub.regionServerStartup(RegionServerStatusProtos.java:5402)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:2114)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:877)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.io.IOException: Couldn't setup connection for
> hbase/vm-regionser...@realm.wl to hbase/vm-mas...@realm.wl
>
> at
> org.apache.hadoop.hbase.ipc.RpcClient$Connection$1.run(RpcClient.java:869)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Unknown Source)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
> at
> org.apache.hadoop.hbase.ipc.RpcClient$Connection.handleSaslConnectionFailure(RpcClient.java:841)
> at
> org.apache.hadoop.hbase.ipc.RpcClient$Connection.setupIOstreams(RpcClient.java:951)
> at
> org.apache.hadoop.hbase.ipc.RpcClient$Connection.writeRequest(RpcClient.java:1094)
> at
> org.apache.hadoop.hbase.ipc.RpcClient$Connection.tracedWriteRequest(RpcClient.java:1061)
> at org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1516)
> at
> org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1724)
> ... 5 more
> Caused by: javax.security.sasl.SaslException: GSS initiate failed [Caused
> by GSSException: No valid credentials provided (Mechanism level: Failed to
> find any Kerberos tgt)]
> at
> com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(Unknown
> Source)
> at
> org.apache.hadoop.hbase.security.HBaseSaslRpcClient.saslConnect(HBaseSaslRpcClient.java:177)
> at
> org.apache.hadoop.hbase.ipc.RpcClient$Connection.setupSaslConnection(RpcClient.java:815)
> at
> org.apache.hadoop.hbase.ipc.RpcClient$Connection.access$800(RpcClient.java:349)
> at
> org.apache.hadoop.hbase.ipc.RpcClient$Connection$2.run(RpcClient.java:943)
> at
> org.apache.hadoop.hbase.ipc.RpcClient$Connection$2.run(RpcClient.java:940)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Unknown Source)
> at
> org.apache.hadoop.security.UserGroupInformation.d

Re: Ambari upgrade

2015-09-01 Thread Loïc Chanel
Here it is :
http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.0.0/bk_upgrading_Ambari/content/_upgrading_the_hdp_stack_from_21_to_23.html


Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne

2015-08-31 18:42 GMT+02:00 Jeff Sposetti :

> Hi, in the Ambari 2.1.1 Upgrade Guide, where do you see the section that
> is dedicated to HDP 2.1 -> 2.3 upgrade?
>
>
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.1.0/bk_upgrading_Ambari/content/_upgrading_hdp_stack.html
>
>
>  I don’t see a section for it. Can you share the link?
>
> From: Loïc Chanel 
> Reply-To: "user@ambari.apache.org" 
> Date: Monday, August 31, 2015 at 11:02 AM
> To: "user@ambari.apache.org" 
> Subject: Ambari upgrade
>
> Hi all,
>
> As I was reading the documentation for upgrading to HDP 2.3 and Ambari
> 2.1, I noticed this sentence :
> "Important : Ambari 2.1 does *not* support directly upgrading from HDP
> 2.0 or HDP 2.1 to HDP 2.3. In order to upgrade from HDP 2.0 or HDP 2.1, *you
> must first upgrade to HDP 2.2 using either Ambari 1.7 or 2.0*. Once
> completed, upgrade your current Ambari to Ambari 2.1. Then, leverage Ambari
> 2.1 to complete the upgrade from HDP 2.2 to HDP 2.3."
>
> But in this exact same documentation, there is a whole paragraph dedicated
> to the upgrade from HDP 2.1 to HDP 2.3.
>
> Can someone please explain what I should understand ?
> Because I have to upgrade a HDP 2.1 & Ambari 1.7 to HDP 2.3 & Ambari 2.1,
> and I would like to know the surest way to do it.
>
> Thanks in advance for your help,
> Regards,
>
>
> Loïc
>
> Loïc CHANEL
> Engineering student at TELECOM Nancy
> Trainee at Worldline - Villeurbanne
>


Ambari upgrade

2015-08-31 Thread Loïc Chanel
Hi all,

As I was reading the documentation for upgrading to HDP 2.3 and Ambari 2.1,
I noticed this sentence :
"Important : Ambari 2.1 does *not* support directly upgrading from HDP 2.0
or HDP 2.1 to HDP 2.3. In order to upgrade from HDP 2.0 or HDP 2.1, *you
must first upgrade to HDP 2.2 using either Ambari 1.7 or 2.0*. Once
completed, upgrade your current Ambari to Ambari 2.1. Then, leverage Ambari
2.1 to complete the upgrade from HDP 2.2 to HDP 2.3."

But in this exact same documentation, there is a whole paragraph dedicated
to the upgrade from HDP 2.1 to HDP 2.3.

Can someone please explain what I should understand ?
Because I have to upgrade a HDP 2.1 & Ambari 1.7 to HDP 2.3 & Ambari 2.1,
and I would like to know the surest way to do it.

Thanks in advance for your help,
Regards,


Loïc

Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne


Re: Clean un-installation via Ambari

2015-08-06 Thread Loïc Chanel
That's a VERY interesting piece of information. Do you know whether it's
documented or not ? If so, where is it ?
Thanks,


Loïc

Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne

2015-08-06 10:33 GMT+02:00 Olivier Renault :

> Sorry I forgot to mention. On each node, you will find a script which
> should clean the nodes for you.
> /usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py, it will
> generally clean up your cluster
>
> I’ve also notice
> /usr/lib/python2.6/site-packages/ambari_agent/DataCleaner.py
>
> Kind regards,
> Olivier
>
> From: Kaliyug Antagonist
> Reply-To: "user@ambari.apache.org"
> Date: Thursday, 6 August 2015 10:22
> To: "user@ambari.apache.org"
> Subject: Re: Clean un-installation via Ambari
>
> Hi Olivier,
>
> Thanks for the reply.
>
> I had two concerns :
>
>
>1. As I mentioned, I want to un install the entire cluster which means
>the 9 nodes where there are datanode directories, nn configs. and
>previously loaded data(less in size), missing blocks(!) etc. should be
>cleaned i.e I get back the 9 machines which can now be used for fresh
>installation of a cluster
>2. The reset thing will I guess only clear the metadata but the HDFS
>and other components will remain unchanged - I am not sure if this will
>solve the problems that I am facing with my existing cluster
>
> Regards !
>
> On Thu, Aug 6, 2015 at 10:12 AM, Olivier Renault  > wrote:
>
>> Log on your ambari-server bring it down and reset it
>>
>> $ ambari-server stop
>> $ ambari-server reset
>>
>> If you are using postgresql – installed and configured by ambari server,
>> you should be able to restart. If you are using MySQL or Oracle, you will
>> need to drop / re-create the database manually.
>>
>> $ ambari-server setup
>> ….
>>
>> Good luck,
>> Olivier
>>
>> From: Kaliyug Antagonist
>> Reply-To: "user@ambari.apache.org"
>> Date: Thursday, 6 August 2015 10:07
>> To: "user@ambari.apache.org"
>> Subject: Clean un-installation via Ambari
>>
>> I had installed HDP-2.2.4.2-2 using Ambari Version 2.0.0.
>>
>> There have been several issues in the cluster due to misconfiguration in
>> the datanode directories and so on. Now I get several alerts and any MR
>> that I execute fails with an error like this :
>>
>> 15/06/01 13:53:44 INFO mapreduce.Job: Job job_1431689151537_0003 running
>> in uber mode : false
>> 15/06/01 13:53:44 INFO mapreduce.Job: map 0% reduce 0%
>> 15/06/01 13:53:47 INFO mapreduce.Job: Task Id :
>> attempt_1431689151537_0003_m_00_1000, Status : FAILED
>> java.io.FileNotFoundException: File
>> /opt/dev/sdb/hadoop/yarn/local/filecache does not exist
>>
>> 15/06/01 13:53:51 INFO mapreduce.Job: Task Id :
>> attempt_1431689151537_0003_m_00_1001, Status : FAILED
>> java.io.FileNotFoundException: File
>> /opt/dev/sdd/hadoop/yarn/local/filecache does not exist
>>
>> 15/06/01 13:53:55 INFO mapreduce.Job: Task Id :
>> attempt_1431689151537_0003_m_00_1002, Status : FAILED
>> java.io.FileNotFoundException: File
>> /opt/dev/sdh/hadoop/yarn/local/filecache does not exist
>>
>>
>> I wish to clean un install the cluster and reinstall it, it is ok even if
>> Ambari needs to be uninstalled and reinstalled.
>>
>> How can I do it ?
>>
>
>


API rolling restart

2015-08-04 Thread Loïc Chanel
Hi all,

As I was trying to use the API to make rolling restart for HA cluster, I
noticed that there is no documentation about such a thing. Is it even
possible to do it ?
Because I saw some things about how to restart a simple component, but
nothing about a rolling restart, neither on Apache wiki nor on
doc.hortonworks.com

Did I miss something ?
Thanks in advance for your help,


Loïc

Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne


HA NameNode switching without reason

2015-07-23 Thread Loïc Chanel
Hi,

I am using a high-availability cluster with 3 JournalNodes and 2 NameNodes
on 2 out of 3 of these hosts, and the NameNode switched his host 3 times in
less than 24 hours without apparent reason.

This can't be a network problem, as the logs indicate clearly that the
NameNode can't send logs to the JournalNode running on the exact same host,
while calling it using its IP, and this doesn't seem to be a CPU or RAM
problem as the command sar does not return any abnormality, and Ganglia
graphics show that the JVM has way more memory than it needs to have.

Do any of you have an idea about where the problem might come from ?
Thanks in advance,


Loïc

Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne


Knox user groups

2015-06-22 Thread Loïc Chanel
Hi all,

As I am deploying Knox on my cluster, I had a few questions about user
identification.
Actually, I can't uderstand how groups are used, because eventhough the
group used by Identity assertion is actually the user name, we have to add
the user to a Unix group, or Knox will raise an error saying it "is not
allowed to impersonate" the user.

Basically, I wonder why I've got such an exception when my user does belong
to Unix groups, and why its groups cannot be used when asserting its
identity to enforce Ranger group policies for example.

Thanks in advance for your help,
Regards,


Loïc

Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne


Re: Launching Kerberized cluster via Blueprint

2015-06-04 Thread Loïc Chanel
Thanks to both of you for the confirmation of the fact that it cannot be
done at the same time.

The Ambari REST API sounds very complicated for what I want to do, so I
will simply use the UI to Kerberize my cluster.
Thanks for your quick responses and your information,


Loïc

Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne

2015-06-04 15:43 GMT+02:00 Robert Levas :

>  Hi Loïc,
>
>  Installing a cluster with Kerberos enabled via Blueprints is not
> available right now.  I think it may be possible to enable this feature,
> but some work needs to done in Ambari to handle it.  I think this is
> somewhere in the roadmap, but I am not sure where.
>
>  As a workaround, it is possible to enable Kerberos via the Ambari ReST
> API, if you were trying to avoid using the UI. Most of the steps are
> straight forward, however there is one step that can be difficult to
> perform due to the size of the data that needs to be posted.  This is the
> Kerberos Descriptor, which declares how each service in the cluster is to
> be handled when enabling Kerberos.  If you are interested in this, I can
> provide the steps; however in Ambari 2.0.0 there is a bug in the UI where,
> if Kerberos was enabled via the API there is a chance that the UI will not
> “think” Kerberos is enabled.   That issue will be fixed for Ambari 2.1.0.
>
>  Rob
>
>   From: Loïc Chanel 
> Reply-To: "user@ambari.apache.org" 
> Date: Thursday, June 4, 2015 at 7:51 AM
> To: "user@ambari.apache.org" 
> Subject: Launching Kerberized cluster via Blueprint
>
>   Hi all,
>
> As I was trying to deploy a fully secured cluster with Knox, Ranger and Ke
> beros, I had the feeling that it is not possible to instantiate a cluster
> asking it to generate the principal and keytabs linked to each of its
> services.
>
> Is there a way to deploy both of the cluster services and the 
> correspondingprincipals
> and keytabs via blueprint, just like if I deployed my cluster and I was
> asking Ambari to enable Kerberos with MIT KDC ?
>
> Thanks,
>
>
>  Loïc
>   Loïc CHANEL
> Engineering student at TELECOM Nancy
> Trainee at Worldline - Villeurbanne (France - 69)
>


Launching Kerberized cluster via Blueprint

2015-06-04 Thread Loïc Chanel
Hi all,

As I was trying to deploy a fully secured cluster with Knox, Ranger and Ke
beros, I had the feeling that it is not possible to instantiate a cluster
asking it to generate the principal and keytabs linked to each of its
services.

Is there a way to deploy both of the cluster services and the
corresponding principals
and keytabs via blueprint, just like if I deployed my cluster and I was
asking Ambari to enable Kerberos with MIT KDC ?

Thanks,


Loïc
Loïc CHANEL
Engineering student at TELECOM Nancy
Trainee at Worldline - Villeurbanne (France - 69)