A message comes in: a website is not responding.
Uncategorized
9
Posts
7
Posters
14
Views
-
A message comes in: a website is not responding. Or rather, it responds but it crawls.
It is a WordPress with a few plugins, all in good shape.I log in and the load is near zero, traffic is tiny. I start digging and nothing makes sense. I run the command "w" and the machine is frozen.
Nothing in the logs.
Then the light bulb goes on:
"ping bsd.cafe"No resolution.
The provider’s upstream DNS servers (set in a hurry, I normally install a local unbound) are not responding and everything grinds to a halt. I switch the DNS servers and everything magically starts working again.
Of course it was DNS! 🙂
-
A message comes in: a website is not responding. Or rather, it responds but it crawls.
It is a WordPress with a few plugins, all in good shape.I log in and the load is near zero, traffic is tiny. I start digging and nothing makes sense. I run the command "w" and the machine is frozen.
Nothing in the logs.
Then the light bulb goes on:
"ping bsd.cafe"No resolution.
The provider’s upstream DNS servers (set in a hurry, I normally install a local unbound) are not responding and everything grinds to a halt. I switch the DNS servers and everything magically starts working again.
Of course it was DNS! 🙂
This post is deleted! -
A message comes in: a website is not responding. Or rather, it responds but it crawls.
It is a WordPress with a few plugins, all in good shape.I log in and the load is near zero, traffic is tiny. I start digging and nothing makes sense. I run the command "w" and the machine is frozen.
Nothing in the logs.
Then the light bulb goes on:
"ping bsd.cafe"No resolution.
The provider’s upstream DNS servers (set in a hurry, I normally install a local unbound) are not responding and everything grinds to a halt. I switch the DNS servers and everything magically starts working again.
Of course it was DNS! 🙂
@stefano if the system is so heavily dependent on the DNS resolver ("frozen"), I would dig deeper, as there could be much more to it
-
@stefano if the system is so heavily dependent on the DNS resolver ("frozen"), I would dig deeper, as there could be much more to it
@winfried the "w" command will, by default, try to resolve the ip addresses into hostnames - that's why it is slow if the resolver isn't responding properly.
As for Wordpress - many of the plugins they are currently using depend on external calls. -
A message comes in: a website is not responding. Or rather, it responds but it crawls.
It is a WordPress with a few plugins, all in good shape.I log in and the load is near zero, traffic is tiny. I start digging and nothing makes sense. I run the command "w" and the machine is frozen.
Nothing in the logs.
Then the light bulb goes on:
"ping bsd.cafe"No resolution.
The provider’s upstream DNS servers (set in a hurry, I normally install a local unbound) are not responding and everything grinds to a halt. I switch the DNS servers and everything magically starts working again.
Of course it was DNS! 🙂
@stefano "We need more pow ... DNS!!!!!" 😂
-
undefined oblomov@sociale.network shared this topic on
-
A message comes in: a website is not responding. Or rather, it responds but it crawls.
It is a WordPress with a few plugins, all in good shape.I log in and the load is near zero, traffic is tiny. I start digging and nothing makes sense. I run the command "w" and the machine is frozen.
Nothing in the logs.
Then the light bulb goes on:
"ping bsd.cafe"No resolution.
The provider’s upstream DNS servers (set in a hurry, I normally install a local unbound) are not responding and everything grinds to a halt. I switch the DNS servers and everything magically starts working again.
Of course it was DNS! 🙂
@stefano "It's always DNS" - or rather, a lack there of ;)
-
A message comes in: a website is not responding. Or rather, it responds but it crawls.
It is a WordPress with a few plugins, all in good shape.I log in and the load is near zero, traffic is tiny. I start digging and nothing makes sense. I run the command "w" and the machine is frozen.
Nothing in the logs.
Then the light bulb goes on:
"ping bsd.cafe"No resolution.
The provider’s upstream DNS servers (set in a hurry, I normally install a local unbound) are not responding and everything grinds to a halt. I switch the DNS servers and everything magically starts working again.
Of course it was DNS! 🙂
-
-
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Oh, no, a guy who drank unboiled, untreated, water is having urgent stomach distress. Who could have predicted this?
-
Dustin's a sweetheart, worrying about whether the other guys got their shelters up.
-
OK, Wayne had a real bear scare. I reckon he's justified in bailing out.
Sam's looking awful cozy, though.
-
Ah, hell, his name is Joe. But, dude, you had a fire going when you lost the fire starter. Just keep it going forever. Where else you gotta be that you can't put a log on the fire every couple hours? Night time is a challenge, but if you keep it reasonably dry, you can stoke it back to life again in the morning.
-
Doomed by misplacing the fire starter is relatable. I would definitely lose something vitally important to my survival immediately.
-
Maybe they've saved the competent folks for later. Two guys have boiled water in episode 2, including the "better float across this water on a rickety tarp raft".
This guy eating a banana slug, a notorious carrier of rat lung worm, seems like an avoidable risk? At least he thoroughly cooked it.
-
Thanks, all. I'd say No.
-
I mean, I guess it's saltwater. But, I think they're in a rainforest? They said this place gets 12+ feet of rain every year.
But, they're seemingly all drinking collected water without boiling or treating it. These folks are not gonna last long.
