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
Uninstall, doesn't really uninstall. #2136
Comments
Thanks, the uninstaller needs a lot of work, the apt based packages are easy to remove as you know, but the custom scripting does need a lot more work and we need to make sure we get the sudoers.d remnants along with the sysv init scripts completely cleared. |
Could you provide information in the meantime how to uninstall manually? |
Yes please, I'm currently experiencing the same issue. |
This is currently affecting my system as well. I would love some manual uninstall instructions! |
same here
|
The main directories to remove are:
But the uninstall script is the source of truth in what should get uninstalled: |
This is still an issue 👎 |
We welcome any Pull Requests to help resolve open issues. |
Any idea why it fails? I experienced this as well, and dug through the script a little. It seems like it should work, but like others mine just stops in the middle. |
I had the same problem. In my case it was caused by the block checking for lighttpd. I did not install it. Maybe that causes the problem. I removed the code block and the uninstaller ran through. |
I've "debugged" the installation process a bit. The problem seems to be the function pi-hole/automated install/uninstall.sh Lines 59 to 61 in ba1e94d
Due to including the script file basic-install.sh here: pi-hole/automated install/uninstall.sh Line 41 in ba1e94d
which has an set -e
the uninstallation process terminates here. I would suggest using set +e and set -e inside the package_check method as a workaround.
|
I can confirm this. I had the same issue. Note: The first time the message "The following dependencies may have been added by the Pi-hole install: (...) Do you wish to go through each dependency for removal?" appeared, I cancelled the uninstaller and removed some of the packages on my own. I wanted to make sure that these packages are removed, even when I select "No". (It says: "Choosing No will leave all dependencies installed") This probably caused the issue in my case. |
@flori-uni |
It seems less files are left over now. I only have
I'm guessing it's safe to just delete these files? |
Yes, none of those files are created by us directly. |
Thanks, I've removed them now. :) |
This issue has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/why-do-speed-tests-no-longer-work/34795/13 |
I just installed and uninstalled pihole. During installation it added the dnstools package but dnstools isn't listed after "The following dependencies may have been added by the Pi-hole install:" during uninstall. |
Thanks for the report. |
In raising this issue, I confirm the following:
{please fill the checkboxes, e.g: [X]}
How familiar are you with the the source code relevant to this issue?:
10 it is a script...
https://github.com/pi-hole/pi-hole/blob/master/automated%20install/uninstall.sh
Expected behaviour:
Uninstall pihole (cleanly) I care about my dependencies. I run seafile and zoneminder on this pi, besides that's what the apt is for.
Actual behaviour:
Check for user account
FTL still running, SIGKILL sent
At this point I'm manually removing all the remaining artifacts.
After removing the services, init.d and /usr/bin
Steps to reproduce:
update / bash curl
uninstall
Debug token provided by uploading
pihole -d
log:I'll pass...
Troubleshooting undertaken, and/or other relevant information:
A friend of mine had an issue and lost sudo privileged on his pihole after running the update. We noticed the only user with sudo privledges was pihole. Tried uninstalling and it failes instantly. Went through his journal and didn't see any weird logins. Assuming his pi was compromised, for whatever reason, I checked mine. I updated just fine and decide to uninstall it and the user account, leading to a ton of artifacts. I went through the script and manually removed each of the remaining locations. It looks like the script is just bouncing out if it can't kill the service.
I would prefer to not reinstall at this time. I may install on another pi however I'll update if any definitive information is found.
The text was updated successfully, but these errors were encountered: