Skip to main content

I accidentally the config file

Yes, today is the day that I made a fine boo-boo.  A shameful one, to be honest.

I was deploying config files for the monitoring software and got lazy - I overwrote files instead of moving them or renaming them...all because I wanted to get that last little bit done before I left for the day.

Of course it turns out that some esoteric command was in the files.  Not mission-critical, but I'll be spending time in the backup software tomorrow (assuming the servers were ever backed up) trying to figure it out.  Or re-writing the command from scratch.  Ouch.

The amount of time it will take to rename the files versus restore from backup can be described in orders of magnitude.  Honest to goodness - at least this project is almost over.

Lesson:  Even if you are 100% certain you'll be okay overwriting a file - move or rename it for insurance, because restoring from backup is tedious and painful and sometimes an endeavour in panic.  

Sub-lesson: Are you in a hurry to go somewhere?  Are you simultaneously working on production systems?  Just stop.  Stop right now.


  1. Bonus points for the sub-lesson. That's an important one to remember for sure! "Hurry" and "production systems" don't belong in the same thought :)

  2. Your sponsor for this update is 'Sub-lesson #2'!

    Sub-lesson #2: Talent can lead to laziness.

    Update: None of these servers were backed up. Sweet! Guess you'll see a nice blog entry on some Nagios commands soon.

  3. Okay, found an old config file that had enough in it to allow some reverse engineering. We good.

  4. Title is odd ... deliberate or typo?

    We learn by being taught but mistakes help the lesson stick.


Post a Comment

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…