Manually updating a cluster.conf file - CentOS5 vs 6


If you want to do manual config changes/propagation (i.e. not using any GUI tools like Luci and system-config-cluster).  The reason why I don't want to use the GUI tools is this - I have NFS running as a cluster service with one client currently.  When I add two new clients and check the config file, there is a slight discrepancy - the original client setting is '1' while the new clients are set to 'on'.  The two new clients refuse to mount the NFS share stating 'access denied', except the are no /etc/exports files stating what clients can connect or not (or anything like that anywhere).  It's a long shot, but all I got!!  And I learned this, so not all is lost.

Note the key difference - one requires a cluster shutdown, the other does not.  If you were not aware, having a different config version number on nodes is BAD NEWS BEARS like whoa.  Basically causes nodes to start freaking out, getting fenced, etc.  It's messy.

On CentOS 5
  1. Shut down all cluster nodes.
  2. Edit config file on one node.
  3. SCP config file to other nodes.
  4. Start cluster.

On CentOS 6
  1. Edit cluster.conf, update config version number (+1) - note that you can only do specific things without having to restart entire cluster - see link: 8.4.1, step 6.
  2. ccs_config_validate - if okay, proceed.
  3. cman_tool version -r ### (updated version number here)
  4. Check other nodes for new config using cman_tool status, or cat /etc/cluster/cluster.conf | grep version.  All nodes should have same version #.

Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many of us work in seem to apply this as law - an
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible on
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99A
Read more