Skip to main content

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 #.


Popular posts from this blog

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 configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally 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$\\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-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…