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

Re: Origin 4 on RHEL 6.5

On Tue, Jan 13, 2015 at 07:49:48PM +0000, Massimiliano Dessì wrote:
2015-01-13 19:11 GMT+00:00 Miciah Dashiel Butler Masters <
mmasters redhat com>:

On Tue, Jan 13, 2015 at 04:43:36PM +0100, Massimiliano Dessě wrote:

Hi all,
I've installed origin 4 on RHEL  6.5
in a vmware infrastructure,
(deploy with one broker and two nodes)
with the oo_deployment_guide_comprehensive.
When I execute the oo-diagnostics on the node  I receive the follows
in the nodes

[root node02 ~]# oo-diagnostics
FAIL: run_script
oo-accept-node had errors:
FAIL: service ruby193-mcollective not running
FAIL: Could not get SELinux context for ruby193-mcollective
eth0: error fetching interface information: Device not found
FAIL: tc htb qdisc not configured

Are you using a different network interface from eth0? If so, you may
have some configuration where you need to substitute the correct name.
Verify that the EXTERNAL_ETH_DEV setting in /etc/openshift/node.conf is
correct.  Your DHCP configuration may also need to be fixed if it has
the wrong interface name.

in /etc/openshift/node.conf there is EXTERNAL_ETH_DEV=bond0

Is it possible you have the setting duplicated? oo-accept-node reads the
setting from that file, so I don't understand why it is complaining
about the wrong interface.  Furthermore, there are other tests that
check or use the EXTERNAL_ETH_DEV setting, so I am surprised that only
this test is failing.

What does the command `scl enable ruby193 'ruby -r openshift-origin-common -e "puts OpenShift::Config.new(OpenShift::Config::NODE_CONF_FILE).get('\''EXTERNAL_ETH_DEV'\'')"'`

What does the command `/sbin/tc qdisc show dev bond0` output?

This test isn't critical; it means that traffic control may not be
enforced correctly, so gear bandwidth may not be limited correctly.
You probably want to fix it, but it should be possible to get OpenShift
generally functioning without it.


--END oo-accept-node OUTPUT--
FAIL: test_services_enabled
     The following service(s) are not currently started:
     These services are required for OpenShift functionality.

Are there any error messages in


 FAIL: test_mcollective_context
     Mcollectived is not running in the expected SELinux context, which
     may result in node execution failures. Please check that the correct
     context is set on /opt/rh/ruby193/root/usr/sbin/mcollectived and
the correct SELinux
     policies are loaded.
       Expected: system_r:openshift_initrc_t:s0-s0:c0.c1023
       Found: system_r:openshift_initrc_t:s0-s0:c0.c1023

I've "fixed"
with the content of this
(chcon -t openshift_initrc_exec_t /etc/init.d/ruby193-mcollective)

What does `pgrep -f mcollectived` show? This error message likely comes
about because MCollective is not running and the test is misinterpreting
output from the ps command.

seem up, but the command
# service ruby193-mcollective status
"mcollectived is stopped"

Does `mco ping` work?

Check the output of ps `pgrep -f mcollectived` to make sure the process
really is the MCollective process (it should show 'ruby /opt/rh/ruby193/root/usr/sbin/mcollectived --pid=/opt/rh/ruby193/root/var/run/mcollectived.pid --config=/opt/rh/ruby193/root/etc/mcollective/server.cfg').

Maybe the process is running but its lockfile and pidfile somehow got
deleted.  Try running `service ruby193-mcollective stop`, then kill the
process manually if it's still running, and then run the command
`service ruby193-mcollective start` whilst monitoring the output in

Miciah Dashiel Butler Masters <mmasters redhat com>

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