Inventor's Paradox

In this post I record steps that I took to debug some ruby code. Actually the code was an ruby mcollective server code that were installed as part of openshift origin Node. The bug is that the server consistently fails to respond to client queries in my configuration. I documented the steps taken  even though I hadn't nailed the bug yet. First thing first First we need to identify the entry point. These commands would do the trick: [root@broker ~]# service ruby193-mcollective status mcollectived (pid  1069) is running... [root@broker ~]# ps afxw | grep 1069  1069 ?        Sl     0:03 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 12428 pts/0    S+     0:00          \_ grep 1069 We found out that the service is : running with pid 1069 running with configuration file /opt/rh...

The Openshift Origin Comprehensive Installation Guideline (http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html) states that there is several things that can be done to ensure the Node is ready for integration into Openshift cluster : built-in script to check the node :  oo-accept-node check that facter runs properly : /etc/cron.minutely/openshift-facts check that mcollective communication works : in the broker, run : oo-mco ping  What I found that it is not enough. For example, openshift-facts show blanks, even though if there is an error with the facter functionality. So check the facter with : facter  And oo-mco ping works fine even though that there is something wrong with the rpc channel. I would suggest run these in the broker : oo-mco facts kernel oo-mco inventory In one of our Openshift Origin M4 cluster , I have these lines in /opt/rh/ruby193/root/etc/mcollective/server.cfg: main_collective = mcol...