[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: oo-install for Origin version 3



Hi All

 

Any pointers on the highlighted exception ?I am using oo-install for deploying openShift origin in Fed 19

Looks like a mongodb issue-

 

I tried login in the mongodb from broker :

 

mongo --username openshift --password mongopass broker.cloudshift.com/openshift_broker

MongoDB shell version: 2.4.6 connecting to: broker.cloudshift.com/openshift_broker Fri Jan 17 21:27:29.783 Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" } at src/mongo/shell/db.js:228 exception: login failed

 

My broker.conf looks like

 

#Broker datastore configuration

MONGO_REPLICA_SETS=false

# Replica set example: "<host-1>:<port-1> <host-2>:<port-2> ..."

MONGO_HOST_PORT="broker.cloudshift.com:27017"

MONGO_USER="openshift"

MONGO_PASSWORD="mongopass"

MONGO_DB="openshift_broker"

MONGO_TEST_DB="openshift_broker_test"

MONGO_SSL="false"

 

Not able to proceed..Please help.

 

Also need to understand ,If I see an error screen like this cid:image001.png@01CF13F1.1074CD50

Which /where are the error logs I should look at.

 

 

Thanks

Shabna

 

From: Madathilthattantav, S.
Sent: Saturday, January 18, 2014 2:01 AM
To: 'The Dude'; 'hripps redhat com'; 'kraman redhat com'
Cc: 'users lists openshift redhat com'; 'dev lists openshift redhat com'
Subject: RE: oo-install for Origin version 3

 

Hi All

 

I am trying this in Fedora19.Since I got it up and running in RHEL –ec2, I was expecting it to work  in Fedora without any technical glitches

 

But I am hit with an issue ->

 

What works  :

1.       oo-accept-node is PASS

2.       mco ping on Broker -PASS

               [root ip-10-180-222-97 fedora]# mco ping

               node1.cloudshift.com                     time=171.12 ms

 

3.       OpenShift web console:Able to login and welcome screen appears

 

What breaks :

1.       oo-accept-broker –v FAILS with an error

INFO: Datastore: mongo db service is remote

INFO: checking mongo db login access

exception: login failed

FAIL: error logging into mongo db:      from /var/www/openshift/broker/config/environment.rb:5:in `<top (required)>':   from /usr/share/gems/gems/railties-3.2.13/lib/rails/railtie/configurable.rb:30:in `method_missing'/from --username /usr/share/gems/gems/railties-3.2.13/lib/rails/application.rb:136:in, exit code: 1

INFO: checking services

INFO: checking cloud user authentication

INFO: auth plugin = from -:2:in `<main>'

NOTICE: unknown auth class: from -:2:in `<main>'

INFO: checking dynamic dns plugin

NOTICE: unknown dns class: from -:2:in `<main>'

INFO: checking messaging configuration

NOTICE: unknown messaging class: from -:2:in `<main>'

1 ERRORS

oo-diagnostics –vv – FAIL -1 error message

FAIL: rescue in load_broker_rails_env

        Broker application failed to load. This is often a gem dependency problem.

        Updating rubygem RPMs and restarting openshift-broker

        to regenerate the broker Gemfile.lock may fix the problem.

        The actual error encountered was:

        #<Moped::Errors::AuthenticationFailure: The operation: #<Moped::Protocol::Commands::Authenticate

  @length=163

  @request_id=3

  @response_to=0

  @op_code=2004

  @flags=[]

  @full_collection_name="openshift_broker.$cmd"

  @skip=0

  @limit=-1

  @selector={:authenticate=>1, :user=>"openshift", :nonce=>"ac4ce7b622ba6d9d", :key=>"811f9ff0fa4b00a7752098ee3a7b718a"}

  @fields=nil>

failed with error 18: "auth fails"

 

See https://github.com/mongodb/mongo/blob/master/docs/errors.md

for details about this error.>

        ***

        THIS PROBLEM NEEDS TO BE RESOLVED FOR THE BROKER TO WORK.

        DISABLING BROKER TESTS.

        ***

When I click on create first application : following screen comes up ,instead of carrdige list

 

Any pointers ??

 

Thanks

Shabna

 

-----Original Message-----
From: Madathilthattantav, S.
Sent: Friday, January 17, 2014 1:07 PM
To: 'The Dude'; hripps redhat com
Cc: users lists openshift redhat com; kraman redhat com; dev lists openshift redhat com
Subject: RE: oo-install for Origin version 3

 

Hi

 

Here is the good news.I was able to get the installation working in aws using oo-install,Thanks a lot for the support.

I will send details on what all manual steps I had to do ,apart from the below steps.A special thanks to The Dude ,great pointers.

 

 

Yet to deploy the applications-- lot of cartridges missing ,specially jboss and tomcat and hitting exception while trying to install the same.

Digging into this,will keep you posted.

 

Thanks

Shabna

 

-----Original Message-----

From: The Dude [mailto:michael mcconachie hotmail com]

Sent: Thursday, January 16, 2014 9:44 PM

To: Madathilthattantav, S.; hripps redhat com

Cc: users lists openshift redhat com; kraman redhat com; dev lists openshift redhat com

Subject: RE: oo-install for Origin version 3

 

Howdy Shabna --

 

I have been heads down at work, but wanted to validate having to restart httpd after the build/reboot.  In fact, I'm putting together a checklist of stuff that I do (and will share it when I'm done). The intent will be to be able to use the installer, reboot, and then pretty much copy/paste to get the rest of it working. Sounds like you sorted much of it already. 

 

