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

Re: dev Digest, Vol 23, Issue 35



I had to re-install my broker using OO-Install again before I bypassed that error after fiddling with it for a long time. That way, you can trace your steps.


On Tue, Feb 18, 2014 at 6:20 PM, <dev-request lists openshift redhat com> wrote:
Send dev mailing list submissions to
        dev lists openshift redhat com

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
or, via email, send a message with subject or body 'help' to
        dev-request lists openshift redhat com

You can reach the person managing the list at
        dev-owner lists openshift redhat com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dev digest..."

Today's Topics:

   1. Re: oo-install broker failing to load (N. Harrison Ripps)
   2. Re: error Moped::Cluster nodes after oo-install
      (N. Harrison Ripps)


---------- Forwarded message ----------
From: "N. Harrison Ripps" <hripps redhat com>
To: Aditi Ghag <aditivghag gmail com>
Cc: "dev lists openshift redhat com" <dev lists openshift redhat com>
Date: Tue, 18 Feb 2014 12:06:35 -0500
Subject: Re: oo-install broker failing to load

On Feb 18, 2014, at 11:49 AM, Aditi Ghag <aditivghag gmail com> wrote:

> Yes, I have set the MONGO_HOST_PORT to be the DBserver ipaddress:port.
> Anyway I also did an nslookup, and it does return the correct mapping.

Is there anything about the way that you set these hosts up that differs from what is described in the oo-install guide[1]? You mentioned that you have the `ruby193-rubygem-sass-twitter-bootstrap` installed. It may be possible that this package pulled in versions of other gems that aren’t compatible with Origin. Also, did you use this as your Origin repo? https://mirror.openshift.com/pub/openshift-origin/release/3/rhel-6/

I am running out of ideas; if anyone else has thoughts on this, feel free to chime in :-)

—Harrison

[1]: http://openshift.github.io/documentation/oo_install_users_guide.html

