From c20fa16c036997c3058b6f9845ba585a84cdf508 Mon Sep 17 00:00:00 2001 From: Marcus Del Greco Date: Wed, 17 Apr 2024 14:57:27 -0400 Subject: [PATCH] Update not-yet-2024-04-17.md --- _posts/not-yet-2024-04-17.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/_posts/not-yet-2024-04-17.md b/_posts/not-yet-2024-04-17.md index e3252ae..144c153 100644 --- a/_posts/not-yet-2024-04-17.md +++ b/_posts/not-yet-2024-04-17.md @@ -4,10 +4,18 @@ Recently, I stood up a simple JSON web service on Apache in my usual way, the ba The calls from the commerical system hung. And hung. And finally timed out. +Friends, your author gets perplexed more easily than you might suspect. When a certain approach works, and works, and continues to work some two decades or more running... the mind grows lazy. Happy experience creates a box diffcult to think outside of. + +Inside this mental box, I couldn't believe these client calls were even making it to my server. What's a hang? It's the network, of course. It's always the network, when things are hanging. Right? + +After careful research (okay fine, after a conversation with chatGPT and various AIs) I arrived at the following effective `tcpdump` command with human readable output, and I was able to see... + ``` sudo tcpdump -i [network interface] -n -t -vv -X -A src [IP address] ``` --- intr0 -- +... that I was wrong (gasp!): the client call *was* making it to my server, but something *else* had to be hanging things up. + +