Here's a shortlist of what I do to get any number of nodes working after a build and reboot.

 

 

Node stuff:

-------------------

service cgred restart; chkconfig cgred on service cgconfig restart; chkconfig cgconfig on echo "kernel.sem = 250  32000 32  4096">> /etc/sysctl.conf; sysctl -p service mcollective restart oo-accept-node

 

Broker stuff:

------------------

host=$(hostname -f)

chkconfig httpd on

sed -i '/VirtualHost/,/VirtualHost/ d' /etc/httpd/conf.d/ssl.conf sed -i 's/localhost/${host}/' /etc/httpd/conf.d/000002_openshift_origin_broker_servername.conf

yum -y install mlocate

service openshift-broker restart

oo-diagnostics -vv

 

If you don't wanna use NetworkManager:

--------------------------------------

grep -l NM_CONTROLLED /etc/sysconfig/network-scripts/ifcfg-* | xargs perl -p -i -e '/NM_CONTROLLED/ && s/yes/no/i'

 

 

Thanks,

 

 

Michael J. McConachie

 

 

 

________________________________

> From: s madathilthattantav accenture com

> To: hripps redhat com

> Subject: RE: oo-install for Origin version 3

> Date: Thu, 16 Jan 2014 06:29:10 +0000

> CC: users lists openshift redhat com; kraman redhat com;

> dev lists openshift redhat com

>  

> Hi Harrison

> Great news..Thanks a lot.

> I re tried the deployment with the new changes—Lot of things got

> resolved. here are some of issue I am facing

> On Broker -

> 1.mco ping not working – this is strange and something really amiss.

> [root ip-10-91-136-141 ec2-user]# mco ping

> bash: mco: command not found

> 2.I had to manually start service httpd restart

> 3.oo-accept-broker is giving one failure which is a little strange

> INFO: Datastore Host:  MOPED: Could not resolve IP address for

> broker.cloudshift.com:27017

> INFO: Datastore Port:  MOPED: Could not resolve IP address for

> broker.cloudshift.com:27017

> INFO: Datastore User:  MOPED: Could not resolve IP address for

> broker.cloudshift.com:27017

> INFO: Datastore SSL:  MOPED: Could not resolve IP address for

> broker.cloudshift.com:27017

> INFO: Datastore Password has been set to non-default

> INFO: Datastore DB Name:  MOPED: Could not resolve IP address for

> broker.cloudshift.com:27017

> INFO: Datastore: mongo db service is remote

> INFO: checking mongo db login access

