-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck on "Cleaning up DNS cache" #192
Comments
👋🏻 Thank you for your feedback, gonna watch it soon |
Hey 👋🏻 |
I reinstalled it, so I believe it is the latest version. |
DNS cleaning doesn't work in script:I can support @0xCarnival's problem, for me also it is stuck at DNS cleaning. Workaround:
Just add a # in front of those two lines. I know the script is not cleaning the DNS-Cache now but it executes fine after that. |
Thanks for the suggestion. I tried doing this and it didn't work.
Just to make sure, you are suggesting this quick fix for now:
def dns_cache():
with clc as unit:
unit.message("Cleaning up DNS cache")
#unit.add(Command("sudo dscacheutil -flushcache"))
#unit.add(Command("sudo killall -HUP mDNSResponder"))
It stucks on:
⠋ Cleaning up DNS cache ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0% -:--:--
0:00:00⠴ Cleaning up DNS cache ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0%
-:--:-- 0:02:03
…On Tue, Aug 13, 2024 at 3:25 PM Kim ***@***.***> wrote:
DNS cleaning doesn't work in script:
I can support @0xCarnival <https://github.com/0xCarnival>'s problem, for
me also it is stuck at DNS cleaning.
I used the commands of the script manually and they are working without
issue, something is not letting the python code move on..
Workaround:
1. Finder -> "Go to Folder.." open following path:
"/opt/homebrew/Cellar/mac-cleanup-py/3.0.4/libexec/lib/python3.10/site-packages/mac_cleanup"
2. Go into the file "default_modules.py"
3. Go to line 409
4. Comment out lines 412 and 413:
unit.add(Command("sudo dscacheutil -flushcache"))
unit.add(Command("sudo killall -HUP mDNSResponder"))
Just add a # in front of those two lines.
I know the script is not cleaning the DNS-Cache now but it executes fine
after that.
—
Reply to this email directly, view it on GitHub
<#192 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWRC6DZQQ3SDUTPJZ4PFOODZRG7JJAVCNFSM6AAAAABMIB5MMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBVGY3DAMZTG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
You have to close all terminals after editing, maybe even restart for all terminal sessions to restart. It didn't work for me either at first but after closing all terminals (or restarting) it should work fine. |
Unfortunately, I tried doing that, restarting, and it is still stuck in the
DNS part.
…On Tue, Aug 13, 2024 at 3:36 PM Kim ***@***.***> wrote:
You have to close all terminals after editing, maybe even restart for all
terminal sessions to restart. It didn't work for me either at first but
after closing all terminals (or restarting) it should work fine.
—
Reply to this email directly, view it on GitHub
<#192 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWRC6D7VBALAX3EGJHWSIMDZRHAQNAVCNFSM6AAAAABMIB5MMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBVGY4DCMJVGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@0xCarnival alright then I'm almost out of ideas. The only idea I have left is that you eventually have multiple versions installed. Like multiple homebrew versions or homebrew and PIP etc. For example you installed using PIP and homebrew but the PIP-one is executed but the homebrew one is modified (check that at least). |
Hey Kim,
All right, I did that. I in fact deleted both, and did a fresh
homebrew install.
Now it gets stuck at:
⠋ Purging inactive memory ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0% -:--:--
0:00:00⠋ Purging inactive memory ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0%
-:--:-- 0:19:19
…On Wed, Aug 14, 2024 at 12:02 PM Kim ***@***.***> wrote:
@0xCarnival <https://github.com/0xCarnival> alright then I'm almost out
of ideas.
The only idea I have left is that you eventually have multiple versions
installed. Like multiple homebrew versions or homebrew and PIP etc.
For example you installed using PIP and homebrew but the PIP-one is
executed but the homebrew one is modified (check that at least).
—
Reply to this email directly, view it on GitHub
<#192 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWRC6D4X5D4TERFL66DNH4TZRLQFXAVCNFSM6AAAAABMIB5MMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBXHA3DANJXHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@0xCarnival here I can just agree this freezes too. I can use the command in terminal but with the tool it doesn't work. You have to comment this out too (Line 419), those are things which need bugfixes.. maybe I find a way to do that. |
Just use the configure option So just do |
That worked, thank you!
…On Wed, Aug 14, 2024 at 9:31 PM Kim ***@***.***> wrote:
@ALL <https://github.com/ALL>
Just use the configure option -c to disable the two things instead of
changing the code.. I forgot that we can do that.
So just do mac-cleanup-py -c and deselect *memory* and *DNS* and it
should run trough.
—
Reply to this email directly, view it on GitHub
<#192 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWRC6D232W6VRACDGHFWO7LZRNS3NAVCNFSM6AAAAABMIB5MMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBYHE2DOOJRGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Please let the issue open tho, it's still a/multiple bug/s |
so I'm 100% sure sudo prompt is the culprit, but I'm not sure why: Can you specify the terminal emulator you use + the shell that is being used? |
I have the same issue. I use default terminal + zsh. I ran into this problem after I used it for a few months. |
Could you please try modifying your pam.d to accept touchId on sudo prompt? |
It works, thank you! |
It stuck on "Cleaning up DNS cache"
After running "mac-cleanup" from the terminal, it first cleans "homebrew", and then it stucks on "Cleaning up DNS cache".
The text was updated successfully, but these errors were encountered: