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

Re: Issues during openshift origin installation



You need to install the augeas package: yum install augeas and re-run oo-diagnostics


On Fri, Feb 21, 2014 at 8:28 AM, <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: Issues during openshift origin installation (Sai Srujan)


---------- Forwarded message ----------
From: Sai Srujan <srujanpatha gmail com>
To: "N. Harrison Ripps" <hripps redhat com>
Cc: dev lists openshift redhat com
Date: Fri, 21 Feb 2014 12:58:32 +0530
Subject: Re: Issues during openshift origin installation
Hi Harrison,

I have tried a fresh installation,but getting an error,could you please guide me further on how to install the augtool.

* Target host is running Red Hat Enterprise Linux
* Located getenforce
* SELinux is running in permissive mode
* Located yum
* Located puppet
* ERROR: Could not locate augtool... Repository 'jenkins_repo' is missing name in configuration, using id
Repository 'origin-base' is missing name in configuration, using id
Repository 'origin-deps' is missing name in configuration, using id
you will need to add a repository that provides this.
* Located dnssec-keygen
* Located htpasswd
* Located scl
* The ruby193 software collection is installed.
Repository 'jenkins_repo' is missing name in configuration, using id
Repository 'origin-base' is missing name in configuration, using id
Repository 'origin-deps' is missing name in configuration, using id
* epel repository is present and enabled

The deployment check was not successful. See above for specific issues.
oo-install exited; removing temporary assets.
n,but it is giving me this error:

TIA
Regards
Srujan


On Fri, Feb 21, 2014 at 8:01 AM, Luke Meyer <lmeyer redhat com> wrote:



From: "N. Harrison Ripps" <hripps redhat com>
To: "Sai Srujan" <srujanpatha gmail com>
Cc: dev lists openshift redhat com
Sent: Thursday, February 20, 2014 4:15:56 PM
Subject: Re: Issues during openshift origin installation



On Feb 20, 2014, at 12:10, Sai Srujan <srujanpatha gmail com> wrote:

> Hi Harrison,
>
> I have rebooted the host.Still facing the same issue.As every thing is present on the same host
> Do i need to change any conf files??

You shouldn't _need_ to change any config files...

> Regards
> Srujan
>
>
> On Thu, Feb 20, 2014 at 10:06 PM, N. Harrison Ripps <hripps redhat com> wrote:
> Hey Srujan--
>
> On Feb 20, 2014, at 11:33, Sai Srujan <srujanpatha gmail com> wrote:
>
> > Hi Harrison,
> >
> > I did not reboot the broker. Is this issue related to activemq.???
> > When i ran service activemq status, it is not running.
>
> Per the oo-install Guide, you should reboot your hosts. The recommended order for reboots is list here:
>
> http://openshift.github.io/documentation/oo_install_users_guide.html#reboot
>
> Give that a shot and let us know if you're still hitting problems.
>
> >
> >
> > Regards
> > Srujan
> >
> >
> >
> >
> > On Thu, Feb 20, 2014 at 9:05 PM, N. Harrison Ripps <hripps redhat com> wrote:
> > Hey Srujan--
> > Don't forget to CC the dev list.
> >
> > On Feb 20, 2014, at 10:05, Sai Srujan <srujanpatha gmail com> wrote:
> >
> > > Hi Harrison,
> > >
> > > I have restarted httpd and openshift-broker and ran the oo-accept-broker -v,still i am getting the error
> >
> > Out of curiosity, did you reboot the broker after you ran the installation?
> >
> > > :
> > > INFO: Broker package is: openshift-origin-broker
> > > INFO: checking packages
> > > INFO: checking package rubygem-openshift-origin-common
> > > INFO: checking package rubygem-openshift-origin-controller
> > > INFO: checking package openshift-origin-broker
> > > INFO: checking package ruby193-rubygem-rails
> > > INFO: checking package ruby193-rubygem-passenger
> > > INFO: checking package ruby193-rubygems
> > > INFO: checking ruby requirements
> > > INFO: checking ruby requirements for openshift-origin-controller
> > > INFO: checking ruby requirements for config/application
> > > INFO: checking that selinux modules are loaded
> > > NOTICE: SELinux is Permissive
> > > NOTICE: SELinux is  Permissive
> > > INFO: checking firewall settings
> > > INFO: checking mongo datastore configuration
> > > INFO: Datastore Host: localhost.openshift.com
> > > INFO: Datastore Port: 27017
> > > INFO: Datastore User: openshift
> > > INFO: Datastore SSL: false
> > > INFO: Datastore Password has been set to non-default
> > > INFO: Datastore DB Name: openshift_broker
> > > INFO: Datastore: mongo db service is remote
> > > INFO: checking mongo db login access
> > > INFO: mongo db login successful: localhost.openshift.com:27017/openshift_broker --username openshift
> > > INFO: checking services
> > > INFO: checking cloud user authentication
> > > INFO: auth plugin = OpenShift::RemoteUserAuthService
> > > INFO: auth plugin: OpenShift::RemoteUserAuthService
> > > INFO: checking remote-user auth configuration
> > > INFO: Auth trusted header: REMOTE_USER
> > > INFO: Auth passthrough is enabled for OpenShift services
> > > INFO: Got HTTP 200 response from https://localhost/broker/rest/api

Can anyone shed some light on these? (below)

> > > FAIL: Did not get expected HTTP 200 response from https://localhost/broker/rest/ cartridges

Everything succeeded except this. This is a call to the API that lists the cartridges the broker knows about by querying the node(s).


> > > INFO: Got HTTP 401 response from https://localhost/broker/rest/user
> > > INFO: Got HTTP 401 response from https://localhost/broker/rest/domains
> >
> > Does anyone on the OpenShift team know why the basic API URL would succeed, but the other URLs would fail?

The fact that the other responses were fine (401s were expected) indicates that the broker is installed and generally doing OK.

This particular failure can indicate a problem from a number of things. The most common is when no cartridges could be retrieved because the broker-node communication is not working. That can mean activemq is down, or the mcollective service is down or misconfigured, or the DNS for the host mcollective is configured against isn't working, or a port is closed at the firewall, or ... the list kinda goes on. It can also mean other problems with the broker trying to read and store information. It's a good test because a lot of OpenShift functionality has to work or it fails. The down side is that it doesn't tell you much about *what* failed.

Look in the broker server log in /var/log/openshift/broker/development.log for a stack trace.
Look in the node server log in /var/log/openshift/node/*mcollective.log to see if it even got a request for cartridges.

What does oo-diagnostics say?



> >
> > > INFO: checking dynamic dns plugin
> > > INFO: dynamic dns plugin = OpenShift::NsupdatePlugin
> > > INFO: checking bind dns plugin configuration
> > > INFO: DNS Server: 173.38.225.182
> > > INFO: DNS Port: 53
> > > INFO: DNS Zone: citsa.com
> > > INFO: DNS Domain Suffix: citsa.com
> > > INFO: DNS Update Auth: key
> > > INFO: DNS Key Name: citsa.com
> > > INFO: DNS Key Value: *****
> > > INFO: adding txt record named testrecord.citsa.com to server 173.38.225.182: thi                                                                                                                                                 s_is_a_test
> > > INFO: txt record successfully added
> > > INFO: deleteing txt record named testrecord.citsa.com to server 173.38.225.182:
> > > INFO: txt record successfully deleted
> > > INFO: checking messaging configuration
> > > INFO: messaging plugin = OpenShift::MCollectiveApplicationContainerProxy
> > > 1 ERRORS
> > >
> > >
> > > Regards:
> > > Srujan
> > >
> > >
> > > On Thu, Feb 20, 2014 at 7:28 PM, N. Harrison Ripps <hripps redhat com> wrote:
> > > Hey Srujan--
> > >
> > > On Feb 20, 2014, at 0:27, Sai Srujan <srujanpatha gmail com> wrote:
> > >
> > > > Hi,
> > > >
> > > > 1)when i run rhc setup --server=localhost --insecure,i am getting the below error:
> > > >
> > > > OpenShift Client Tools (RHC) Setup Wizard
> > > >
> > > > This wizard will help you upload your SSH keys, set your application namespace, and check that other programs like Git are properly installed.
> > > >
> > > > Using an existing token for xxx gmail com to login to local host
> > > >
> > > > Saving configuration to /root/.openshift/express.conf ... done
> > > >
> > > > Checking for git ... found git version 1.7.1
> > > >
> > > > Checking common problems .
> > > >
> > > > An error occurred while communicating with the server. This problem may only be temporary. Check that you have correctly specified your OpenShift server 'https://localhost/broker/rest/domains'.
> > > >
> > > > Checking for a domain ... An error occurred while communicating with the server. This problem may only be temporary. Check that you have correctly specified your OpenShift server 'https://localhost/broker/rest/domains'.
> > > >
> > > >
> > > > 2) When i run  oo-accept-broker -v:
> > > >
> > > > INFO: Broker package is: openshift-origin-broker
> > > > INFO: checking packages
> > > > INFO: checking package rubygem-openshift-origin-common
> > > > INFO: checking package rubygem-openshift-origin-controller
> > > > INFO: checking package openshift-origin-broker
> > > > INFO: checking package ruby193-rubygem-rails
> > > > INFO: checking package ruby193-rubygem-passenger
> > > > INFO: checking package ruby193-rubygems
> > > > INFO: checking ruby requirements
> > > > INFO: checking ruby requirements for openshift-origin-controller
> > > > INFO: checking ruby requirements for config/application
> > > > INFO: checking that selinux modules are loaded
> > > > NOTICE: SELinux is Permissive
> > > > NOTICE: SELinux is  Permissive
> > > > INFO: checking firewall settings
> > > > INFO: checking mongo datastore configuration
> > > > INFO: Datastore Host: localhost.openshift.citsa.com
> > > > INFO: Datastore Port: 27017
> > > > INFO: Datastore User: openshift
> > > > INFO: Datastore SSL: false
> > > > INFO: Datastore Password has been set to non-default
> > > > INFO: Datastore DB Name: openshift_broker
> > > > INFO: Datastore: mongo db service is remote
> > > > INFO: checking mongo db login access
> > > > INFO: mongo db login successful: localhost.openshift.citsa.com:27017/openshift_broker --username openshift
> > > > INFO: checking services
> > > > INFO: checking cloud user authentication
> > > > INFO: auth plugin = OpenShift::RemoteUserAuthService
> > > > INFO: auth plugin: OpenShift::RemoteUserAuthService
> > > > INFO: checking remote-user auth configuration
> > > > INFO: Auth trusted header: REMOTE_USER
> > > > INFO: Auth passthrough is enabled for OpenShift services
> > > > FAIL: Did not get expected HTTP 200 response from https://localhost/broker/rest/api
> > > > FAIL: Did not get expected HTTP 200 response from https://localhost/broker/rest/cartridges
> > >
> > > Restart the httpd and openshift-broker services. The 401 error indicates that one of these isn't running.
> > >
> > > > INFO: Got HTTP 401 response from https://localhost/broker/rest/user
> > > > INFO: Got HTTP 401 response from https://localhost/broker/rest/domains
> > > > INFO: checking dynamic dns plugin
> > > > INFO: dynamic dns plugin = OpenShift::NsupdatePlugin
> > > > INFO: checking bind dns plugin configuration
> > > > INFO: DNS Server: 173.38.225.182
> > > > INFO: DNS Port: 53
> > > > INFO: DNS Zone: citsa.com
> > > > INFO: DNS Domain Suffix: citsa.com
> > > > INFO: DNS Update Auth: key
> > > > INFO: DNS Key Name: citsa.com
> > > > INFO: DNS Key Value: *****
> > > > INFO: adding txt record named testrecord.citsa.com to server 173.38.225.182: this_is_a_test
> > > > INFO: txt record successfully added
> > > > INFO: deleteing txt record named testrecord.citsa.com to server 173.38.225.182:
> > > > INFO: txt record successfully deleted
> > > > INFO: checking messaging configuration
> > > > INFO: messaging plugin = OpenShift::MCollectiveApplicationContainerProxy
> > > > 2 ERRORS
> > > >
> > > > please help me in resolving the issues
> > > >
> > > >
> > > > TIA
> > > > Regards,
> > > > Srujan
> > > > _______________________________________________
> > > > 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



_______________________________________________
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]