> exception: connect failed

> FAIL: error logging into mongo db:  MOPED: Could not resolve IP

> address for broker.cloudshift.com:27017: MOPED: Could not resolve IP

> address for broker.cloudshift.com:27017/MOPED: --username Could, exit

> code: 1

> INFO: checking services

> INFO: checking cloud user authentication

> INFO: auth plugin = MOPED: Could not resolve IP address for

> broker.cloudshift.com:27017

> NOTICE: unknown auth class: MOPED: Could not resolve IP address for

> broker.cloudshift.com:27017

> INFO: checking dynamic dns plugin

> NOTICE: unknown dns class: MOPED: Could not resolve IP address for

> broker.cloudshift.com:27017

> INFO: checking messaging configuration

> NOTICE: unknown messaging class: MOPED: Could not resolve IP address

> for broker.cloudshift.com:27017

> 1 ERRORS

> On Node : I manually changed the BROKER_HOST to elastic ip in

> /etc/openshift/node and following are the error I get wen I run

> oo-accept-node –v

> But these errors are not that showstoppers and from what I understand

> can be ignored

> FAIL: kernel.sem semaphores too low: 128 < 512

> INFO: checking cgroups configuration

> INFO: checking cgroups processes

> INFO: find district uuid: NONE

> INFO: determining node uid range: 1000 to 6500

> INFO: checking presence of tc qdisc

> INFO: checking for cgroup filter

> INFO: checking presence of tc classes

> INFO: checking filesystem quotas

> INFO: checking quota db file selinux label

> INFO: checking 0 user accounts

> INFO: checking application dirs

> INFO: checking system httpd configs

> INFO: checking cartridge repository

> FAIL: no manifest in the cart repo matches

> /usr/libexec/openshift/cartridges/php/metadata/manifest.yml

> FAIL: no manifest in the cart repo matches

> /usr/libexec/openshift/cartridges/jenkins-client/metadata/manifest.yml

> FAIL: no manifest in the cart repo matches

> /usr/libexec/openshift/cartridges/perl/metadata/manifest.yml

> 4 ERRORS

> From the browser,I am able to login,but unable to create application-

> An error occurred screen appears.

> [https://bay172.afx.ms/att/GetInline.aspx?messageid=93fc9e06-7e78-11e3

> -a701-00215ad9b8c2&attindex=0&cp=-1&attdepth=0&imgsrc=cid%3aimage001.p

> ng%4001CF12B2.375C53B0&cid=b78b6bdcd5dd4d99&hm__login=michael.mcconach

> ie&hm__domain=hotmail.com&ip=10.111.80.8&d=d4205&mf=32&hm__ts=Thu%2c%2

> 016%20Jan%202014%2016%3a02%3a45%20GMT&st=michael.mcconachie&hm__ha=01_

> 7b476f6627dfd34f26a57bbfeb709ce30750804a19243f798df848307dbcf6c7&onere

> dir=1]

> -----Original Message-----

> From: N. Harrison Ripps [mailto:hripps redhat com]

> Sent: Wednesday, January 15, 2014 10:59 PM

> To: Madathilthattantav, S.

> Cc: dev lists openshift redhat com; users lists openshift redhat com;

> Krishna Raman

> Subject: Re: oo-install for Origin version 3

> Hey Shabna--

> On Jan 15, 2014, at 11:42 ,

> <s madathilthattantav accenture com<mailto:s madathilthattantav accent

> ure.com>>

> <s madathilthattantav accenture com<mailto:s madathilthattantav accent

> ure.com>>

> wrote:

> > Hi Harrison

> >

> > Thanks a lot.Let me know if there would be any changes for this-

> > since

> > the timelines would have an impact on the current task I am working on.

> The optional named_ip_address override is in place now. If you rerun

> oo-install from install.openshift.com, you will see that if you opt to

> edit your current broker config, you will have the opportunity to set

> a value for the BIND DNS IP addr that is distinct from the broker's

> primary IP addr.

> I am still following up re: setting broker & activemq host info for the node.

