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.

Comments

  1. KeithJanuary 17, 2012 at 5:32 PM

    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 :)

    ReplyDelete
  2. Chris TrotterJanuary 18, 2012 at 6:08 AM

    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.

    ReplyDelete
  3. Chris TrotterJanuary 18, 2012 at 4:16 PM

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

    ReplyDelete
  4. AnittaJanuary 29, 2012 at 4:55 AM

    Title is odd ... deliberate or typo?

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

    ReplyDelete

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...
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...
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...
Read more