How many people still believe the "cloud" was worth it? Maybe we should go back to the days of buying software and running it ourselves with our own infrastructure.
I know, I'm dreaming.
CrowdStrike Update: Windows Bluescreen and Boot Loops
251–260 of 1001 posts
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#252Can someone explain what Crowdstrike actually is? Reading Wikipedia it seems to be some sort of anti-virus software?
[deleted]
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#253They all should have used some expensive corporate-and-government-level product that promises protection against exactly that kind of large scale attack on infrastructure.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#254The details (the particular companies / systems etc) of this global incident don't really matter. When the entire society and economy are being digitized AND that digitisation is controlled and passes through a handful of choke points its an invitation to major disaster. It is risk management 101, never put all your digital eggs in one (or even a few) baskets. The love affair with oligopoly, cornered markets and powe…
Society was able to move to mass WFH on a global scale in a single month during Covid, thanks to the highly centralized and efficient cloud infrastructure. That could have easily saved tens of millions of lives (Imagine the Spanish flu with mass air travel, no vaccines, no strain-weakening)
These small 'downages' basically never cause serious issue. Your solutions are just alarmist and extremely costly (though they will provide developer employment...).
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#255We are a major CS client, with 50k windows-based endpoints or so. All down. There exists a workaround but CS does not make it clear whether this means running without protection or not. (The workaround does get the windows boxes unstuck from the boot loop, but they do appear offline in the CS host management console - which of course may have many reasons).
Wow that's terrible. I'm curious as to whether your contract with them allows for meaningful compensation in an event like this or is it just limited to the price of the software?
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#256That piece of "AV software" slowed down my brand new corporate i7 Lenovo to shit so I switched to M2 Pro. Best decision ever.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#257This was apparently caused by a faulty "channel file"[0], which is presumably some kind of configuration database that the software uses to identify malware.
So there wasn't any new kernel driver deployed, the existing kernel driver just doesn't fail gracefully.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#258The impact of this will be profound! Obviously bugs are inevitable, but why this wasn't progressively rolled out is beyond me.
Yeah, progressive rollout would have dramatically reduced the impact, I think that should be mandatory for any of these systems.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#259The details (the particular companies / systems etc) of this global incident don't really matter. When the entire society and economy are being digitized AND that digitisation is controlled and passes through a handful of choke points its an invitation to major disaster. It is risk management 101, never put all your digital eggs in one (or even a few) baskets. The love affair with oligopoly, cornered markets and powe…
Be aware that enterprise firms actively choose and "asses" who their AV suppliers are on-premis and in the cloud not imposed by msft. Googling it does seem that CrowdStrike, does have a history of Kernel Panics. Perhaps such interesting things as Kernel panic should be part of compliance checklist.
Googling it seems crowdstrike has a history of causing kernel panics.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#260Throwaway account... CrowdStrike in this context is a NT kernel loadable module (a .sys file) which does syscall level interception and logs then to a separate process on the machine. It can also STOP syscalls from working if they are trying to connect out to other nodes and accessing files they shouldn't be (using some drunk ass heuristics). What happened here was they pushed a new kernel driver out to every client…
> give clients control over this but they pissed over everyone's staging and rules and just pushed this to production.
Interesting..
> We have to literally take each node down, attach the disk to a working node..
Probably the easiest solution for you is to go back in time to a previous scheduled snapshot, if you have that setup already.