> >

> > Shabna

> >

> > -----Original Message-----

> > From: N. Harrison Ripps [mailto:hripps redhat com]

> > Sent: Wednesday, January 15, 2014 7:15 PM

> > To: Madathilthattantav, S.

> > Cc: 

> dev lists openshift redhat com<mailto:dev lists openshift redhat com>;

> users lists openshift redhat com<mailto:users lists openshift redhat c

> om>;

> > Krishna Raman

> > Subject: Re: oo-install for Origin version 3

> > Importance: High

> >

> > Hey Shabna--

> >

> > On Jan 15, 2014, at 4:11 ,

> s madathilthattantav accenture com<mailto:s madathilthattantav accentu

> re.com>

> wrote:

> >

> >> Hi Harrison

> >>

> >> I am facing some challenges  with the oo-install uitility while

> >> trying to install OpenShiftOrigin version 3 in AWS

> >>

> >> Issue 1 :Broker Configuration

> >>

> >> In cased of of aws , broker_ip_addr  √†will be the elastic ip of the

> >> instance and named_ip_adrr  -√† should be the eth0 IP address of the

> >> broker host

> >>

> >> But the script is not giving me an option to configure it as

> different. Looks like the oo-install is assuming and  populating both

> broker_ip_addr and

> >> named_ip_adrr   as the same .

> >> This does not work in case of aws,I tried some trails with

> >> different

> config in the scripts but no success - Any work around /manual changes

> suggested ?

> >>

> >>

> >> Th script config looks like this  -

> >>

> >> Host Information

> >> +----------------+-----------------------+

> >> | Host           | broker.cloudshift.com |

> >> | Roles          | Broker                |

> >> | SSH Host       | localhost             |

> >> | User           | root                  |

> >> | IP Addr        | 54.221.250.159        |

> >> | IP Interface   | eth0                  |

> >> | Install Status | new                   |

> >> +----------------+-----------------------+

> >> +----------------+----------------------+

> >> | Host           | node1.cloudshift.com |

> >> | Roles          | Node                 |

> >> | SSH Host       | 54.204.45.129        |

> >> | User           | root                 |

> >> | IP Addr        | 54.204.45.129        |

> >> | IP Interface   | eth0                 |

> >> | Install Status | new                  |

> >> +----------------+----------------------+

> >>

> >> oo_install_configure_broker.cloudshift.com.pp

> >>

> >> [root ip-10-45-186-170 tmp]# cat

> >> oo_install_configure_broker.cloudshift.com.pp

> >> class { 'openshift_origin' :

> >>  bind_key =>

> >> 'rXZhU3SnlJmee+IT0muuZUrlW8QoxiglLJf5iquolicyIVcHJ52PwWvliVFl7y5n7b

> >> zE

> >> Cd6n6JjeCQO4gDKtUg==',

> >>  install_method => 'yum',

> >>  named_ip_addr => '54.221.250.159',

> >>  datastore_hostname => 'broker.cloudshift.com',  roles =>

> >> ['activemq','datastore','broker','named'],

> >>  repos_base =>

> >> 'http://mirror.openshift.com/pub/origin-server/release/3/rhel-6',

> >>  broker_hostname => 'broker.cloudshift.com',  activemq_hostname =>

> >> 'broker.cloudshift.com',  named_hostname =>

> >> 'broker.cloudshift.com',

> >> broker_ip_addr => '54.221.250.159',  jenkins_repo_base =>

> >> 'http://pkg.jenkins-ci.org/redhat',

> >>  domain => 'cloudshift.com',

> >> }

> >

> > Great point. Previously we hadn't hit any cases where "pinning" the

> named_ip_addr to the broker_ip_addr was a problem. However, if this is

> going to come up in every AWS deployment, I will modify oo-install to

> give the user optional control over that value.

> >

> >> Issue 2 :Node  Configuration -

> >> Do the script provide an option to configure  the following param

> >> as

> >> ip adresses.For some reason from my previous experience I had to

> make these as ip address Instead of hostname to get it working for

