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

Re: error after oo-install



On 05/02/14 08:19 -0800, Mochamad Yusuf wrote:
  On 4 February 2014 10:40, Jason DeTiberus <[1]jdetiber redhat com>
  wrote:

  On 04/02/14 12:47 -0500, N. Harrison Ripps wrote:

    On Feb 4, 2014, at 12:18 , Mochamad Yusuf <[2]fearleeee gmail com>
    wrote:

    today i just installed origin using oo-install
    two machine(broker and node), fedora 19 minimal install.
    output from oo-accept-broker
    [root broker ~]# oo-accept-broker
    NOTICE: SELinux is Enforcing
    NOTICE: SELinux is  Enforcing
    FAIL: Did not get expected HTTP 200 response from
    [3]https://localhost/broker/rest/cartridges
    FAIL: configured messaging class is the abstract one:
    OpenShift::ApplicationContainerProxy
    2 ERRORS

    My initial thought was that this is a simple issue of
    openshift-broker or httpd not running; he's tried restarting those
    but with no success. Does anyone have any other suggestions for him?

    Looks like rubygem-openshift-origin-msg-broker-mcollective is not
    installed (or the
    /etc/openshift/plugins.d/openshift-origin-msg-broker-mcollective.con
    f
    file is not present (an example file is here:
    /etc/openshift/plugins.d/openshift-origin-msg-broker-mcollective.con
    f.example).
    You can also verify the following logfiles for more details on the
    non-200 response code to the /broker/rest/cartridges request in the
    following logfiles:
    /var/log/openshift/broker/production.log
    /var/log/openshift/broker/httpd/error_log.

    output from oo-acept-node
    [root node1 ~]# oo-accept-node
    /usr/sbin/oo-accept-node:431:in `check_cgroup_procs': undefined
    method `value' for nil:NilClass (NoMethodError)
            from /usr/sbin/oo-accept-node:889:in `<main>'

    This looked like a bug in `oo-accept-node`, anyone have any ideas on
    this?

    The district_uuid fact is missing.  Is the
    openshift-origin-msg-node-mcollective package installed?

    is there a problem with my broker ??

    Overall, it looks like the puppet setup failed to at least setup the
    broker and node mcollective plugins.  The output from the puppet run
    would probably shed more light on exactly what went wrong.
    --
    Jason DeTiberus

  thanks a lot Jason, i get a PASS from oo-accept-broker and
  oo-accept-node.
  But when i open up my broker node [4]https://10.227.30 it's always
  redirect me into [5]https://10.11.227.30/console/unauthorized
  nothing show up...
  is there something that i can do ??


Without the puppet output or log output, I would hazard a guess that
the puppet run failed to configure the auth plugin.

Verify the following:
- rubygem-openshift-origin-auth-remote-user is installed
- /etc/openshift/plugins.d/openshift-origin-auth-remote-user.conf exists and has the same content as openshift-origin-auth-remote-user.conf.example
- /etc/openshift/console.conf has CONSOLE_SECURITY set to remote_user
- /etc/openshift/console.conf has REMOTE_USER_HEADER set to REMOTE_USER
- /etc/openshift/console.conf has REMOTE_UESR_COPY_HEADERS set to X-Remote-User
- /etc/openshift/htpasswd exists (can be created or edited with the htpasswd command)

If you have to make any of the changes above, restart openshift-broker
and openshift-console.

You can also try to run oo-diagnostics (most of the tests work with
origin, but there could be some false positives there still).

--
Jason DeTiberus


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