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

Re: FAIL: No node hosts responded. Run 'oo-mco ping' and troubleshoot if this is unexpected.



Thank you for suggestion, Michael.
Here is the output.
=====
[root vs114 ~]# oo-accept-systems -vv
INFO: checking that each public_hostname resolves to external IP
FAIL: No node hosts responded. Run 'oo-mco ping' and troubleshoot if
this is unexpected.
1 ERRORS
[root vs114 ~]# oo-mco ping
vs115.example.com                          time=81.08 ms

---- ping statistics ----
1 replies max: 81.08 min: 81.08 avg: 81.08
=====

Both hosts has two dns names. In particular the node has
node.lab4.example.com (created due to comprehensive guide) and
vs115.example.com (was assigned before OpenShift installation). The
broker can resolve both of them. However it's not clear to me if they
are just aliases or there is additional sense for these names. I'd
prefer to use vs115.example.com and do not create additional aliases
if it's possible.

> Then restart the ruby193-mcollective process
I can not do this due to https://bugzilla.redhat.com/show_bug.cgi?id=1074553
I can only restart the node host. I attached oo-diagnostics output
from the node. I can see that ruby193-mcollective is started using "ps
-A", and oo-mco ping works for me (as I mentioned in the previous
letter).

I have ruby193-mcollective-2.4.1-2.el6oso installed.


On Tue, Sep 30, 2014 at 3:23 AM, The Dude
<michael mcconachie hotmail com> wrote:
>> From: anton ananich inpun com
>> Date: Tue, 30 Sep 2014 02:17:39 +0300
>> Subject: FAIL: No node hosts responded. Run 'oo-mco ping' and troubleshoot
>> if this is unexpected.
>> To: users lists openshift redhat com
>>
>> Hi, All!
>>
>> I'm trying to install OpenShift 4 Origin, and I passed nearly to the
>> very end and now I need to introduce a node host to a broker host. In
>> the broker host I try this:
>>
>> =====
>> [root vs114 ~]# oo-accept-systems -w 2
>
> Hi Anton, did you first try oo-accept-node -vv from the node host to see if
> you can trap any specific errors?
>
> Double check and make sure that you either manually create a dns entry for
> the node (dont forget to restart named if you do it via vim -or- rndc reload
> if you use nsupdate) or run the oo-register-dns utility for the node in
> question. Then, re-run oo-accept-node -vv and make sure that it exits
> cleanly.  Then restart the ruby193-mcollective process and attempt another
> oo-mco ping.  From there, do an oo-diagnostics (which triggers
> oo-accept-systems -w 2 anyway) and see if you're good to go.
>
>> FAIL: No node hosts responded. Run 'oo-mco ping' and troubleshoot if
>> this is unexpected.
>> 1 ERRORS
>> [root vs114 ~]# oo-mco ping
>> vs115.example.com time=81.81 ms
>>
>> ---- ping statistics ----
>> 1 replies max: 81.81 min: 81.81 avg: 81.81
>> =====
>>
>> As you can see, the situation is strange. The broker seems to be able
>> to connect to the node, however the host can not be accepted.
>>
>> I can see the following message in ruby193-mcollective-client.log at
>> the broker host:
>> =====
>> W, [2014-09-30T01:26:38.858857 #2208] WARN -- : client.rb:218:in
>> `rescue in start_receiver' Could not receive all responses. Expected :
>> 1. Received : 0
>> =====
>>
>> I'd appreciate any suggestion on what the trouble could be. I do not
>> know what additional information could be useful, but can provide any
>> by request.
>>
>> Regards,
>> Anthony
>>
>> _______________________________________________
>> users mailing list
>> users lists openshift redhat com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
[root vs115 ~]# oo-diagnostics 
WARN: test_selinux_enabled
            The following recent entries in /var/log/audit/audit.log likely indicate problems:
            
type=AVC msg=audit(1412018851.641:455): avc:  denied  { write } for  pid=5735 comm="quotacheck" name="/" dev=dm-0 ino=2 scontext=unconfined_u:unconfined_r:quota_t:s0-s0:c0.c1023 tcontext=system_u:object_r:file_t:s0 tclass=dir

            Note that SELinux violations are not always logged in the audit log.

FAIL: run_script
oo-accept-node had errors:
--BEGIN OUTPUT--
FAIL: service ruby193-mcollective not running
FAIL: service oddjobd not running
FAIL: Could not get SELinux context for ruby193-mcollective
FAIL: Could not get SELinux context for oddjobd
4 ERRORS

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

WARN: test_services_enabled
      The following service(s) are not currently started:
        ntpd, oddjobd, messagebus, openshift-watchman
      Unless you know they are not needed, please start these services.

WARN: test_services_enabled
      The following service(s) are not started at boot time:
        ntpd, messagebus, openshift-watchman
      Unless you know they are not needed, please ensure that they start at boot.

WARN: test_system_config_firewall
         Using system-config-firewall and lokkit with OpenShift is not recommended.
         To continue using lokkit please ensure the following custom rules are 
         installed in /etc/sysconfig/system-config-firewall:

         --custom-rules=ipv4:filter:/etc/openshift/system-config-firewall-compat
         --custom-rules=ipv4:filter:/etc/openshift/iptables.filter.rules
         --custom-rules=ipv4:nat:/etc/openshift/iptables.nat.rules

4 WARNINGS
2 ERRORS

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