search

objective-see / BlockBlock

BlockBlock provides continual protection by monitoring persistence locations.
GNU General Public License v3.0
619 stars 38 forks source link

Could Not Connect To The BlockBlock Deamon 2.2.2 #75

Open iioniis opened 3 months ago

iioniis commented 3 months ago

"Could Not Connect To The BlockBlock Deamon Please ensure that the BlockBlock daemon is currently running."

Yes it's spelled wrong in the first line, no it was not spelled by me. I get this every launch with 2.2.2 on Monterey 12.7.4. I have to manually launch the helper and deselect the icon toggle to make it show up in the menu bar. BlockBlock always has full disk access. I even threw the helper in there to have full disk access and doesn't work.

objective-see commented 3 months ago

Sorry to hear about the issue 🫣

I've fixed the spelling already, but need some more information to help track down the more pressing communication issue.

Can you (please):

  1. Check to see if there any crash log/reports (via Console.app) ...maybe the daemon crashed?
  2. Run log show --predicate="subsystem='com.objective-see.blockblock'" from the Terminal to see if there are any error messages
  3. Run log stream --level debug --predicate="subsystem='com.objective-see.blockblock'" while manually (re)starting the helper to see if there are any error messages.

Thanks

iioniis commented 3 months ago

Ran both of those commands and have attached them here. There wasn't anything in the Console's crash report.

Terminal Saved Output.txt Terminal Saved Output2.txt

iCSpotRun commented 3 months ago

Do you have Little Snitch installed? Could be realted to this: https://github.com/objective-see/BlockBlock/issues/33

iioniis commented 3 months ago

I don't but I do have some Eclectic Light Company software installed. Skint, Silent Knight, Systhist and Lockrattler.

Edit: Update

So I went ahead and removed those apps and did a deep clean with Find Any File to finish the job. Did the same with BlockBlock, reinstalled, rebooted and all is well!

iioniis commented 3 months ago

Well, I guess that didn't work as when booting up just now, it's doing the same thing.

Spl0itable commented 2 months ago

Also having the same issue here. This machine is running with JAMF config and Falcon filters. Could that be contributing?