Description

Troubleshooting is much more than solving problems. True troubleshooting is digging into the issue until you identify the root cause of the issue. This week we dig deep into the art of troubleshooting and give you some practical tips and ticks you can use to troubleshoot your way out of any issue!

-- During The Show --

01:00 Digital Signage & CCTV - Matt

• Xibo
• Frigate

04:00 Rust Desk - Charlie

• Rust Desk
• Video on censortube
• Video Shownotes for docker install
• Rport
• Important to offer a paid "hosted" option

11:00 Camera/NVR Combo - Mike

• Chinese cameras bad
• Used Access Cameras
  • Might be missing peices
  • May need to be reset
  • May not have updates
• GeoVision
  • Stay away from GeoVision 360 Cameras
• Spork Syndrome
• Buy a Used Switch
• Synology + Survelance Station
• [Orchard NVR](ipconfigure.com)
• MotionEyeOS

21:20 Gadget of the Week

• Notkia Hackaday

24:00 News Wire

• JRC Disaster Relief Algorithm

  • JRC
  • Github

• Open Source USB Camera

  • DIY Photography
  • Circuit Valley

• MS Store Policy Changes

  • GHacks

• Mattermost 7

  • Venture Beat

• Grafana OnCall Open Source

  • Tech Crunch

• KDE Plasma 5.25

  • KDE

• Manjaro 21.3

  • Make Use Of

• Linux 5.17 EOL

  • 9 to 5 Linux

• Fish Shell 3.5

  • Fish Shell

• Ubuntu Core 22

  • Venture Beat

• Proton 7.0-3

  • Make Use Of

• Total War WARHAMMER III Ported to Linux

  • 9 to 5 Linux

• Travis CI Bug

  • Tech Monitor

• Linux Rootkit Syslogk

  • Tech Radar

• SSH Worm Panchan

  • Akamai

• New Linux Malware Symbiote

  • Threat Post

28:15 Technical Problem Solving

• Start with the end in mind
  • Define Success (Avoids Scope Creep)
  • Appropriate Response to scope creep
• Eliminate low hanging fruit first
  • Make sure things are up to date
  • Back tracing (try earlier versions)
  • Nuke and Pave
  • Keunwoo's Blog Post
• Start with what you know
  • Eliminate Variables
  • Simplify or Isolate
  • Be Firm "We have to do this"
  • Minimize hardware and software configuration
  • Can the problem be reproduced on single and/or multiple systems
• Root Cause Analasys
  • What is the cause
  • Is it correctly fixed
• Three main Root Causes
  • Physical
  • Human Error
  • Organizational
• Problem Solving Steps
  • 1 Define the Problem
  • 2 Gather Data
  • 3 Identify Causal Factors
  • 4 Determine Root Cause for each factor
  • 5 Implement Solutions
• Documentation
  • Start with existing documentation
  • Document and share trouble shooting steps
  • Document the solution (no magic configs)
  • Share the solution
• Effective Bug Reporting
  • A HUMAN IS ON THE OTHER SIDE OF YOUR BUG REPORT!!!
  • Title/Bug ID/Reference Point
  • Environment details
  • Steps to reproduce a bug
  • Expected result
  • Actual result
  • Visual Proof (Screenshot/Video/Logs)
  • Severity/Priority
• Resolution / Presentation
  • Review the end goal
  • Work around or fix
  • Escalated/Filled Bug Report

-- The Extra Credit Section --

For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard!

This Episode's Podcast Dashboard

Phone Systems for Ask Noah provided by Voxtelesys

Join us in our dedicated chatroom #GeekLab:linuxdelta.com on Matrix

-- Stay In Touch --

Find all the resources for this show on the Ask Noah Dashboard

Ask Noah Dashboard

Need more help than a radio show can offer? Altispeed provides commercial IT services and they’re excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show!

Altispeed Technologies

Contact Noah

live [at] asknoahshow.com

-- Twitter --

• Noah - Kernellinux
• Ask Noah Show
• Altispeed Technologies

Special Guests: JT Pennington and Steve Ovens.