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

Raspbian Stretch Install Issue #208

Closed
thorrak opened this issue Oct 24, 2017 · 4 comments
Closed

Raspbian Stretch Install Issue #208

thorrak opened this issue Oct 24, 2017 · 4 comments
Assignees

Comments

@thorrak
Copy link
Owner

thorrak commented Oct 24, 2017

Amadio on HBT reported an issue installing under Raspbian Stretch:

I just got a new Pi 3, trying to install on the latest Raspbian (STRETCH LITE September 2017).

using the automated installer I see this error message during the install

[code]::: Copying nginx configuration to /etc/nginx and activating.
sed: can't read /home/fermentrack/fermentrack-tools/nginx-configs/default-fermentrack: No such file or directory
::: Running updateCronCircus.sh from the script repo
Checking and fixing cron entries for Fermentrack
::: Starting circus process monitor.
Starting Fermentrack supervisor: circusd: /home/fermentrack/fermentrack/utils/updateCronCircus.sh: line 36: /home/fermentrack/venv/bin/circusd: No such file or directory
failed, please see logfile.[/code]

there is no /home/fermentrack/fermentrack-tools/ directory, but there is a ~/fermentrack-tools directory

@stone
Copy link
Collaborator

stone commented Dec 18, 2017

I will have a look at this

@stone stone self-assigned this Dec 18, 2017
@stone
Copy link
Collaborator

stone commented Dec 18, 2017

My pi3 is not booting.. I have to come back to this when it's up and running again..

@thorrak
Copy link
Owner Author

thorrak commented Dec 18, 2017

Hey there! Cougar281 and I spent time researching this one on HBT - I think it’s pip’s fault.

@thorrak
Copy link
Owner Author

thorrak commented Feb 4, 2018

So I think this issue is resolved between two commits in Fermentrack tools.

The first commit added a script which forces reinstallation of pip within the virtualenv. This should hopefully fix any issues that

The second commit separately adds the '-H' flag to each call made via sudo <fermentrack user>. I think that some environments/installations do this by default, while in others this behavior isn't assumed. By forcing the -H flag the home directory is always redirected which is what we want in this case.

I'm actually guessing it's the second of these changes that is the more important one - but I'm leaving the first one (for now) as it doesn't seem to cause any issues elsewhere.

@thorrak thorrak closed this as completed Feb 4, 2018
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

2 participants