You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ambari.apache.org by Aaron Cody <ac...@keywcorp.com> on 2013/07/12 01:59:37 UTC
need help with adding service to stack
I have a service FOO that is packaged in foo-1.0.rpm
I put my rpm up on my yum server and verified that 'yum install foo-1.0' works ok.
I want to add it to the Ambari stack. I have been trying to follow the notes at :
https://cwiki.apache.org/confluence/display/AMBARI/Adding+a+New+Service+as+part+of+the+Stack+Definition
I added a reference to my repo to ambari.repo like so:
[My-Ambari-Services]
name=My Ambari Services
baseurl=http://yum.mycompany.com/yum_repo/ambari
gpgcheck=0
enabled=1
I added the new service alongside the existing ones in the source code:
+repos
+repoinfo.xml
+services
Š MAPREDUCE et alŠ
+ FOO
+metainfo.xml
+configuration
+configuration.xml
But I need some clarification on the tags in repoinfo.xml. So far I have:
<baseurl>http://yum.mycompany.com/yum_repo/ambari</baseurl><http://yum.mycompany.com/yum_repo/ambari%3C/baseurl%3E>
<repoid>My-AmbariServices</repoid>
<reponame>??????????</reponame> <---- what is this????
I guess I'm not understanding where you tell ambari that service FOO lives in foo-1.0.rpm Š?
TIA
Re: need help with adding service to stack
Posted by Siddharth Wagle <sw...@hortonworks.com>.
Hi Aron,
Alternatively, you can install the service using the API after installation
of the cluster. The UI will start showing the new service on the Dashboard.
Final part of Step 3. Adding a New Service to an Existing
Cluster<https://cwiki.apache.org/confluence/display/AMBARI/Adding+a+New+Service+to+an+Existing+Cluster>
-Sid
On Fri, Jul 12, 2013 at 11:48 AM, Srimanth Gunturi <srimanth@hortonworks.com
> wrote:
> Hi Aaron,
> During install you should select whatever stack you added your service to.
> That stack should also be marked active=true in its metainfo.xml to show
> up in UI.
> Stacks being worked upon (ex: HDP2.0.1) will be in source, but will not
> show up in UI due to that active flag.
>
> Ambari UI might not show your service currently, as it might be hardcoded
> to show only some predefined services.
> If you observe that to be the case, please open a JIRA for Ambari UI to
> dynamically show services available in a stack.
> Hope that helps.
> Regards,
> Srimanth
>
>
>
>
>
> On Fri, Jul 12, 2013 at 11:09 AM, Aaron Cody <ac...@keywcorp.com> wrote:
>
>> - Ok so looking at the hosts, I see that the ambari.repo file isn't
>> getting copied over .. so nothing is getting installed on them.. I need to
>> understand this bootstrap process better … where is the code/script that
>> implements it?
>> Q: as I have modified ambari.repo, I'm wondering if my modified version
>> needs to be placed somewhere on my yum server?
>>
>> Just to clarify what I did so far:
>> I added something like this to ambari.repo on the master .. :
>>
>> [My-Ambari-Services]
>> name=My Ambari Services
>> baseurl=http://yum.mycompanyname.com/yum_repo/ambari
>> gpgcheck=0
>> enabled=1
>> priority=0
>>
>> …and then I put the rpm for my new service plus the rebuilt
>> ambari-server/agent rpms up on my yum server in the yum_repo/ambari folder…
>>
>> - regarding versions - I'm a bit confused .. :)
>> - In the source code I have (git clone git://git.apache.org/ambari.git),
>> I see stack versions under src/main/resources/ :
>> stacks.HDP.1.2.0
>> stacks.HDP.1.2.1
>> stacks.HDP.1.3.0 <--- I added my service in here….
>> stacks.HDP.2.0.1 ???
>> - in the Ambari docs (on the web), versions 0.9, 1.2.0, 1.2.1, 1.2.2,
>> 1.2.3 are all mentioned….
>> -in the Ambari UI, you get to choose between 1.3.0 or 1.2.1 (I
>> select 1.3.0 as that's where I added my service)
>> - in your reply you mention 1.2.4, but it's not available yet, so that's
>> no good to me ;)
>>
>> Q: what version should I be using today in order to add a service to the
>> stack?
>>
>> thanks
>> A
>>
>> From: Siddharth Wagle <sw...@hortonworks.com>
>> Reply-To: <am...@incubator.apache.org>
>> Date: Thu, 11 Jul 2013 19:38:08 -0700
>> To: <am...@incubator.apache.org>
>> Subject: Re: need help with adding service to stack
>>
>> Hi Aaron,
>>
>> 'it just sits there 'installing'
>> - Do you have the ambari-agent package in the rpm, can you verify it is
>> getting installed on the host? (rpm -qa | grep ambari-agent)
>>
>> Q: should I be adding my service to the 1.3.0 stack tree or the 1.2.x
>> stack tree?
>> Ambari will allow stack selection in the 1.2.4 release, should be
>> available by next week, you can use the call
>> http://localhost:8080/api/v1/clusters/<name> to determine the default
>> stack.
>>
>> Q: how do you map a service name to the actual rpm containing the service?
>> There is no mapping a service to rpm, a package will be installed by the
>> agent based on what rpm is available. This can be from the repo of users
>> choosing, the ambari agent will only ascertain the correct package for a
>> service is installed.
>>
>> Here is the link to design docs which should help,
>> https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Design
>>
>> -Sid
>>
>>
>> On Thu, Jul 11, 2013 at 6:52 PM, Aaron Cody <ac...@keywcorp.com> wrote:
>>
>>> Thanks Sid, ok well that didn't seem to get me any further…
>>>
>>> Q: should I be adding my service to the 1.3.0 stack tree or the 1.2.x
>>> stack tree?
>>> Q: what determines the version?
>>> Q: how do you map a service name to the actual rpm containing the
>>> service?
>>>
>>> After adding my service, I'm rebuilding the ambari rpms (server/agent)
>>> and putting them up on my yum repo .. then setting the priority of my repo
>>> to 0 so that it trumps yours … so that when I do the usual 'yum install
>>> ambari-server' it pulls down my rebuilt rpm … that all goes fine, but when
>>> I go into the web interface, define my two hosts and hit next… it just sits
>>> there 'installing' .. No progress .. No errors .. Nothing…. I checked
>>> passwordless SSH is configured correctly … it is….
>>>
>>> Any ideas?
>>>
>>
>>
>
Re: need help with adding service to stack
Posted by Srimanth Gunturi <sr...@hortonworks.com>.
Hi Aaron,
During install you should select whatever stack you added your service to.
That stack should also be marked active=true in its metainfo.xml to show up
in UI.
Stacks being worked upon (ex: HDP2.0.1) will be in source, but will not
show up in UI due to that active flag.
Ambari UI might not show your service currently, as it might be hardcoded
to show only some predefined services.
If you observe that to be the case, please open a JIRA for Ambari UI to
dynamically show services available in a stack.
Hope that helps.
Regards,
Srimanth
On Fri, Jul 12, 2013 at 11:09 AM, Aaron Cody <ac...@keywcorp.com> wrote:
> - Ok so looking at the hosts, I see that the ambari.repo file isn't
> getting copied over .. so nothing is getting installed on them.. I need to
> understand this bootstrap process better … where is the code/script that
> implements it?
> Q: as I have modified ambari.repo, I'm wondering if my modified version
> needs to be placed somewhere on my yum server?
>
> Just to clarify what I did so far:
> I added something like this to ambari.repo on the master .. :
>
> [My-Ambari-Services]
> name=My Ambari Services
> baseurl=http://yum.mycompanyname.com/yum_repo/ambari
> gpgcheck=0
> enabled=1
> priority=0
>
> …and then I put the rpm for my new service plus the rebuilt
> ambari-server/agent rpms up on my yum server in the yum_repo/ambari folder…
>
> - regarding versions - I'm a bit confused .. :)
> - In the source code I have (git clone git://git.apache.org/ambari.git),
> I see stack versions under src/main/resources/ :
> stacks.HDP.1.2.0
> stacks.HDP.1.2.1
> stacks.HDP.1.3.0 <--- I added my service in here….
> stacks.HDP.2.0.1 ???
> - in the Ambari docs (on the web), versions 0.9, 1.2.0, 1.2.1, 1.2.2,
> 1.2.3 are all mentioned….
> -in the Ambari UI, you get to choose between 1.3.0 or 1.2.1 (I select
> 1.3.0 as that's where I added my service)
> - in your reply you mention 1.2.4, but it's not available yet, so that's
> no good to me ;)
>
> Q: what version should I be using today in order to add a service to the
> stack?
>
> thanks
> A
>
> From: Siddharth Wagle <sw...@hortonworks.com>
> Reply-To: <am...@incubator.apache.org>
> Date: Thu, 11 Jul 2013 19:38:08 -0700
> To: <am...@incubator.apache.org>
> Subject: Re: need help with adding service to stack
>
> Hi Aaron,
>
> 'it just sits there 'installing'
> - Do you have the ambari-agent package in the rpm, can you verify it is
> getting installed on the host? (rpm -qa | grep ambari-agent)
>
> Q: should I be adding my service to the 1.3.0 stack tree or the 1.2.x
> stack tree?
> Ambari will allow stack selection in the 1.2.4 release, should be
> available by next week, you can use the call
> http://localhost:8080/api/v1/clusters/<name> to determine the default
> stack.
>
> Q: how do you map a service name to the actual rpm containing the service?
> There is no mapping a service to rpm, a package will be installed by the
> agent based on what rpm is available. This can be from the repo of users
> choosing, the ambari agent will only ascertain the correct package for a
> service is installed.
>
> Here is the link to design docs which should help,
> https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Design
>
> -Sid
>
>
> On Thu, Jul 11, 2013 at 6:52 PM, Aaron Cody <ac...@keywcorp.com> wrote:
>
>> Thanks Sid, ok well that didn't seem to get me any further…
>>
>> Q: should I be adding my service to the 1.3.0 stack tree or the 1.2.x
>> stack tree?
>> Q: what determines the version?
>> Q: how do you map a service name to the actual rpm containing the service?
>>
>> After adding my service, I'm rebuilding the ambari rpms (server/agent)
>> and putting them up on my yum repo .. then setting the priority of my repo
>> to 0 so that it trumps yours … so that when I do the usual 'yum install
>> ambari-server' it pulls down my rebuilt rpm … that all goes fine, but when
>> I go into the web interface, define my two hosts and hit next… it just sits
>> there 'installing' .. No progress .. No errors .. Nothing…. I checked
>> passwordless SSH is configured correctly … it is….
>>
>> Any ideas?
>>
>
>
Re: need help with adding service to stack
Posted by Aaron Cody <ac...@keywcorp.com>.
- Ok so looking at the hosts, I see that the ambari.repo file isn't getting
copied over .. so nothing is getting installed on them.. I need to
understand this bootstrap process better where is the code/script that
implements it?
Q: as I have modified ambari.repo, I'm wondering if my modified version
needs to be placed somewhere on my yum server?
Just to clarify what I did so far:
I added something like this to ambari.repo on the master .. :
[My-Ambari-Services]
name=My Ambari Services
baseurl=http://yum.mycompanyname.com/yum_repo/ambari
gpgcheck=0
enabled=1
priority=0
and then I put the rpm for my new service plus the rebuilt
ambari-server/agent rpms up on my yum server in the yum_repo/ambari folder
- regarding versions - I'm a bit confused .. :)
- In the source code I have (git clone git://git.apache.org/ambari.git), I
see stack versions under src/main/resources/ :
stacks.HDP.1.2.0
stacks.HDP.1.2.1
stacks.HDP.1.3.0 <--- I added my service in here.
stacks.HDP.2.0.1 ???
- in the Ambari docs (on the web), versions 0.9, 1.2.0, 1.2.1, 1.2.2, 1.2.3
are all mentioned.
-in the Ambari UI, you get to choose between 1.3.0 or 1.2.1 (I select
1.3.0 as that's where I added my service)
- in your reply you mention 1.2.4, but it's not available yet, so that's no
good to me ;)
Q: what version should I be using today in order to add a service to the
stack?
thanks
A
From: Siddharth Wagle <sw...@hortonworks.com>
Reply-To: <am...@incubator.apache.org>
Date: Thu, 11 Jul 2013 19:38:08 -0700
To: <am...@incubator.apache.org>
Subject: Re: need help with adding service to stack
Hi Aaron,
'it just sits there 'installing'
- Do you have the ambari-agent package in the rpm, can you verify it is
getting installed on the host? (rpm -qa | grep ambari-agent)
Q: should I be adding my service to the 1.3.0 stack tree or the 1.2.x stack
tree?
Ambari will allow stack selection in the 1.2.4 release, should be available
by next week, you can use the call
http://localhost:8080/api/v1/clusters/<name> to determine the default stack.
Q: how do you map a service name to the actual rpm containing the service?
There is no mapping a service to rpm, a package will be installed by the
agent based on what rpm is available. This can be from the repo of users
choosing, the ambari agent will only ascertain the correct package for a
service is installed.
Here is the link to design docs which should help,
https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Design
-Sid
On Thu, Jul 11, 2013 at 6:52 PM, Aaron Cody <ac...@keywcorp.com> wrote:
> Thanks Sid, ok well that didn't seem to get me any further
>
> Q: should I be adding my service to the 1.3.0 stack tree or the 1.2.x stack
> tree?
> Q: what determines the version?
> Q: how do you map a service name to the actual rpm containing the service?
>
> After adding my service, I'm rebuilding the ambari rpms (server/agent) and
> putting them up on my yum repo .. then setting the priority of my repo to 0 so
> that it trumps yours so that when I do the usual 'yum install ambari-server'
> it pulls down my rebuilt rpm that all goes fine, but when I go into the web
> interface, define my two hosts and hit next it just sits there 'installing'
> .. No progress .. No errors .. Nothing. I checked passwordless SSH is
> configured correctly it is.
>
> Any ideas?
Re: need help with adding service to stack
Posted by Siddharth Wagle <sw...@hortonworks.com>.
Hi Aaron,
'it just sits there 'installing'
- Do you have the ambari-agent package in the rpm, can you verify it is
getting installed on the host? (rpm -qa | grep ambari-agent)
Q: should I be adding my service to the 1.3.0 stack tree or the 1.2.x stack
tree?
Ambari will allow stack selection in the 1.2.4 release, should be available
by next week, you can use the call http://localhost:8080/api/v1/clusters/<name>
to determine the default stack.
Q: how do you map a service name to the actual rpm containing the service?
There is no mapping a service to rpm, a package will be installed by the
agent based on what rpm is available. This can be from the repo of users
choosing, the ambari agent will only ascertain the correct package for a
service is installed.
Here is the link to design docs which should help,
https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Design
-Sid
On Thu, Jul 11, 2013 at 6:52 PM, Aaron Cody <ac...@keywcorp.com> wrote:
> Thanks Sid, ok well that didn't seem to get me any further…
>
> Q: should I be adding my service to the 1.3.0 stack tree or the 1.2.x
> stack tree?
> Q: what determines the version?
> Q: how do you map a service name to the actual rpm containing the service?
>
> After adding my service, I'm rebuilding the ambari rpms (server/agent) and
> putting them up on my yum repo .. then setting the priority of my repo to 0
> so that it trumps yours … so that when I do the usual 'yum install
> ambari-server' it pulls down my rebuilt rpm … that all goes fine, but when
> I go into the web interface, define my two hosts and hit next… it just sits
> there 'installing' .. No progress .. No errors .. Nothing…. I checked
> passwordless SSH is configured correctly … it is….
>
> Any ideas?
>
Re: problem with the registration step
Posted by Mahadev Konar <ma...@hortonworks.com>.
Wow! Nice catch! :)
Might want to open a jira for this.
On Thu, Jul 25, 2013 at 6:43 PM, Aaron Cody <ac...@keywcorp.com> wrote:
> ok well I figured out what was going on ... not an Ambari problem.
>
> so I had grabbed the 1.2.4 source tree from apache using svn .. and
> immediately checked that into our source control - perforce.
> built the source.. built fine...
> ran it .. got the cert error.
> scratched head.
> blew everything away.
> re-synced the source from perforce ... rebuilt... built ok .. ran it ..
> cert error...
> blew everything away ...
> grabbed the source from apace using svn... rebuilt .. built ok ... ran
> fine....
> so it occurred to me that perforce might be doing something to the source
> tree to cause the problem..
> much diffing later...
> so perforce ignores empty folders... so they all get stripped out when you
> check in the code.
> Ambari has a file - ca.config where the cert stuff is configured.
> In there, new_certs_dir references an empty folder
> (/var/lib/ambari-server/keys/db/newcerts)
> In the apache source, that folder has a .gitignore file in it, so that's
> all good.
> Perforce doesn't see the .gitignore file, so thinks it is an empty folder
> and strips it out.
> At runtime, the ambari server SSL cert code looks for new_certs_dir and
> blows up if it can't find it.... leading to the runtime cert error.
>
> you might want to put a non-hidden placeholder file in that folder, so it
> doesn't get lost so easily ...
>
> :)
>
>
> On 7/24/13 9:08 AM, "Mahadev Konar" <ma...@hortonworks.com> wrote:
>
>>Aaron,
>> I would say wait for 1.2.5 to be released if this is an issue. 1.2.5
>>has a lot of fixes for ssl's and also has ability to disable ssl and
>>better debugging capabilities. I am hoping we can release that in next
>>2-3 weeks.
>>
>>thanks
>>mahadev
>>
>>On Wed, Jul 24, 2013 at 8:51 AM, Aaron Cody <ac...@keywcorp.com> wrote:
>>> oh ok just realized that the cert timestamps are in GMT and so should
>>>have
>>> been fine Š
>>> so no nearer to figuring out why registration is suddenly failing.
>>>
>>> ambari folks .. any ideas?
>>>
>>>
>>>
>>> From: Aaron Cody <ac...@keywcorp.com>
>>> Reply-To: <am...@incubator.apache.org>
>>> Date: Tuesday, July 23, 2013 11:32 PM
>>>
>>> To: "ambari-user@incubator.apache.org"
>>><am...@incubator.apache.org>
>>> Subject: Re: problem with the registration step
>>>
>>> the problem appears to be that for some reason, the SSL cert generated
>>>and
>>> signed by the ambari server as it starts up is invalid until tomorrow ..
>>>
>>> openssl x509 -noout -in /var/lib/ambari-server/keys/ca.crt dates
>>>
>>> notBefore=Jul 24 04:41:20 2013 GMT
>>> notAfter=Jul 24 04:41:20 2014 GMT
>>>
>>> which is really strange as the system date/time on my server seems to
>>>be set
>>> correctly..
>>>
>>> Anyone seen anything like this before?
>>>
>>> (the version of openssl I've got on my RH6.4 x64 box is:
>>> openssl-1.0.0-27.el6.x86_64, ambari codebase v1.2.4)
>>>
>>>
>>>
>>> From: Aaron Cody <ac...@keywcorp.com>
>>> Reply-To: <am...@incubator.apache.org>
>>> Date: Tuesday, July 23, 2013 1:39 PM
>>> To: "ambari-user@incubator.apache.org"
>>><am...@incubator.apache.org>
>>> Subject: Re: problem with the registration step
>>>
>>> looks like the agent is failing to connect back to the master because of
>>> some SSL cert problem??
>>>
>>> curl
>>>
>>>https://ac-dev-01.sensage.com:8441/agent/v1/register/ac-dev-03.sensage.co
>>>m
>>>
>>> curl: (60) Peer certificate cannot be authenticated with known CA
>>> certificates
>>> More details here: http://curl.haxx.se/docs/sslcerts.html
>>>
>>> curl performs SSL certificate verification by default, using a "bundle"
>>> of Certificate Authority (CA) public keys (CA certs). If the default
>>> bundle file isn't adequate, you can specify an alternate file
>>> using the --cacert option.
>>> If this HTTPS server uses a certificate signed by a CA represented in
>>> the bundle, the certificate verification probably failed due to a
>>> problem with the certificate (it might be expired, or the name might
>>> not match the domain name in the URL).
>>> If you'd like to turn off curl's verification of the certificate, use
>>> the -k (or --insecure) option.
>>>
>>> any ideas how to rectify this?
>>> thanks
>>>
>>>
>>> From: Aaron Cody <ac...@keywcorp.com>
>>> Reply-To: <am...@incubator.apache.org>
>>> Date: Tuesday, July 23, 2013 1:28 PM
>>> To: "ambari-user@incubator.apache.org"
>>><am...@incubator.apache.org>
>>> Subject: Re: problem with the registration step
>>>
>>> attached - thanks
>>>
>>> From: Siddharth Wagle <sw...@hortonworks.com>
>>> Reply-To: "ambari-user@incubator.apache.org"
>>> <am...@incubator.apache.org>
>>> Date: Tuesday, July 23, 2013 1:00 PM
>>> To: "ambari-user@incubator.apache.org"
>>><am...@incubator.apache.org>
>>> Subject: Re: problem with the registration step
>>>
>>> Hi Aaron,
>>>
>>> Could you correlate this message with the server logs and provide them?
>>> If you stop and start the agent you should be able to capture the error
>>>if
>>> any on the server side.
>>>
>>> To turn on debugging on the agent, edit
>>> /etc/ambari-agent/conf/ambari-agent.ini
>>> also turning on debugging on the server site might help.
>>> (/etc/ambari-server/conf/log4j.properties)
>>>
>>> -Sid
>>>
>>>
>>> On Tue, Jul 23, 2013 at 12:27 PM, Aaron Cody <ac...@keywcorp.com> wrote:
>>>>
>>>> Any ideas what might be causing this?
>>>>
>>>> I am using FQDNs and I can passwordless-SSH from master to all slave
>>>> machinesŠ
>>>> RedHat 6.4
>>>>
>>>> Registration fails:
>>>>
>>>> self.httpsconn.connect()\n File
>>>> \"/usr/lib/python2.6/site-packages/ambari_agent/security.py\", line
>>>>63, in
>>>> connect\n ca_certs=server_crt)\n File \"/usr/lib64/python2.6/ssl.py\",
>>>>line
>>>> 338, in wrap_socket\n suppress_ragged_eofs=suppress_ragged_eofs)\n File
>>>> \"/usr/lib64/python2.6/ssl.py\", line 118, in __init__\n cert_reqs,
>>>> ssl_version, ca_certs)\nSSLError: [Errno 336445442] _ssl.c:353:
>>>> error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system
>>>> lib\n', None)\n\nSTDERR\nConnection to ac-dev-04.sensage.com
>>>> closed.\nRegistering with the server...\nRegistration with the server
>>>> failed."}]
>>>
>>>
Re: problem with the registration step
Posted by Aaron Cody <ac...@keywcorp.com>.
ok well I figured out what was going on ... not an Ambari problem.
so I had grabbed the 1.2.4 source tree from apache using svn .. and
immediately checked that into our source control - perforce.
built the source.. built fine...
ran it .. got the cert error.
scratched head.
blew everything away.
re-synced the source from perforce ... rebuilt... built ok .. ran it ..
cert error...
blew everything away ...
grabbed the source from apace using svn... rebuilt .. built ok ... ran
fine....
so it occurred to me that perforce might be doing something to the source
tree to cause the problem..
much diffing later...
so perforce ignores empty folders... so they all get stripped out when you
check in the code.
Ambari has a file - ca.config where the cert stuff is configured.
In there, new_certs_dir references an empty folder
(/var/lib/ambari-server/keys/db/newcerts)
In the apache source, that folder has a .gitignore file in it, so that's
all good.
Perforce doesn't see the .gitignore file, so thinks it is an empty folder
and strips it out.
At runtime, the ambari server SSL cert code looks for new_certs_dir and
blows up if it can't find it.... leading to the runtime cert error.
you might want to put a non-hidden placeholder file in that folder, so it
doesn't get lost so easily ...
:)
On 7/24/13 9:08 AM, "Mahadev Konar" <ma...@hortonworks.com> wrote:
>Aaron,
> I would say wait for 1.2.5 to be released if this is an issue. 1.2.5
>has a lot of fixes for ssl's and also has ability to disable ssl and
>better debugging capabilities. I am hoping we can release that in next
>2-3 weeks.
>
>thanks
>mahadev
>
>On Wed, Jul 24, 2013 at 8:51 AM, Aaron Cody <ac...@keywcorp.com> wrote:
>> oh ok just realized that the cert timestamps are in GMT and so should
>>have
>> been fine
>> so no nearer to figuring out why registration is suddenly failing.
>>
>> ambari folks .. any ideas?
>>
>>
>>
>> From: Aaron Cody <ac...@keywcorp.com>
>> Reply-To: <am...@incubator.apache.org>
>> Date: Tuesday, July 23, 2013 11:32 PM
>>
>> To: "ambari-user@incubator.apache.org"
>><am...@incubator.apache.org>
>> Subject: Re: problem with the registration step
>>
>> the problem appears to be that for some reason, the SSL cert generated
>>and
>> signed by the ambari server as it starts up is invalid until tomorrow ..
>>
>> openssl x509 -noout -in /var/lib/ambari-server/keys/ca.crt dates
>>
>> notBefore=Jul 24 04:41:20 2013 GMT
>> notAfter=Jul 24 04:41:20 2014 GMT
>>
>> which is really strange as the system date/time on my server seems to
>>be set
>> correctly..
>>
>> Anyone seen anything like this before?
>>
>> (the version of openssl I've got on my RH6.4 x64 box is:
>> openssl-1.0.0-27.el6.x86_64, ambari codebase v1.2.4)
>>
>>
>>
>> From: Aaron Cody <ac...@keywcorp.com>
>> Reply-To: <am...@incubator.apache.org>
>> Date: Tuesday, July 23, 2013 1:39 PM
>> To: "ambari-user@incubator.apache.org"
>><am...@incubator.apache.org>
>> Subject: Re: problem with the registration step
>>
>> looks like the agent is failing to connect back to the master because of
>> some SSL cert problem??
>>
>> curl
>>
>>https://ac-dev-01.sensage.com:8441/agent/v1/register/ac-dev-03.sensage.co
>>m
>>
>> curl: (60) Peer certificate cannot be authenticated with known CA
>> certificates
>> More details here: http://curl.haxx.se/docs/sslcerts.html
>>
>> curl performs SSL certificate verification by default, using a "bundle"
>> of Certificate Authority (CA) public keys (CA certs). If the default
>> bundle file isn't adequate, you can specify an alternate file
>> using the --cacert option.
>> If this HTTPS server uses a certificate signed by a CA represented in
>> the bundle, the certificate verification probably failed due to a
>> problem with the certificate (it might be expired, or the name might
>> not match the domain name in the URL).
>> If you'd like to turn off curl's verification of the certificate, use
>> the -k (or --insecure) option.
>>
>> any ideas how to rectify this?
>> thanks
>>
>>
>> From: Aaron Cody <ac...@keywcorp.com>
>> Reply-To: <am...@incubator.apache.org>
>> Date: Tuesday, July 23, 2013 1:28 PM
>> To: "ambari-user@incubator.apache.org"
>><am...@incubator.apache.org>
>> Subject: Re: problem with the registration step
>>
>> attached - thanks
>>
>> From: Siddharth Wagle <sw...@hortonworks.com>
>> Reply-To: "ambari-user@incubator.apache.org"
>> <am...@incubator.apache.org>
>> Date: Tuesday, July 23, 2013 1:00 PM
>> To: "ambari-user@incubator.apache.org"
>><am...@incubator.apache.org>
>> Subject: Re: problem with the registration step
>>
>> Hi Aaron,
>>
>> Could you correlate this message with the server logs and provide them?
>> If you stop and start the agent you should be able to capture the error
>>if
>> any on the server side.
>>
>> To turn on debugging on the agent, edit
>> /etc/ambari-agent/conf/ambari-agent.ini
>> also turning on debugging on the server site might help.
>> (/etc/ambari-server/conf/log4j.properties)
>>
>> -Sid
>>
>>
>> On Tue, Jul 23, 2013 at 12:27 PM, Aaron Cody <ac...@keywcorp.com> wrote:
>>>
>>> Any ideas what might be causing this?
>>>
>>> I am using FQDNs and I can passwordless-SSH from master to all slave
>>> machines
>>> RedHat 6.4
>>>
>>> Registration fails:
>>>
>>> self.httpsconn.connect()\n File
>>> \"/usr/lib/python2.6/site-packages/ambari_agent/security.py\", line
>>>63, in
>>> connect\n ca_certs=server_crt)\n File \"/usr/lib64/python2.6/ssl.py\",
>>>line
>>> 338, in wrap_socket\n suppress_ragged_eofs=suppress_ragged_eofs)\n File
>>> \"/usr/lib64/python2.6/ssl.py\", line 118, in __init__\n cert_reqs,
>>> ssl_version, ca_certs)\nSSLError: [Errno 336445442] _ssl.c:353:
>>> error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system
>>> lib\n', None)\n\nSTDERR\nConnection to ac-dev-04.sensage.com
>>> closed.\nRegistering with the server...\nRegistration with the server
>>> failed."}]
>>
>>
Re: problem with the registration step
Posted by Mahadev Konar <ma...@hortonworks.com>.
Aaron,
I would say wait for 1.2.5 to be released if this is an issue. 1.2.5
has a lot of fixes for ssl's and also has ability to disable ssl and
better debugging capabilities. I am hoping we can release that in next
2-3 weeks.
thanks
mahadev
On Wed, Jul 24, 2013 at 8:51 AM, Aaron Cody <ac...@keywcorp.com> wrote:
> oh ok just realized that the cert timestamps are in GMT and so should have
> been fine …
> so no nearer to figuring out why registration is suddenly failing.
>
> ambari folks .. any ideas?
>
>
>
> From: Aaron Cody <ac...@keywcorp.com>
> Reply-To: <am...@incubator.apache.org>
> Date: Tuesday, July 23, 2013 11:32 PM
>
> To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
> Subject: Re: problem with the registration step
>
> the problem appears to be that for some reason, the SSL cert generated and
> signed by the ambari server as it starts up is invalid until tomorrow ..
>
> openssl x509 -noout -in /var/lib/ambari-server/keys/ca.crt –dates
>
> notBefore=Jul 24 04:41:20 2013 GMT
> notAfter=Jul 24 04:41:20 2014 GMT
>
> which is really strange as the system date/time on my server seems to be set
> correctly..
>
> Anyone seen anything like this before?
>
> (the version of openssl I've got on my RH6.4 x64 box is:
> openssl-1.0.0-27.el6.x86_64, ambari codebase v1.2.4)
>
>
>
> From: Aaron Cody <ac...@keywcorp.com>
> Reply-To: <am...@incubator.apache.org>
> Date: Tuesday, July 23, 2013 1:39 PM
> To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
> Subject: Re: problem with the registration step
>
> looks like the agent is failing to connect back to the master because of
> some SSL cert problem??
>
> curl
> https://ac-dev-01.sensage.com:8441/agent/v1/register/ac-dev-03.sensage.com
>
> curl: (60) Peer certificate cannot be authenticated with known CA
> certificates
> More details here: http://curl.haxx.se/docs/sslcerts.html
>
> curl performs SSL certificate verification by default, using a "bundle"
> of Certificate Authority (CA) public keys (CA certs). If the default
> bundle file isn't adequate, you can specify an alternate file
> using the --cacert option.
> If this HTTPS server uses a certificate signed by a CA represented in
> the bundle, the certificate verification probably failed due to a
> problem with the certificate (it might be expired, or the name might
> not match the domain name in the URL).
> If you'd like to turn off curl's verification of the certificate, use
> the -k (or --insecure) option.
>
> any ideas how to rectify this?
> thanks
>
>
> From: Aaron Cody <ac...@keywcorp.com>
> Reply-To: <am...@incubator.apache.org>
> Date: Tuesday, July 23, 2013 1:28 PM
> To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
> Subject: Re: problem with the registration step
>
> attached - thanks
>
> From: Siddharth Wagle <sw...@hortonworks.com>
> Reply-To: "ambari-user@incubator.apache.org"
> <am...@incubator.apache.org>
> Date: Tuesday, July 23, 2013 1:00 PM
> To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
> Subject: Re: problem with the registration step
>
> Hi Aaron,
>
> Could you correlate this message with the server logs and provide them?
> If you stop and start the agent you should be able to capture the error if
> any on the server side.
>
> To turn on debugging on the agent, edit
> /etc/ambari-agent/conf/ambari-agent.ini
> also turning on debugging on the server site might help.
> (/etc/ambari-server/conf/log4j.properties)
>
> -Sid
>
>
> On Tue, Jul 23, 2013 at 12:27 PM, Aaron Cody <ac...@keywcorp.com> wrote:
>>
>> Any ideas what might be causing this?
>>
>> I am using FQDNs and I can passwordless-SSH from master to all slave
>> machines…
>> RedHat 6.4
>>
>> Registration fails:
>>
>> self.httpsconn.connect()\n File
>> \"/usr/lib/python2.6/site-packages/ambari_agent/security.py\", line 63, in
>> connect\n ca_certs=server_crt)\n File \"/usr/lib64/python2.6/ssl.py\", line
>> 338, in wrap_socket\n suppress_ragged_eofs=suppress_ragged_eofs)\n File
>> \"/usr/lib64/python2.6/ssl.py\", line 118, in __init__\n cert_reqs,
>> ssl_version, ca_certs)\nSSLError: [Errno 336445442] _ssl.c:353:
>> error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system
>> lib\n', None)\n\nSTDERR\nConnection to ac-dev-04.sensage.com
>> closed.\nRegistering with the server...\nRegistration with the server
>> failed."}]
>
>
Re: problem with the registration step
Posted by Aaron Cody <ac...@keywcorp.com>.
oh ok just realized that the cert timestamps are in GMT and so should have
been fine
so no nearer to figuring out why registration is suddenly failing.
ambari folks .. any ideas?
From: Aaron Cody <ac...@keywcorp.com>
Reply-To: <am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 11:32 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
the problem appears to be that for some reason, the SSL cert generated and
signed by the ambari server as it starts up is invalid until tomorrow ..
openssl x509 -noout -in /var/lib/ambari-server/keys/ca.crt dates
notBefore=Jul 24 04:41:20 2013 GMT
notAfter=Jul 24 04:41:20 2014 GMT
which is really strange as the system date/time on my server seems to be set
correctly..
Anyone seen anything like this before?
(the version of openssl I've got on my RH6.4 x64 box is:
openssl-1.0.0-27.el6.x86_64, ambari codebase v1.2.4)
From: Aaron Cody <ac...@keywcorp.com>
Reply-To: <am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 1:39 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
looks like the agent is failing to connect back to the master because of
some SSL cert problem??
curl
https://ac-dev-01.sensage.com:8441/agent/v1/register/ac-dev-03.sensage.com
curl: (60) Peer certificate cannot be authenticated with known CA
certificates
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
any ideas how to rectify this?
thanks
From: Aaron Cody <ac...@keywcorp.com>
Reply-To: <am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 1:28 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
attached - thanks
From: Siddharth Wagle <sw...@hortonworks.com>
Reply-To: "ambari-user@incubator.apache.org"
<am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 1:00 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
Hi Aaron,
Could you correlate this message with the server logs and provide them?
If you stop and start the agent you should be able to capture the error if
any on the server side.
To turn on debugging on the agent, edit
/etc/ambari-agent/conf/ambari-agent.ini
also turning on debugging on the server site might help.
(/etc/ambari-server/conf/log4j.properties)
-Sid
On Tue, Jul 23, 2013 at 12:27 PM, Aaron Cody <ac...@keywcorp.com> wrote:
> Any ideas what might be causing this?
>
> * I am using FQDNs and I can passwordless-SSH from master to all slave
> machines
> * RedHat 6.4
> Registration fails:
>
> self.httpsconn.connect()\n File
> \"/usr/lib/python2.6/site-packages/ambari_agent/security.py\", line 63, in
> connect\n ca_certs=server_crt)\n File \"/usr/lib64/python2.6/ssl.py\", line
> 338, in wrap_socket\n suppress_ragged_eofs=suppress_ragged_eofs)\n File
> \"/usr/lib64/python2.6/ssl.py\", line 118, in __init__\n cert_reqs,
> ssl_version, ca_certs)\nSSLError: [Errno 336445442] _ssl.c:353:
> error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system lib\n',
> None)\n\nSTDERR\nConnection to ac-dev-04.sensage.com
> <http://ac-dev-04.sensage.com> closed.\nRegistering with the
> server...\nRegistration with the server failed."}]
Re: problem with the registration step
Posted by Aaron Cody <ac...@keywcorp.com>.
the problem appears to be that for some reason, the SSL cert generated and
signed by the ambari server as it starts up is invalid until tomorrow ..
openssl x509 -noout -in /var/lib/ambari-server/keys/ca.crt dates
notBefore=Jul 24 04:41:20 2013 GMT
notAfter=Jul 24 04:41:20 2014 GMT
which is really strange as the system date/time on my server seems to be set
correctly..
Anyone seen anything like this before?
(the version of openssl I've got on my RH6.4 x64 box is:
openssl-1.0.0-27.el6.x86_64, ambari codebase v1.2.4)
From: Aaron Cody <ac...@keywcorp.com>
Reply-To: <am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 1:39 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
looks like the agent is failing to connect back to the master because of
some SSL cert problem??
curl
https://ac-dev-01.sensage.com:8441/agent/v1/register/ac-dev-03.sensage.com
curl: (60) Peer certificate cannot be authenticated with known CA
certificates
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
any ideas how to rectify this?
thanks
From: Aaron Cody <ac...@keywcorp.com>
Reply-To: <am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 1:28 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
attached - thanks
From: Siddharth Wagle <sw...@hortonworks.com>
Reply-To: "ambari-user@incubator.apache.org"
<am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 1:00 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
Hi Aaron,
Could you correlate this message with the server logs and provide them?
If you stop and start the agent you should be able to capture the error if
any on the server side.
To turn on debugging on the agent, edit
/etc/ambari-agent/conf/ambari-agent.ini
also turning on debugging on the server site might help.
(/etc/ambari-server/conf/log4j.properties)
-Sid
On Tue, Jul 23, 2013 at 12:27 PM, Aaron Cody <ac...@keywcorp.com> wrote:
> Any ideas what might be causing this?
>
> * I am using FQDNs and I can passwordless-SSH from master to all slave
> machines
> * RedHat 6.4
> Registration fails:
>
> self.httpsconn.connect()\n File
> \"/usr/lib/python2.6/site-packages/ambari_agent/security.py\", line 63, in
> connect\n ca_certs=server_crt)\n File \"/usr/lib64/python2.6/ssl.py\", line
> 338, in wrap_socket\n suppress_ragged_eofs=suppress_ragged_eofs)\n File
> \"/usr/lib64/python2.6/ssl.py\", line 118, in __init__\n cert_reqs,
> ssl_version, ca_certs)\nSSLError: [Errno 336445442] _ssl.c:353:
> error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system lib\n',
> None)\n\nSTDERR\nConnection to ac-dev-04.sensage.com
> <http://ac-dev-04.sensage.com> closed.\nRegistering with the
> server...\nRegistration with the server failed."}]
Re: problem with the registration step
Posted by Aaron Cody <ac...@keywcorp.com>.
looks like the agent is failing to connect back to the master because of
some SSL cert problem??
curl
https://ac-dev-01.sensage.com:8441/agent/v1/register/ac-dev-03.sensage.com
curl: (60) Peer certificate cannot be authenticated with known CA
certificates
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
any ideas how to rectify this?
thanks
From: Aaron Cody <ac...@keywcorp.com>
Reply-To: <am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 1:28 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
attached - thanks
From: Siddharth Wagle <sw...@hortonworks.com>
Reply-To: "ambari-user@incubator.apache.org"
<am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 1:00 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
Hi Aaron,
Could you correlate this message with the server logs and provide them?
If you stop and start the agent you should be able to capture the error if
any on the server side.
To turn on debugging on the agent, edit
/etc/ambari-agent/conf/ambari-agent.ini
also turning on debugging on the server site might help.
(/etc/ambari-server/conf/log4j.properties)
-Sid
On Tue, Jul 23, 2013 at 12:27 PM, Aaron Cody <ac...@keywcorp.com> wrote:
> Any ideas what might be causing this?
>
> * I am using FQDNs and I can passwordless-SSH from master to all slave
> machines
> * RedHat 6.4
> Registration fails:
>
> self.httpsconn.connect()\n File
> \"/usr/lib/python2.6/site-packages/ambari_agent/security.py\", line 63, in
> connect\n ca_certs=server_crt)\n File \"/usr/lib64/python2.6/ssl.py\", line
> 338, in wrap_socket\n suppress_ragged_eofs=suppress_ragged_eofs)\n File
> \"/usr/lib64/python2.6/ssl.py\", line 118, in __init__\n cert_reqs,
> ssl_version, ca_certs)\nSSLError: [Errno 336445442] _ssl.c:353:
> error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system lib\n',
> None)\n\nSTDERR\nConnection to ac-dev-04.sensage.com
> <http://ac-dev-04.sensage.com> closed.\nRegistering with the
> server...\nRegistration with the server failed."}]
Re: problem with the registration step
Posted by Aaron Cody <ac...@keywcorp.com>.
attached - thanks
From: Siddharth Wagle <sw...@hortonworks.com>
Reply-To: "ambari-user@incubator.apache.org"
<am...@incubator.apache.org>
Date: Tuesday, July 23, 2013 1:00 PM
To: "ambari-user@incubator.apache.org" <am...@incubator.apache.org>
Subject: Re: problem with the registration step
Hi Aaron,
Could you correlate this message with the server logs and provide them?
If you stop and start the agent you should be able to capture the error if
any on the server side.
To turn on debugging on the agent, edit
/etc/ambari-agent/conf/ambari-agent.ini
also turning on debugging on the server site might help.
(/etc/ambari-server/conf/log4j.properties)
-Sid
On Tue, Jul 23, 2013 at 12:27 PM, Aaron Cody <ac...@keywcorp.com> wrote:
> Any ideas what might be causing this?
>
> * I am using FQDNs and I can passwordless-SSH from master to all slave
> machines
> * RedHat 6.4
> Registration fails:
>
> self.httpsconn.connect()\n File
> \"/usr/lib/python2.6/site-packages/ambari_agent/security.py\", line 63, in
> connect\n ca_certs=server_crt)\n File \"/usr/lib64/python2.6/ssl.py\", line
> 338, in wrap_socket\n suppress_ragged_eofs=suppress_ragged_eofs)\n File
> \"/usr/lib64/python2.6/ssl.py\", line 118, in __init__\n cert_reqs,
> ssl_version, ca_certs)\nSSLError: [Errno 336445442] _ssl.c:353:
> error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system lib\n',
> None)\n\nSTDERR\nConnection to ac-dev-04.sensage.com
> <http://ac-dev-04.sensage.com> closed.\nRegistering with the
> server...\nRegistration with the server failed."}]
Re: problem with the registration step
Posted by Siddharth Wagle <sw...@hortonworks.com>.
Hi Aaron,
Could you correlate this message with the server logs and provide them?
If you stop and start the agent you should be able to capture the error if
any on the server side.
To turn on debugging on the agent, edit
/etc/ambari-agent/conf/ambari-agent.ini
also turning on debugging on the server site might help.
(/etc/ambari-server/conf/log4j.properties)
-Sid
On Tue, Jul 23, 2013 at 12:27 PM, Aaron Cody <ac...@keywcorp.com> wrote:
> Any ideas what might be causing this?
>
>
> - I am using FQDNs and I can passwordless-SSH from master to all slave
> machines…
> - RedHat 6.4
>
> Registration fails:
>
> self.httpsconn.connect()\n File
> \"/usr/lib/python2.6/site-packages/ambari_agent/security.py\", line 63, in
> connect\n ca_certs=server_crt)\n File \"/usr/lib64/python2.6/ssl.py\", line
> 338, in wrap_socket\n suppress_ragged_eofs=suppress_ragged_eofs)\n File
> \"/usr/lib64/python2.6/ssl.py\", line 118, in __init__\n cert_reqs,
> ssl_version, ca_certs)\nSSLError: [Errno 336445442] _ssl.c:353:
> error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system
> lib\n', None)\n\nSTDERR\nConnection to ac-dev-04.sensage.comclosed.\nRegistering with the server...\nRegistration with the server
> failed."}]
>
problem with the registration step
Posted by Aaron Cody <ac...@keywcorp.com>.
Any ideas what might be causing this?
* I am using FQDNs and I can passwordless-SSH from master to all slave
machines
* RedHat 6.4
Registration fails:
self.httpsconn.connect()\n File
\"/usr/lib/python2.6/site-packages/ambari_agent/security.py\", line 63, in
connect\n ca_certs=server_crt)\n File \"/usr/lib64/python2.6/ssl.py\",
line 338, in wrap_socket\n suppress_ragged_eofs=suppress_ragged_eofs)\n
File \"/usr/lib64/python2.6/ssl.py\", line 118, in __init__\n cert_reqs,
ssl_version, ca_certs)\nSSLError: [Errno 336445442] _ssl.c:353:
error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system
lib\n', None)\n\nSTDERR\nConnection to ac-dev-04.sensage.com
closed.\nRegistering with the server...\nRegistration with the server
failed."}]
Re: need help with adding service to stack
Posted by Aaron Cody <ac...@keywcorp.com>.
Thanks Sid, ok well that didn't seem to get me any further
Q: should I be adding my service to the 1.3.0 stack tree or the 1.2.x stack
tree?
Q: what determines the version?
Q: how do you map a service name to the actual rpm containing the service?
After adding my service, I'm rebuilding the ambari rpms (server/agent) and
putting them up on my yum repo .. then setting the priority of my repo to 0
so that it trumps yours so that when I do the usual 'yum install
ambari-server' it pulls down my rebuilt rpm that all goes fine, but when I
go into the web interface, define my two hosts and hit next it just sits
there 'installing' .. No progress .. No errors .. Nothing. I checked
passwordless SSH is configured correctly it is.
Any ideas?
Re: need help with adding service to stack
Posted by Siddharth Wagle <sw...@hortonworks.com>.
Hi Aron,
You just need to add a new repo section to repoinfo.xml with,
[My-Ambari-Services] {= repo-id}
name=My Ambari Services {= repo-name}
-Sid
On Thu, Jul 11, 2013 at 4:59 PM, Aaron Cody <ac...@keywcorp.com> wrote:
> I have a service FOO that is packaged in foo-1.0.rpm
>
> I put my rpm up on my yum server and verified that 'yum install foo-1.0'
> works ok.
>
> I want to add it to the Ambari stack. I have been trying to follow the
> notes at :
>
> https://cwiki.apache.org/confluence/display/AMBARI/Adding+a+New+Service+as+part+of+the+Stack+Definition
>
> I added a reference to my repo to ambari.repo like so:
>
> [My-Ambari-Services]
> name=My Ambari Services
> baseurl=http://yum.mycompany.com/yum_repo/ambari
> gpgcheck=0
> enabled=1
>
> I added the new service alongside the existing ones in the source code:
> +repos
> +repoinfo.xml
> +services
> Š MAPREDUCE et alŠ
> + FOO
> +metainfo.xml
> +configuration
> +configuration.xml
>
>
> But I need some clarification on the tags in repoinfo.xml. So far I have:
>
> <baseurl>http://yum.mycompany.com/yum_repo/ambari</baseurl>
> <repoid>My-AmbariServices</repoid>
> <reponame>??????????</reponame> <---- what is this????
>
> I guess I'm not understanding where you tell ambari that service FOO
> lives in foo-1.0.rpm Š?
>
> TIA
>