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

Re: Add node to district problem



Ignore what I said about version, my brain was elsewhere. But OS proved to be crucial! You're right, that cron job needs to account for the SCL-ization of mcollective under Enterprise Linux.

----- Original Message -----
From: "Marian Ignev" <m ignev gmail com>
To: "Brenton Leanhardt" <bleanhar redhat com>
Cc: "Luke Meyer" <lmeyer redhat com>, users lists openshift redhat com
Sent: Monday, November 4, 2013 8:17:52 AM
Subject: Re: Add node to district problem


Yeah .. got it .. 


This is the ouuput of the cron: 



[root node ~]# cat cron-m-output 
/var/tmp/scl9KsZFj: line 8: /usr/libexec/mcollective/update_yaml.rb: No such file or directory 
[root node ~]# 


I use Centos 6.4 as distro and as openshift version i use the nigthly repos ... so may be is 2.0 beta :) sorry i did not mention it! 


Now i change the path of the update_yaml.rb and everything works fine! 



#!/bin/bash 
rpm -q ruby193-mcollective &> /dev/null 
if [ $? -eq 0 ]; then 
YAML="/opt/rh/ruby193/root/etc/mcollective/facts.yaml" 
else 
YAML="/etc/mcollective/facts.yaml" 
fi 
oo-exec-ruby /opt/rh/ruby193/root/usr/libexec/mcollective/update_yaml.rb $YAML &> /dev/null 


Поздрави, 
Мариан Игнев 

--- 
www: http://m.ignev.net/ 
twitter: @mignev 





2013/11/4 Brenton Leanhardt < bleanhar redhat com > 


It would be also useful to know if you are running RHEL or Fedora. 
For RHEL the all configuration files will be relative to the SCL root 
(/opt/rh/ruby193/root/) 

--Brenton 

+++ Luke Meyer [04/11/13 07:44 -0500]: 




I take it you're working with the 2.0 beta? That would be good to mention :) 

selinux has been known to trip up the cron job. Can you try "setenforce 0" and see if the cron job now updates facts.yaml? 

If that is the problem, open a bug with the contents of /var/log/audit/audit.log because we need to make sure this works. 

If not, try removing the part of the cron job that sends the output > /dev/null and see if that gives you anything useful. 

----- Original Message ----- 
From: "Marian Ignev" < m ignev gmail com > 
To: "Luke Meyer" < lmeyer redhat com > 
Cc: users lists openshift redhat  com , "Steve Morrissey" < smorriss d umn edu > 
Sent: Monday, November 4, 2013 7:15:36 AM 
Subject: Re: Add node to district problem 


Yeah, 
i got that, but the cron doesnt work correctly and i dont know why ... and this acts me very confusing. 


I have already installed the package: 

[root node ~]# rpm -qa |grep 'openshift-origin-msg-node- mcollective' 
openshift-origin-msg-node- mcollective-1.16.1-1.git.25. 67d4311.el6.noarch 
[root node ~]# 


and the cron looks works: 



[root node ~]# tail -f /var/log/cron 
Nov 4 14:11:01 node CROND[11606]: (root) CMD (run-parts /etc/cron.minutely) 
Nov 4 14:11:01 node run-parts(/etc/cron.minutely)[ 11606]: starting openshift-facts 
Nov 4 14:11:01 node run-parts(/etc/cron.minutely)[ 11620]: finished openshift-facts 
Nov 4 14:11:01 node run-parts(/etc/cron.minutely)[ 11606]: starting openshift-origin-cron-minutely 
Nov 4 14:11:01 node run-parts(/etc/cron.minutely)[ 11645]: finished openshift-origin-cron-minutely 
Nov 4 14:12:01 node CROND[11779]: (root) CMD (run-parts /etc/cron.minutely) 
Nov 4 14:12:01 node run-parts(/etc/cron.minutely)[ 11779]: starting openshift-facts 
Nov 4 14:12:01 node run-parts(/etc/cron.minutely)[ 11793]: finished openshift-facts 
Nov 4 14:12:01 node run-parts(/etc/cron.minutely)[ 11779]: starting openshift-origin-cron-minutely 
Nov 4 14:12:01 node run-parts(/etc/cron.minutely)[ 11815]: finished openshift-origin-cron-minutely 
Nov 4 14:13:01 node CROND[11821]: (root) CMD (run-parts /etc/cron.minutely) 
Nov 4 14:13:01 node run-parts(/etc/cron.minutely)[ 11821]: starting openshift-facts 
Nov 4 14:13:01 node run-parts(/etc/cron.minutely)[ 11835]: finished openshift-facts 
Nov 4 14:13:01 node run-parts(/etc/cron.minutely)[ 11821]: starting openshift-origin-cron-minutely 
Nov 4 14:13:01 node run-parts(/etc/cron.minutely)[ 11857]: finished openshift-origin-cron-minutely 


