Skip to main content

Troubleshooting requires...

In my humble opinion, troubleshooting requires fundamental knowledge, persistence, patience, attention to detail, and a willingness to learn continuously.

My Father-in-Law passed away this past week.  After the funeral, we came back to the house to spend time together. That evening, everything in the Family Room connected to electricity started acting very weird. Lights flickering, TV going on and off, etc.  Honestly, my first thought was his ghost had come back to haunt us. 

Then, we began to smell the odor of something electrical going bad.

Let the troubleshooting begin!  

After unplugging everything, I inspected each outlet.

The last outlet I checked behind a bookcase and one that we never use looked liked this...

The discoloration on the face of the outlet is what caught my eye. 
The picture above is after I removed the cover plate and pulled it from the wall. Don't forget to switch off the correct circuit breaker before doing any of this type of work! 

After fully removing it, I found the full extent of the damage.

Somehow, one black wire came loose on this outlet and it started arcing.

It only cost a $1.15 to repair but it took a couple of iterations of rewiring and re-installing before it started working again.  I broke one of the black wires after the first attempt while pushing it back into the box in the wall. So, that is when the patience and persistence came into play.

Attention to detail and my fundamental knowledge of electricity is the main reason I found the problem. (Thank you, United States Air Force.)

While doing the repair, I learned how multiple outlets are wired together.

The point of this post is that troubleshooting skills are transferable across many situations. I've used my skills to do database administration, aircraft maintenance and fix things at home.

My troubleshooting skills saved a call to an electrician and the TV in the Family Room is ready for the Super Bowl. They've also helped avoid much grief at the day job. ;-)


Popular posts from this blog

Modifying Endpoint URLs on Availability Group Replicas

I recently had to modify the Endpoint URLs on our SQL Server Availability Group replicas.  The reason for this blog post is that I could not answer the following questions: Do I need to suspend data movement prior to making this change?  Would this change require a restart of the database instance? I spent enough time searching on my own to no avail that I tossed the question to the #sqlhelp hashtag on Twitter and Slack but didn't get an answer prior to executing the change request. After reading the relevant documentation, I think it's probably a good idea to suspend data movement for this change. The T-SQL is straightforward.  USE MASTER GO ALTER AVAILABILITY GROUP [AG1]  MODIFY REPLICA ON 'SQL2012-1' WITH (ENDPOINT_URL = 'TCP://'); ALTER AVAILABILITY GROUP [AG1]  MODIFY REPLICA ON 'SQL2012-2' WITH (ENDPOINT_URL = 'TCP://'); ALTER AVAILABILITY GROUP [AG2]  MODIFY REPLICA ON 'SQL2012-1

Set Azure App Service Platform Configuration to 64 bit.

If you need to update several Azure App Services' Configuration to change the Platform setting from 32 bit to 64 bit under Configuration | General settings, this script will save you about six clicks per service and you won't forget to press the SAVE button. Ask me I know. 🙄 Login-AzureRmAccount Set-AzureRmContext  -SubscriptionName  "Your Subscription" $ResourceGroupName  =  'RG1' ,  'RG2', 'RG3' foreach  ( $g   in   $ResourceGroupName ) {       # Set PROD slot to use 64 bit Platform Setting      Get-AzureRmWebApp  -ResourceGroupName  $g  | Select Name |  %  {  Set-AzureRmWebApp  -ResourceGroupName  $g  -Name  $_ .Name  -Use32BitWorkerProcess  $false  }       # Set staging slot to use 64 bit Platform setting      Get-AzureRmWebApp  -ResourceGroupName  $g  | Select Name |  %  {  Set-AzureRmWebAppSlot  -ResourceGroupName  $g  -Name  $_ .Name  -Slot  "staging"  -Use32BitWorkerProcess  $false  }  }

AzureRM Templates 101

I've recently started working with AzureRM templates to build new environments. This document really helped me understand the template structure when I first started looking at them. I love examples when I'm trying to learn something new and the Quick Start templates are the mother lode. Our goal is to incorporate our templates into an Azure Blueprint so that we can quickly build new environments when needed.  AzureRM templates can be artifacts of a blueprint.