Skip to content
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

installation error #9

Closed
technicalpyro opened this issue Feb 20, 2017 · 12 comments
Closed

installation error #9

technicalpyro opened this issue Feb 20, 2017 · 12 comments

Comments

@technicalpyro
Copy link
Contributor

to preface this i did not attempt this on a complete fresh install but you will see from the steps i think i did the correct sequence of commands

killed any existing pihole and pihole-FTL processes

rm -rf /etc/.pihole
git clone https://github.com/pi-hole/pi-hole.git /etc/.pihole/
cd /etc/.pihole/
git checkout new/FTL
rm -rf /var/html/admin/
gi clone https://github.com/pi-hole/AdminLTE.git
cd /var/html/admin/
git checkout new/FTL-nitegration
cd
pihole -r

got an error when it went to install (sorry should have taken a debug) that stated error of file not found and referred back to line 972 of the automated script

slept on it
did the same as the above the next morning but changed to using the new/FT:L-binary branch
once the script completed(successfully with no errors) i checked the web interface and saw FTL offline
i checked /etc/.pihole/ for a pihole-FTL executable ad saw none moved one from my testing directory started it and everything was working

@dschaper
Copy link
Member

Okay, working on updating the repo to pull down the precompiled binaries now, instead of needing to compile directly on the client. I'm writing the tests for that process now in the new/FTL-binary branch, but that's subject to breakage as I try different tests and tweak things.

@technicalpyro
Copy link
Contributor Author

am running pihole -r in that process posted above right now to see if it recreates the error if so i will make a debug

@technicalpyro
Copy link
Contributor Author

technicalpyro commented Feb 20, 2017

Compiling FTL... /etc/.pihole/automated install/basic-install.sh: line 972: cd: /etc/.pihole-FTL: No such file or directory
Debug
6o6a8z0e9j

my next attempt will be to run
git clone https://github.com/pi-hole/FTL.git /etc/.pihole-FTL/
and see if that resolves this

@dschaper
Copy link
Member

Ah, looks like the directory may not be created. Just a minute and I'll tweak that.

@dschaper
Copy link
Member

Okay, directory is created first. Try that again and see if it gets past the error at 972.

@technicalpyro
Copy link
Contributor Author

technicalpyro commented Feb 20, 2017

ok trying now
EDIT when i manually cloned the ftl repo into /etc/.pihole/ it did run correctly will wipe ad try with commands to be 100% sure

@technicalpyro
Copy link
Contributor Author

::: Compiling FTL... ::: Restarting services...
tried a couple times after removing both /etc.pihole/ and /etc/.pihole-FTL/
not sure if that is the expected result
and the web admin console shows FTL offline

@technicalpyro
Copy link
Contributor Author

technicalpyro commented Feb 20, 2017

perhaps the inelegant solution would be to have the basic installation script run the following command before attempting to compile
git clone https://github.com/pi-hole/FTL.git /etc/.pihole-FTL/

or assuming FTL will be an option (not sure the direction on this) when it is selected in the whiptail that clone runs first then it compiles

@dschaper
Copy link
Member

There wont be a need to copy the git repo, we compile the bits now and provide the precompiled binaries. Just need to finish testing the code that copies the release.

@technicalpyro
Copy link
Contributor Author

ahhh ok the other thing i just noticed is the script doesnt seem to start the FTL portion i had to start that manually

@technicalpyro
Copy link
Contributor Author

also the usual let me know if theres anything i can test here on my end i know im limited but happy to be helpful

@DL6ER
Copy link
Member

DL6ER commented Feb 20, 2017

That is very much appreciated. Let me close this issue since it is partially / mostly based on you working on an outdated code that is not maintained any longer (we don't compile on-the-fly anymore).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants