Please follow the below template, it will help us to help you!
Expected Behaviour:
This should complete and installation should continue:
Downloading and Installing FTL.../tmp/tmp.tlvwELuiKR /etc/.pihole
Actual Behaviour:
Machine freezes at full CPU utilization. Can no longer SSH into the machine, nor use tty for login.
Debug Token:
not available
Additional information:
Here is the installation log up until the point where the system freezes.
Additional clues:
The system is a ESXi 6.5 VM, 2GB RAM, 16GB HDD (i3-6100 CPU) which has ran Pihole with great success last year (using debian jessie). The system was left unused for a while until now, where it is dire time to do maintenance.
I've managed to bring Debian from 8.7 to date (apt-get update, apt-get upgrade) updated pihole successfully (pihole -up) to most current version.
Then I decided to jump to Debian 9.4 which also updated successfully. Pihole started to act up (loosing the graphs in the gui). Could not solved by (pihole -up).
Then loosing proper IPv4 in the webgui. Found this possibly due to a lack of consistency (likely user-inflicted during general late-night mayhem following general network problems) in DHCP vs static settings in the /etc/network/interfaces.
I uninstalled and attempted to reinstall pihole completely. This is where I am now. I cannot manage to get past the FTL download and installation.
The installer no longer hangs at the specific stage without any other intervention from me.
At around line 771, https://pastebin.com/7tSUrdnV you'll see the current progress.
Presently it is stuck at "pending..." for the s3.amazonaws.com (simple_ad.txt). (approx 30min)
I recognise this is a different error. What's the way to proceed, granted that I'm in the midst of a fresh install process?
cheers!
Oh man. I don't even ....
A couple of iterations later
I've come to realize every failed installation requires to reinvoke the old config file since the current /etc/lighttpd/lighttpd.conf gets blanked out, causing the lighttpd service to not load properly on reboot(after freeze), and in turn, cause all sorts of madness during the installation process.
Once lighttpd is in place, the installation has fighting chance to work.
I've right now gotten stuck at the same s3.amazonaws.com multiple times.