> Node in aws.

> >>

> >> [root ip-10-45-186-170 tmp]# cat

> >> oo_install_configure_node1.cloudshift.com.pp

> >> class { 'openshift_origin' :

> >>  node_ip_addr => '54.204.45.129',

> >>  bind_key =>

> >> 'rXZhU3SnlJmee+IT0muuZUrlW8QoxiglLJf5iquolicyIVcHJ52PwWvliVFl7y5n7b

> >> zE

> >> Cd6n6JjeCQO4gDKtUg==',

> >>  install_method => 'yum',

> >>  named_ip_addr => '54.221.250.159',

> >>  datastore_hostname => 'broker.cloudshift.com',  roles => ['node'],

> >> repos_base =>

> >> 'http://mirror.openshift.com/pub/origin-server/release/3/rhel-6',

> >>  broker_hostname => 'broker.cloudshift.com',  activemq_hostname =>

> >> 'broker.cloudshift.com',

> >

> > oo-install doesn't provide that option right now. Part of the issue

> is that broker_hostname is used to set the FQDN of the broker host,

> which could be a problem. Krishna, any thoughts on this one?

> >

> >>  conf_node_external_eth_dev => 'eth0',  node_hostname =>

> >> 'node1.cloudshift.com',  named_hostname => 'broker.cloudshift.com',

> >> broker_ip_addr => '54.221.250.159',  jenkins_repo_base =>

> >> 'http://pkg.jenkins-ci.org/redhat',

> >>  domain => 'cloudshift.com',

> >> }

> >>

> >> I have attached a sample config that worked using puppet.Any

> pointers/thought will be appreciated.

> >

> > I'll put up a change in oo-install for the first issue and follow up

> with Krishna about the second. Thanks for the great feedback; we

> really appreciate it!

> >

> > --Harrison

> >

> >>

> >> Thanks

> >> Shabna

> >>

> >>

> >> From: Harrison Ripps [mailto:hripps redhat com]

> >> Sent: Tuesday, January 14, 2014 6:50 PM

> >> To: Madathilthattantav, S.

> >> Cc: 

> dev lists openshift redhat com<mailto:dev lists openshift redhat com>;

> users lists openshift redhat com<mailto:users lists openshift redhat c

> om>

> >> Subject: Re: oo-install for Origin version 3

> >>

> >> Hi Shabna--

> >> We've tested the Origin-3-on-RHEL scenario an it does work. Check

> the oo-install guide on openshift.github.io for some prerequisites

> (like Puppet) that you will need to set up on your target host(s). Let

> me know if you run into any problems.

> >>

> >> Cheers,

> >> Harrison

> >>

> >> On Jan 14, 2014, at 6:36,

> <s madathilthattantav accenture com<mailto:s madathilthattantav accent

> ure.com>>

> wrote:

> >>

> >> Hi All

> >>

> >> Has anyone tried out Origin v3 install using oo-install utility in

> >> AWS

> >> ?(RHEL)

> >>

> >> Thanks

> >> Shabna

> >>

> >>

> >> This message is for the designated recipient only and may contain

> privileged, proprietary, or otherwise confidential information. If you

> have received it in error, please notify the sender immediately and

> delete the original. Any other use of the e-mail by you is prohibited.

> Where allowed by local law, electronic communications with Accenture

> and its affiliates, including e-mail and instant messaging (including

> content), may be scanned by our systems for the purposes of

> information security and assessment of internal compliance with Accenture policy. .

> >> ___________________________________________________________________

> >> __

> >> _

> >> ________________

> >>

> >> www.accenture.com<http://www.accenture.com>

> >> _______________________________________________

> >> users mailing list

> >> users lists openshift redhat com<mailto:users lists openshift redha

> >> t.com>

> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users

> >> <Puppetconfig.docx>

> >

> >

> >

> _______________________________________________ users mailing list

> users lists openshift redhat com

> http://lists.openshift.redhat.com/openshiftmm/listinfo/users                              




This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. .
______________________________________________________________________________________

www.accenture.com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]