Here's something I see in a lot of incidents: Nobody is an "expert" so nobody engages with the problem.
I'm not an expert on a lot of this stuff either, I just start opening log files and poking at shit until it giggles and rubs its tummy and stops giving 5xx errors.
Conversation
Notices
-
Embed this notice
SwiftOnSecurity (swiftonsecurity@infosec.exchange)'s status on Sunday, 09-Apr-2023 11:52:07 JST SwiftOnSecurity - Valerie Aurora repeated this.
-
Embed this notice
Kobold Curry Chef (koboldcurrychef@mstdn.social)'s status on Sunday, 09-Apr-2023 11:52:05 JST Kobold Curry Chef @SwiftOnSecurity The two things I always want my help desk and myself (IT Mgr) to remember:
1) CHECK THE CABLES
2) CHECK THE LOGFILES -
Embed this notice
Adriano (adriano@lile.cl)'s status on Sunday, 09-Apr-2023 12:37:20 JST Adriano @jab01701mid @SwiftOnSecurity stating only what you see and not what you believe is an art and takes years of practice
-
Embed this notice
John Breen (jab01701mid@universeodon.com)'s status on Sunday, 09-Apr-2023 12:37:21 JST John Breen @SwiftOnSecurity It's true. I will observe a corollary - often someone will claim they know what the problem must be, in a meeting of non-experts. Because they are seen as an expert, the momentum is hard to stop.
"Don't say you know, when you don't know" is the way I've heard it put...it wastes time...Jake Hildreth (acorn) :blacker_heart_outline: repeated this.