>
>
> On Tue, Feb 18, 2014 at 11:43 AM, N. Harrison Ripps <hripps redhat com> wrote:
> Hey Aditi—
>
> On Feb 18, 2014, at 11:35 AM, Aditi Ghag <aditivghag gmail com> wrote:
>
> > I don't know if this is relevant, but I had to specify the database name when I was connecting to the mongo server from the broker.
> > So here is the command-
> > mongo --verbose openshift_broker_dev  -u openshift -p mooo --host 128.XX.XX.XX:27017
> >
> > Now if I leave out the "openshift_broker_dev" , the login fails. It took me a while to figure this out because I din't find this documented anywhere. Could this be an issue? Is the broker specifying the right database when it tries to authenticate to the mongo server?
>
> I don’t know. Anyone have any ideas here? I would expect that since MONGO_DB is captured in the broker.conf file that the broker is using that value as part of the connection attempt.
>
> Does the MONGO_HOST_PORT value in your broker.conf file reflect the correct host:IP info? If it contains a hostname instead of the DB host’s IP address, can you successfully do an nslookup of the DB host from the Broker?
>
>
> > On Tue, Feb 18, 2014 at 11:29 AM, Aditi Ghag <aditivghag gmail com> wrote:
> > Hi,
> >
> > I restarted the openshift-broker, made sure the broker is still able to connect to the DBserver. I then ran the oo-diagnostics script, and its still giving me the same error.
> > Any ideas?
> >
> > Aditi
> >
> >
> > On Tue, Feb 18, 2014 at 11:09 AM, N. Harrison Ripps <hripps redhat com> wrote:
> >
> > On Feb 17, 2014, at 5:50 PM, Aditi Ghag <aditivghag gmail com> wrote:
> >
> > > Hey Harrison,
> > >
> > > I apologize for not giving all the details.
> > > But, I already tested the communication link between broker and the db. So I have all the four componets(broker,db,msg and node) running on four separate machines.
> > > Based on the mongo_ values given in the broker.conf file, I executed following command-
> > > mongo --verbose openshift_broker_dev  -u openshift -p mooo --host 128.XX.XX.XX:27017
> >
> > Okay, so it sounds like puppet laid down the broker config and installed MongoDB correctly on the DB host. You were able to successfully connect to the DB from the Broker using the mongo client.
> >
> > My only other thought is that maybe you hit a race condition. Perhaps the mongod service wasn’t up yet when the broker tried to start. If you run `service openshift-broker restart` now, do you still see the MongoDB errors?
> >
> > Give that a shot and let me know the outcome.
> >
> > >
> > > MongoDB shell version: 2.4.6
> > >
> > > Fri Feb 14 14:10:11.168 versionArrayTest passed
> > >
> > > connecting to: 128.XX.XX.XX:27017/openshift_broker_dev
> > >
> > > Fri Feb 14 14:10:11.209 creating new connection to:128.XX.XX.XX:27017
> > >
> > > Fri Feb 14 14:10:11.210 BackgroundJob starting: ConnectBG
> > >
> > > Fri Feb 14 14:10:11.210 connected connection!
> > >
> > > Welcome to the MongoDB shell.
> > >
> > > For interactive help, type "help".
> > >
> > > For more comprehensive documentation, see
> > >
> > > http://docs.mongodb.org/
> > >
> > > Questions? Try the support group
> > >
> > > http://groups.google.com/group/mongodb-user
> > >
> > > > exit
> > >
> > > bye
> > >
> > > Fri Feb 14 14:11:41.748 freeing 2 uncollected N5mongo14DBClientCursorE objects
> > >
> > > Fri Feb 14 14:11:41.748 freeing 1 uncollected N5mongo20DBClientWithCommandsE objects
> > >
> > > Fri Feb 14 14:11:41.748 freeing 2 uncollected N5mongo10BSONHolderE objects
> > >
> > >
> > >
> > > It looks to me that the connection was established successfully.
> > >
> > > Am I missing anything here?
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Aditi
> > >
> > > On Mon, Feb 17, 2014 at 3:33 PM, N. Harrison Ripps <hripps redhat com> wrote:
> > > Hey Aditi—
> > >
> > > On Feb 17, 2014, at 3:02 PM, Aditi Ghag <aditivghag gmail com> wrote:
> > >
> > > > Hi Harrison,
> > > >
> > > > Thanks for your reply.
> > > >
> > > > I am using the redhat 6.5 OS.
> > >
> > > Okay, cool—see below.
> > >
> > > >
> > > > Thanks,
> > > > Aditi
> > > >
> > > >
> > > >
> > > >> On 17-Feb-2014, at 14:59, "N. Harrison Ripps" <hripps redhat com> wrote:
> > > >>
> > > >> Hi Aditi—
> > > >> What OS are you trying this on?
> > > >>
> > > >>> On Feb 14, 2014, at 4:36 PM, Aditi Ghag <aditivghag gmail com> wrote:
> > > >>>
> > > >>> Hi,
> > > >>>
> > > >>> I have installed OpenShift Origin using the oo-install command(sh <(curl -s https://install.openshift.com/)).
> > > >>> I have the components broker, msgserver, DBserver and node setup on four different machines.
> > > >>>
> > > >>> The broker application is failing to load. Here is the output of the oo-diagnostic script-
> > > >>> /usr/sbin/oo-diagnostics
> > > >>>
> > > >>> 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
> > >
> > > It is possible that MongoDB didn’t fully install. Try this:
> > >
> > > 1. Look at the MongoDB credentials in your broker config file. The config file is either:
> > >     * /etc/openshift/broker.conf or
> > >     * /etc/openshift/broker-dev.conf
> > >    You want the MONGO_* values
> > >
> > > 2. Try to connect directly to MongoDB from the command line on the broker:
> > >    `mongo localhost:27017/<MONGO_DB> -u <MONGO_USER> -p <MONGOPASSWORD>`
> > >
> > > If you -can’t- connect that way, then the Broker mongo configuration needs some help. In that case, have a look at the “Configure mongos” portion of the Comprehensive Deployment Guide: http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#configure-em-mongod-em
> > >
> > > >>>
> > > >>> @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=>"cfc0ea89ffac344b", :key=>"e0829b4e2c9a8d23aa483596011ac07d"}
> > > >>>
> > > >>> @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 googled this error, I came across a thread where this error message was mentioned. But, there was no fix mentioned.
> > > >>>
> > > >>> Please note that I have installed the ruby193-rubygem-sass-twitter-bootstrap package.
> > > >>>
> > > >>> Please suggest what the exact problem is and how to go about solving this error. Let me know if you need any other information.
> > > >>>
> > > >>>
> > > >>>
> > > >>> Thanks,
> > > >>>
> > > >>> Aditi
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>> _______________________________________________
> > > >>> dev mailing list
> > > >>> dev lists openshift redhat com
> > > >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> > > >>
> > >
> > >
> >
> >
> >
>
>



---------- Forwarded message ----------
From: "N. Harrison Ripps" <hripps redhat com>
To: Mochamad Yusuf <fearleeee gmail com>
Cc: dev lists openshift redhat com
Date: Tue, 18 Feb 2014 12:20:46 -0500
Subject: Re: error Moped::Cluster nodes after oo-install

On Feb 18, 2014, at 12:09 PM, Mochamad Yusuf <fearleeee gmail com> wrote:

> content of /etc/openshift/broker-dev.conf
>
> MONGO_HOST_PORT="localhost:27017"
> MONGO_USER="openshift"
> MONGO_PASSWORD="mooo"
> MONGO_DB="openshift_broker_dev"
> MONGO_TEST_DB="openshift_broker_test"
> MONGO_SSL="false"
> #Enables gear/filesystem resource usage tracking
> ENABLE_USAGE_TRACKING_DATASTORE="true"
> #Log resource usage information
> ENABLE_USAGE_TRACKING_AUDIT_LOG="false"
> USAGE_TRACKING_AUDIT_LOG_FILE="/var/log/openshift/broker/usage.log"
>
> testing login
> [root broker ~]# mongo localhost:27017/openshift_broker_dev -u openshift -p mooo
> MongoDB shell version: 2.4.6
> connecting to: localhost:27017/openshift_broker_dev
> Tue Feb 18 12:07:47.776 Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" } at src/mongo/shell/db.js:228
> exception: login failed

Okay, can you verify that mongodb is running? systemctl status mongod.service
Also, what repo did you use for the lo-install yum source? Was it:

https://mirror.openshift.com/pub/openshift-origin/release/3/fedora-19/

As with Aditi’s issues, I’m running out of ideas; broker / mongodb interaction is not my forte, so hopefully someone else can chime in.

>
> content of /etc/openshift/broker.conf
> #Broker datastore configuration
> MONGO_REPLICA_SETS=false
> # Replica set example: "<host-1>:<port-1> <host-2>:<port-2> ..."
> MONGO_HOST_PORT="broker.openshift.iard.com:27017"
> MONGO_USER="openshift"
> MONGO_PASSWORD="mongopass"
> MONGO_DB="openshift_broker"
> MONGO_TEST_DB="openshift_broker_test"
> MONGO_SSL="false"
> #Enables gear/filesystem resource usage tracking
> ENABLE_USAGE_TRACKING_DATASTORE="true"
> #Log resource usage information
> ENABLE_USAGE_TRACKING_AUDIT_LOG="false"
> USAGE_TRACKING_AUDIT_LOG_FILE="/var/log/openshift/broker/usage.log"
>
> testing login
> [root broker ~]# mongo localhost:27017/openshift_broker -u openshift -p mongopass
> MongoDB shell version: 2.4.6
> connecting to: localhost:27017/openshift_broker
> Tue Feb 18 12:09:27.530 Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" } at src/mongo/shell/db.js:228
> exception: login failed
>
>
> On 18 February 2014 08:30, N. Harrison Ripps <hripps redhat com> wrote:
> Hi Mochamad—
>
> On Feb 17, 2014, at 7:09 PM, Mochamad Yusuf <fearleeee gmail com> wrote:
>
> > hei Harrison, thanks for coming.. :)
> > i'm already write the detail...
> > fedora 19 minimal install,, two machine. 1 broker 1 node.
>
> Indeed you did! Sorry for missing that.
>
> > On 17 February 2014 11:59, N. Harrison Ripps <hripps redhat com> wrote:
> > Hi Mochamad—
> > What OS are you trying this on?
> >
> > On Feb 15, 2014, at 7:46 PM, Mochamad Yusuf <fearleeee gmail com> wrote:
> >
> > > i just finished install origin using oo-install
> > > fedora 19 minimal install, two machine ( 1 broker and 1 node)
> > > i get some error when running oo-accept-broker and oo-accept-node
> > > 10.11.227.32 ==> my broker's IP
> > > output from oo-accept-broker
> > > [root broker ~]# oo-accept-broker
> > > NOTICE: SELinux is Enforcing
> > > NOTICE: SELinux is  Enforcing
> > > exception: connect failed
> > > FAIL: error logging into mongo db:   MOPED: Retrying connection to primary for replica set <Moped::Cluster nodes=[<Moped::Node resolved_address="10.11.227.32:27017">]>:  MOPED: Retrying connection to primary for replica set <Moped::Cluster nodes=[<Moped::Node resolved_address="10.11.227.32:27017">]>/MOPED: --username Retrying, exit code: 1
> > > NOTICE: unknown auth class: MOPED: Retrying connection to primary for replica set <Moped::Cluster nodes=[<Moped::Node resolved_address="10.11.227.32:27017">]>
> > > NOTICE: unknown dns class: MOPED: Retrying connection to primary for replica set <Moped::Cluster nodes=[<Moped::Node resolved_address="10.11.227.32:27017">]>
> > > NOTICE: unknown messaging class: MOPED: Retrying connection to primary for replica set <Moped::Cluster nodes=[<Moped::Node resolved_address="10.11.227.32:27017">]>
> > > 1 ERRORS
>
> This looks like a general MongoDB connectivity problem, so please try the same manual connection that I talked through on this thread:
>
> http://lists.openshift.redhat.com/openshift-archives/dev/2014-February/msg00078.html
>
> If you are successful in your attempt to connect manually, then restart the Broker and see if the errors are still raised:
>
>     systemctl restart openshift-broker.service
>
> Let me know the outcome of these steps.
>
> > >
> > > output from oo-accept-node
> > > [root node1 ~]# oo-accept-node
> > > FAIL: /etc/openshift/node.conf: BROKER_HOST broker.openshift.iard.com does not resolve (getaddrinfo: Name or service not known)
> > > FAIL: /etc/openshift/node.conf: PUBLIC_HOSTNAME node1.openshift.iard.com does not resolve as a FQDN (getaddrinfo: Name or service not known)
> > > 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
> > > 5 ERRORS
> > >
> > > mco ping -v
> > > The ping application failed to run, use -v for full error details: undefined method `body' for nil:NilClass
> > >
> > > undefined method `body' for nil:NilClass (NoMethodError)
> > >         from /usr/libexec/mcollective/mcollective/connector/activemq.rb:246:in `receive'  <----
> > >         from /usr/share/ruby/vendor_ruby/mcollective/client.rb:89:in `receive'
> > >         from /usr/share/ruby/vendor_ruby/mcollective/client.rb:152:in `block (2 levels) in req'
> > >         from /usr/share/ruby/vendor_ruby/mcollective/client.rb:151:in `loop'
> > >         from /usr/share/ruby/vendor_ruby/mcollective/client.rb:151:in `block in req'
> > >         from /usr/share/ruby/timeout.rb:66:in `timeout'
> > >         from /usr/share/ruby/vendor_ruby/mcollective/client.rb:148:in `req'
> > >         from /usr/libexec/mcollective/mcollective/application/ping.rb:58:in `main'
> > >         from /usr/share/ruby/vendor_ruby/mcollective/application.rb:285:in `run'
> > >         from /usr/share/ruby/vendor_ruby/mcollective/applications.rb:23:in `run'
> > >         from /usr/sbin/mco:20:in `<main>'
> > >
> > >
> > > what can i do to solve it ??
> > >
> > > _______________________________________________
> > > dev mailing list
> > > dev lists openshift redhat com
> > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> >
> >
>
>


_______________________________________________
dev mailing list
dev lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev




--
Mfawa Alfred Onen
M.Sc Telecoms, B.Eng Elect/Elect, CCNA, RHCE(in view)
System Administrator
Department of Computer Science,
Bingham University.

E-Mail: systemadmin binghamuni edu ng
Phone1: +234 805 944 3154
Phone2: +234 803 079 6088


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