But does not update the facts.yaml ... which is more confusing. 


Поздрави, 
Мариан Игнев 

--- 
www: http://m.ignev.net/ 
twitter: @mignev 





2013/11/4 Luke Meyer < lmeyer redhat com > 


That file is supposed to be populated by a cron job. Do you have the openshift-origin-msg-node- mcollective RPM installed on your node? It provides /etc/cron.minutely/openshift- facts which runs /usr/libexec/mcollective/ update_yaml.rb - and if that is not running, you will have bigger problems than not being able to district the node. You don't normally need to do anything manually here, but the docs mention it here: https://access.redhat.com/ site/documentation/en-US/ OpenShift_Enterprise/1/html- single/Deployment_Guide/index. html#Updating_the_Facter_ Database 

It may help you to run oo-diagnostics on all your hosts to see if it can find anything else wrong. 



----- Original Message ----- 
From: "Marian Ignev" < m ignev gmail com > 
To: "Steve Morrissey" < smorriss d umn edu > 
Cc: users lists openshift redhat  com 
Sent: Monday, November 4, 2013 3:12:34 AM 
Subject: Re: Add node to district problem 



Hi Steve, 
thank you very much! I just add the node_profile in the facts.yaml as you said and it's okay now! You save me a lot of time! I was started to debug the chain ... 


In the facts.yaml i had only this directive: 
mcollective: 1 


Can you give me some documentation link or article about this file, because i can't find. Thanks in advance :) 


Thanks once again. 


Поздрави, 
Мариан Игнев 

--- 
www: http://m.ignev.net/ 
twitter: @mignev 





2013/11/4 Steve Morrissey < smorriss d umn edu > 



Sorry for the list spam, I was doing too many things at the same time and didn't type the proper file path in my prior email. The facts.yaml file is located in /etc/mcollective/facts.yaml. Look at the node_profile, if it doesn't say small you might need to manually run the cron.minutely task that updates that file. 





On Sun, Nov 3, 2013 at 7:26 PM, Steve Morrissey < smorriss d umn edu > wrote: 



Hi Marian, 


What does your facts.yaml (in /etc/haproxy) file say for "node_profile"? 





On Sun, Nov 3, 2013 at 3:32 PM, Marian Ignev < m ignev gmail com > wrote: 








Hi guys! Before i describe what tortures me, i want to thank you for awesome job that are you doing, because openshift is awesome!!! So ... my problem ... As an noob who don't understand the whole system in details, i have the following situation. 


I try to add district for small gears with the command which i found in the admin guide: 


# oo-admin-ctl-district -c create -n small_district -p small 


Successfully created district: 513b50508f9f44aeb90090f19d2fd9 40 ... great! 


But when i try to add node to this distrcit with this line: 

oo-admin-ctl-district -c add-node -n small_district -i node.example.com 

This returns message: 


Node with server identity: node.example.com is of node profile '' and needs to be 'small' to add to district 'small_district' 


But on the node's resource_limits.conf node_profile directive is set: node_profile='small' 


Can you give me some advices, where i was wrong? 


Thanks in advance guys! You rockz! 

______________________________ _________________ 
users mailing list 
users lists openshift redhat  com 
http://lists.openshift.redhat. com/openshiftmm/listinfo/users 





-- 
Steve Morrissey 
Information Technology Systems & Services 
University of Minnesota Duluth 
o: 218.726.8866 



-- 
Steve Morrissey 
Information Technology Systems & Services 
University of Minnesota Duluth 
o: 218.726.8866 

______________________________ _________________ 
users mailing list 
users lists openshift redhat  com 
http://lists.openshift.redhat. com/openshiftmm/listinfo/users 


______________________________ _________________ 
users mailing list 
users lists openshift redhat  com 
http://lists.openshift.redhat. com/openshiftmm/listinfo/users 



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