Fermentrack Redis Docker??

[jeeppilot]

Okay so I haven’t brewed for about 6 months and had my Raspi powered down. Upon firing it up, and updating it as well as Fermentrack, I’m having multiple issues.

First, I can’t remote in as always have been able to. Checked ifconfig for the correct IP address and port forwarding and so on. I went through so many dead ends I went to try and reinstall Fermentrack only to get this: “ERROR: Port 6379 is required by Redis but is currently in use. Installation cannot continue.”

I have done all the get-apt update and upgrades, and those completed without issue. I don’t know where to go. Any thoughts? Thanks in advance! @Thorrak

 

[Thorrak]

Okay so I haven’t brewed for about 6 months and had my Raspi powered down. Upon firing it up, and updating it as well as Fermentrack, I’m having multiple issues.

First, I can’t remote in as always have been able to. Checked ifconfig for the correct IP address and port forwarding and so on. I went through so many dead ends I went to try and reinstall Fermentrack only to get this: “ERROR: Port 6379 is required by Redis but is currently in use. Installation cannot continue.”

I have done all the get-apt update and upgrades, and those completed without issue. I don’t know where to go. Any thoughts? Thanks in advance! @Thorrak

Which raspberry pi are you using? When you say you "can't remote in as you have always been able to do", what do you mean? Are you not able to SSH in, or just not access the Fermentrack webpage?

 

[jeeppilot]

Which raspberry pi are you using? When you say you "can't remote in as you have always been able to do", what do you mean? Are you not able to SSH in, or just not access the Fermentrack webpage?

It’s a Pi 3 B+ and I cannot access the Fermentrack webpage when connected to the home network using 192.168.1.xx or from outside my network.

 

[Thorrak]

It’s a Pi 3 B+ and I cannot access the Fermentrack webpage when connected to the home network using 192.168.1.xx or from outside my network.

Got it. Before we go too much further, do you have any data you want to save from your old Fermentrack install, or are you fine with wiping it out in favor of having fewer (potential) issues in the future?

No worries if it's the former - we can get you back up and running, it just changes the next steps

 

[jeeppilot]

I don’t have anything I need to back up. This stuff is not my strong suit so the less potential future issues, the better!

 

[Thorrak]

I don’t have anything I need to back up. This stuff is not my strong suit so the less potential future issues, the better!

Perfect. Try running the following two commands - you may need to restart the Pi once in between:

sudo apt-get remove -y redis-server curl -L install.fermentrack.com | bash

That should uninstall redis and then install the Docker-based version of Fermentrack (which will be much easier to maintain going forward!)

 

[jeeppilot]

Okay so the Redis uninstall appears to have gone okay. The Fermentrack reinstall did not. First, I tried the install command not as root (dropping “sudo” before bash) and it gave me an error code saying,

Checking internet connection:
/home/pi/fermentrack-tools/install.sh line 67 ./install.log Permission Denied
/home/pi/fermentrack-tools/install.sh line 102 ./install.log Permission Denied
ERROR could not connect to GitHub, are you sure you have a working internet
/home/pi/fermentrack-tools/install.sh line 79./install.log Permission Denied
ERROR connection? Install will exit: It needs to fetch code from GitHub.
/home/pi/fermentrack-tools/install.sh line 79./install.log Permission Denied

So I tried it using the root “sudo” command and I didn’t get the above errors, but did get the following:

ERROR: Version in “./docker-compose.yml is unsupported.....plus a bunch more talking about version 2.0 and possibly reverting to 1.0.

ERROR: Unable to find an initialized, responsive instance of Fermentrack

 

[matridium]

Okay so I haven’t brewed for about 6 months and had my Raspi powered down. Upon firing it up, and updating it as well as Fermentrack, I’m having multiple issues.

First, I can’t remote in as always have been able to. Checked ifconfig for the correct IP address and port forwarding and so on. I went through so many dead ends I went to try and reinstall Fermentrack only to get this: “ERROR: Port 6379 is required by Redis but is currently in use. Installation cannot continue.”

I have done all the get-apt update and upgrades, and those completed without issue. I don’t know where to go. Any thoughts? Thanks in advance! @Thorrak

Im in the same boat came back from a long break and now can't do anything, cant read the LCD and I tried a reinstall of the software and getting same issue as jeeppilot.

 

[matridium]

Im in the same boat came back from a long break and now can't do anything, cant read the LCD and I tried a reinstall of the so

Okay so the Redis uninstall appears to have gone okay. The Fermentrack reinstall did not. First, I tried the install command not as root (dropping “sudo” before bash) and it gave me an error code saying,

Checking internet connection:
/home/pi/fermentrack-tools/install.sh line 67 ./install.log Permission Denied
/home/pi/fermentrack-tools/install.sh line 102 ./install.log Permission Denied
ERROR could not connect to GitHub, are you sure you have a working internet
/home/pi/fermentrack-tools/install.sh line 79./install.log Permission Denied
ERROR connection? Install will exit: It needs to fetch code from GitHub.
/home/pi/fermentrack-tools/install.sh line 79./install.log Permission Denied

So I tried it using the root “sudo” command and I didn’t get the above errors, but did get the following:

ERROR: Version in “./docker-compose.yml is unsupported.....plus a bunch more talking about version 2.0 and possibly reverting to 1.0.

ERROR: Unable to find an initialized, responsive instance of Fermentrack

same thing for me too
ftware and getting same issue as jeeppilot.

so I followed the instructions to uninstall redis same issue for me too after installing fermentrack.

 

[Thorrak]

Okay so the Redis uninstall appears to have gone okay. The Fermentrack reinstall did not. First, I tried the install command not as root (dropping “sudo” before bash) and it gave me an error code saying,

Checking internet connection:
/home/pi/fermentrack-tools/install.sh line 67 ./install.log Permission Denied
/home/pi/fermentrack-tools/install.sh line 102 ./install.log Permission Denied
ERROR could not connect to GitHub, are you sure you have a working internet
/home/pi/fermentrack-tools/install.sh line 79./install.log Permission Denied
ERROR connection? Install will exit: It needs to fetch code from GitHub.
/home/pi/fermentrack-tools/install.sh line 79./install.log Permission Denied

So I tried it using the root “sudo” command and I didn’t get the above errors, but did get the following:

ERROR: Version in “./docker-compose.yml is unsupported.....plus a bunch more talking about version 2.0 and possibly reverting to 1.0.

ERROR: Unable to find an initialized, responsive instance of Fermentrack

Delete the fermentrack tools directory (you will need to use sudo rm -rf fermentrack-tools to do this), run the installation command again without sudo, and let me know exactly what errors you encounter. I don't recognize "ERROR: Version in “./docker-compose.yml is unsupported" unfortunately.

 

[Thorrak]

Im in the same boat came back from a long break and now can't do anything, cant read the LCD and I tried a reinstall of the software and getting same issue as jeeppilot.

Which errors exactly do you encounter?

 

[matridium]

Okay so the Redis uninstall appears to have gone okay. The Fermentrack reinstall did not. First, I tried the install command not as root (dropping “sudo” before bash) and it gave me an error code saying,

Checking internet connection:
/home/pi/fermentrack-tools/install.sh line 67 ./install.log Permission Denied
/home/pi/fermentrack-tools/install.sh line 102 ./install.log Permission Denied
ERROR could not connect to GitHub, are you sure you have a working internet
/home/pi/fermentrack-tools/install.sh line 79./install.log Permission Denied
ERROR connection? Install will exit: It needs to fetch code from GitHub.
/home/pi/fermentrack-tools/install.sh line 79./install.log Permission Denied

So I tried it using the root “sudo” command and I didn’t get the above errors, but did get the following:

ERROR: Version in “./docker-compose.yml is unsupported.....plus a bunch more talking about version 2.0 and possibly reverting to 1.0.

ERROR: Unable to find an initialized, responsive instance of Fermentrack

same for me too

Which errors exactly do you encounter?

same exact ones as listed above

 

[Thorrak]

same for me too

same exact ones as listed above

The command I provided in my response to @jeeppilot should resolve the specific errors he pasted here, but beyond that I can't help diagnose what is going on unless you copy and paste the exact error messages you're encountering.

 

[matridium]

pi@raspberrypi:~ $ sudo apt-get remove -y redis
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'redis' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
pi@raspberrypi:~ $ sudo apt-get remove -y redis-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'redis-server' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
pi@raspberrypi:~ $ sudo rm -rf fermentrack-tools
pi@raspberrypi:~ $ sudo apt-get remove -y redis-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'redis-server' is not installed, so not removed
^[[A^[[A0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
pi@raspberrypi:~ $ sudo apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
pi@raspberrypi:~ $ curl -L install.fermentrack.com | sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 123 100 123 0 0 588 0 --:--:-- --:--:-- --:--:-- 588
100 6918 100 6918 0 0 21155 0 --:--:-- --:--:-- --:--:-- 21155

<<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>>
:: Checking user
::: This script was launched as root. Although this used to be the recommended installation method,
::: installs now recommend being launched under the standard user (generally 'pi' for Raspberry Pi
::: installations). If you wish to cancel this installation and relaunch as a different user, press
::: Ctrl+C now. If you wish to continue to install as 'root' wait 10 seconds and the script will
::: continue.
:: Verifying free disk space...
::: Sufficent free space for installation
:: Installing dependencies using apt-get
::: installing git and build-essential.
::: (This may take a few minutes during which everything will be silent)
:::: All packages installed successfully.
:: Cloning fermentrack-tools repo from GitHub into /home/pi/fermentrack-tools
::: Repo was cloned successfully.
:: This script will now attempt to install Fermentrack using the script that has been created at
::: /home/pi/fermentrack-tools/install.sh
::: If the install script does not complete successfully, please relaunch the script above directly.
:::
:::: Launching Fermentrack installer.
::: Checking for Internet connection:
::: Internet connection Success!
::: Verifying free disk space...
::: Sufficient free disk space is available
::: Checking/installing Docker prerequisites using apt-get
::: Docker is already installed. Continuing.
::: Docker-compose is already installed. Continuing.
::: Script is run as root - no need to add to docker group.
::: Able to access docker - Proceeding.
::: The default port for Fermentrack to run on is port 80 (which is standard
::: for most websites). If you have another service currently running on port 80
::: then this install will likely fail unless another port is selected.

*** WARNING: Port 80 is currently in use.
::: You probably want to stop the installation here and either select a
::: new port or stop the service currently occupying port 80.
*** WARNING: Installation will continue with port 80 in 10 seconds unless you press Ctrl+C now.
*** ERROR: Port 6379 is required by Redis, but is currently in use. Installation cannot continue.

pi@raspberrypi:~ $ sudo lsof -i tcp:6379
lsof: no pwd entry for UID 999
lsof: no pwd entry for UID 999
lsof: no pwd entry for UID 999
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
python 693 fermentrack 3u IPv4 22157 0t0 TCP localhost:44876->localhost:6379 (ESTABLISHED)
python 693 fermentrack 4u IPv4 23375 0t0 TCP localhost:44878->localhost:6379 (ESTABLISHED)
lsof: no pwd entry for UID 999
redis-ser 1229 999 6u IPv4 22066 0t0 TCP localhost:6379 (LISTEN)
lsof: no pwd entry for UID 999
redis-ser 1229 999 7u IPv4 22158 0t0 TCP localhost:6379->localhost:44876 (ESTABLISHED)
lsof: no pwd entry for UID 999
redis-ser 1229 999 8u IPv4 22159 0t0 TCP localhost:6379->localhost:44878 (ESTABLISHED)

 

[Thorrak]

pi@raspberrypi:~ $ sudo apt-get remove -y redis
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'redis' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
pi@raspberrypi:~ $ sudo apt-get remove -y redis-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'redis-server' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
pi@raspberrypi:~ $ sudo rm -rf fermentrack-tools
pi@raspberrypi:~ $ sudo apt-get remove -y redis-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'redis-server' is not installed, so not removed
^[[A^[[A0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
pi@raspberrypi:~ $ sudo apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
pi@raspberrypi:~ $ curl -L install.fermentrack.com | sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 123 100 123 0 0 588 0 --:--:-- --:--:-- --:--:-- 588
100 6918 100 6918 0 0 21155 0 --:--:-- --:--:-- --:--:-- 21155

<<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>>
:: Checking user
::: This script was launched as root. Although this used to be the recommended installation method,
::: installs now recommend being launched under the standard user (generally 'pi' for Raspberry Pi
::: installations). If you wish to cancel this installation and relaunch as a different user, press
::: Ctrl+C now. If you wish to continue to install as 'root' wait 10 seconds and the script will
::: continue.
:: Verifying free disk space...
::: Sufficent free space for installation
:: Installing dependencies using apt-get
::: installing git and build-essential.
::: (This may take a few minutes during which everything will be silent)
:::: All packages installed successfully.
:: Cloning fermentrack-tools repo from GitHub into /home/pi/fermentrack-tools
::: Repo was cloned successfully.
:: This script will now attempt to install Fermentrack using the script that has been created at
::: /home/pi/fermentrack-tools/install.sh
::: If the install script does not complete successfully, please relaunch the script above directly.
:::
:::: Launching Fermentrack installer.
::: Checking for Internet connection:
::: Internet connection Success!
::: Verifying free disk space...
::: Sufficient free disk space is available
::: Checking/installing Docker prerequisites using apt-get
::: Docker is already installed. Continuing.
::: Docker-compose is already installed. Continuing.
::: Script is run as root - no need to add to docker group.
::: Able to access docker - Proceeding.
::: The default port for Fermentrack to run on is port 80 (which is standard
::: for most websites). If you have another service currently running on port 80
::: then this install will likely fail unless another port is selected.

*** WARNING: Port 80 is currently in use.
::: You probably want to stop the installation here and either select a
::: new port or stop the service currently occupying port 80.
*** WARNING: Installation will continue with port 80 in 10 seconds unless you press Ctrl+C now.
*** ERROR: Port 6379 is required by Redis, but is currently in use. Installation cannot continue.

pi@raspberrypi:~ $ sudo lsof -i tcp:6379
lsof: no pwd entry for UID 999
lsof: no pwd entry for UID 999
lsof: no pwd entry for UID 999
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
python 693 fermentrack 3u IPv4 22157 0t0 TCP localhost:44876->localhost:6379 (ESTABLISHED)
python 693 fermentrack 4u IPv4 23375 0t0 TCP localhost:44878->localhost:6379 (ESTABLISHED)
lsof: no pwd entry for UID 999
redis-ser 1229 999 6u IPv4 22066 0t0 TCP localhost:6379 (LISTEN)
lsof: no pwd entry for UID 999
redis-ser 1229 999 7u IPv4 22158 0t0 TCP localhost:6379->localhost:44876 (ESTABLISHED)
lsof: no pwd entry for UID 999
redis-ser 1229 999 8u IPv4 22159 0t0 TCP localhost:6379->localhost:44878 (ESTABLISHED)

Thank you!

That is both helpful and quite frustrating, as I thought we had that issue resolved.

No matter - as a first step, do you mind restarting your Pi to see if that triggers the redis server service to shut down?

Assuming that doesn't fix it, can you try the following:

sudo apt-get purge --auto-remove redis-server
sudo service redis_version stop
sudo rm /usr/local/bin/redis-*
sudo rm -r /etc/redis/
sudo rm /var/log/redis_*
sudo rm -r /var/lib/redis/
sudo rm /etc/init.d/redis_*
sudo rm /var/run/redis_*

...and then re-run the Fermentrack install script?

 

[matridium]

Thank you!

That is both helpful and quite frustrating, as I thought we had that issue resolved.

No matter - as a first step, do you mind restarting your Pi to see if that triggers the redis server service to shut down?

Assuming that doesn't fix it, can you try the following:

sudo apt-get purge --auto-remove redis-server
sudo service redis_version stop
sudo rm /usr/local/bin/redis-*
sudo rm -r /etc/redis/
sudo rm /var/log/redis_*
sudo rm -r /var/lib/redis/
sudo rm /etc/init.d/redis_*
sudo rm /var/run/redis_*

...and then re-run the Fermentrack install script?

ok
so I restarted and that did not work.
I tried everything you told me to do in terminal
result same errors as before here is a list of whats using the port still.
i@raspberrypi:~ $ sudo lsof -i tcp:6379
lsof: no pwd entry for UID 999
lsof: no pwd entry for UID 999
lsof: no pwd entry for UID 999
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
python 664 fermentrack 3u IPv4 20353 0t0 TCP localhost:57776->localhost:6379 (ESTABLISHED)
python 664 fermentrack 4u IPv4 20354 0t0 TCP localhost:57778->localhost:6379 (ESTABLISHED)
lsof: no pwd entry for UID 999
redis-ser 1236 999 6u IPv4 21324 0t0 TCP localhost:6379 (LISTEN)
lsof: no pwd entry for UID 999
redis-ser 1236 999 7u IPv4 23151 0t0 TCP localhost:6379->localhost:57776 (ESTABLISHED)
lsof: no pwd entry for UID 999
redis-ser 1236 999 8u IPv4 23152 0t0 TCP localhost:6379->localhost:57778 (ESTABLISHED)

 

[jeeppilot]

No dice. Tried all the manual redis file/folder commands and it appears it was all deleted already. Restarted. Ran the install script WITHOUT sudo and got:

pi@brewpi:~ $ sudo rm -rf fermentrack-tools
pi@brewpi:~ $ curl -L install.fermentrack.com | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 123 100 123 0 0 486 0 --:--:-- --:--:-- --:--:-- 488
100 6918 100 6918 0 0 11765 0 --:--:-- --:--:-- --:--:-- 20963

<<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>>
:: Checking user
::: This script was called without root privileges, which is recommended. The script will, however,
::: need root privileges periodically in order to install certain packages. Please be ready to
::: enter your password if prompted to allow installation to continue.
:::
:: Verifying free disk space...
::: Sufficent free space for installation
:: Installing dependencies using apt-get
::: installing git and build-essential.
::: (This may take a few minutes during which everything will be silent)
:::: All packages installed successfully.
:: Cloning fermentrack-tools repo from GitHub into /home/pi/fermentrack-tools
::: Repo was cloned successfully.
:: This script will now attempt to install Fermentrack using the script that has been created at
::: /home/pi/fermentrack-tools/install.sh
::: If the install script does not complete successfully, please relaunch the script above directly.
:::
:::: Launching Fermentrack installer.
::: Checking for Internet connection:
::: Internet connection Success!
::: Verifying free disk space...
::: Sufficient free disk space is available
::: Checking/installing Docker prerequisites using apt-get
::: Docker is already installed. Continuing.
::: Docker-compose is already installed. Continuing.
::: Adding pi to the 'docker' group.
::: Able to access docker - Proceeding.
::: The default port for Fermentrack to run on is port 80 (which is standard
::: for most websites). If you have another service currently running on port 80
::: then this install will likely fail unless another port is selected.

*** WARNING: Port 80 is currently in use.
::: You probably want to stop the installation here and either select a
::: new port or stop the service currently occupying port 80.
*** WARNING: Installation will continue with port 80 in 10 seconds unless you press Ctrl+C now.
::: Downloading required files from GitHub for setup
::: Creating Fermentrack environment configuration at ./envs/django
::: Creating Fermentrack Postgres environment configuration at ./envs/postgres
::: Downloading, building, and starting Fermentrack containers
Using default tag: latest
latest: Pulling from jdbeeler/fermentrack
Digest: sha256:46c70ac5fea2b5e35d1a74bc71a2e42184217fc8aee05a25a9c9771863798100
Status: Image is up to date for jdbeeler/fermentrack:latest
docker.io/jdbeeler/fermentrack:latest
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see Compose file
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see Compose file
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see Compose file
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see Compose file
::: Waiting for Fermentrack install to initialize and become responsive.
::: Fermentrack may take up to 3 minutes to first boot as the database is being initialized.
..........................................................................................missing.
*** ERROR: Unable to find an initialized, responsive instance of Fermentrack
pi@brewpi:~ $

 

[Thorrak]

...
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
...

Progress! You've got a different issue than @matridium now, at least. Let's check what version of RPi OS, Docker, and Docker-compose you have. Can you run the following four commands and report back what your Pi says?

uname -a
cat /etc/os-release
docker-compose --version
docker --version

 

[Thorrak]

ok
so I restarted and that did not work.
I tried everything you told me to do in terminal
result same errors as before here is a list of whats using the port still.
i@raspberrypi:~ $ sudo lsof -i tcp:6379
lsof: no pwd entry for UID 999
lsof: no pwd entry for UID 999
lsof: no pwd entry for UID 999
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
python 664 fermentrack 3u IPv4 20353 0t0 TCP localhost:57776->localhost:6379 (ESTABLISHED)
python 664 fermentrack 4u IPv4 20354 0t0 TCP localhost:57778->localhost:6379 (ESTABLISHED)
lsof: no pwd entry for UID 999
redis-ser 1236 999 6u IPv4 21324 0t0 TCP localhost:6379 (LISTEN)
lsof: no pwd entry for UID 999
redis-ser 1236 999 7u IPv4 23151 0t0 TCP localhost:6379->localhost:57776 (ESTABLISHED)
lsof: no pwd entry for UID 999
redis-ser 1236 999 8u IPv4 23152 0t0 TCP localhost:6379->localhost:57778 (ESTABLISHED)

What do you get if you do ps -xauf ?

Redis-server shouldn't be able to launch now that you've run those earlier commands. The foresting from that ps command should show what redis's parent processes are.

 

[jeeppilot]

pi@brewpi:~ $ uname -a
Linux brewpi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
pi@brewpi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@brewpi:~ $ docker-compose --version
docker-compose version 1.8.0, build unknown
pi@brewpi:~ $ docker --version
Docker version 19.03.15, build 99e3ed8919
pi@brewpi:~ $

 

[Thorrak]

pi@brewpi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
...
pi@brewpi:~ $ docker-compose --version
docker-compose version 1.8.0, build unknown
pi@brewpi:~ $ docker --version
Docker version 19.03.15, build 99e3ed8919

You're running on Raspbian Stretch which appears to have an ancient version of docker/docker compose available. I was under the impression that using the "get docker" scripts would bring Stretch installations up to date, but it doesn't appear that it has in your case. Try running the following, and let's see if it gets any better:

First, run this to (hopefully) update Docker:

curl -fsSL get.docker.com -o get-docker.sh && sh get-docker.sh

(Note - the above command is going to spit out a bunch of text, don't worry about copying/pasting it back here)

Then run this again (and copy the result back here) to check what the script did:

docker --version

 

[jeeppilot]

I ran the above command and I'm pasting the result as it failed to update. Same version as previous, and the error message is at the end of this string.

pi@brewpi:~ $ curl -fsSL get.docker.com -o get-docker.sh && sh get-docker.sh
# Executing docker install script, commit: 7cae5f8b0decc17d6571f9f52eb840fbc13b2737
Warning: the "docker" command appears to already exist on this system.

If you already have Docker installed, this script can cause trouble, which is
why we're displaying this warning and provide the opportunity to cancel the
installation.

If you installed the current Docker package using this script and are using it
again to update Docker, you can safely ignore this message.

You may press Ctrl+C now to abort this script.
+ sleep 20
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
+ sudo -E sh -c curl -fsSL "https://download.docker.com/linux/raspbian/gpg" | apt-key add -qq - >/dev/null
Warning: apt-key output should not be parsed (stdout is not a terminal)
+ sudo -E sh -c echo "deb [arch=armhf] Index of linux/raspbian/ stretch stable" > /etc/apt/sources.list.d/docker.list
+ sudo -E sh -c apt-get update -qq >/dev/null
+ [ -n ]
+ sudo -E sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
+ [ -n 1 ]
+ sudo -E sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce-rootless-extras >/dev/null
E: Unable to locate package docker-ce-rootless-extras
pi@brewpi:~ $ docker --version
Docker version 19.03.15, build 99e3ed8919
pi@brewpi:~ $

 

[matridium]

What do you get if you do ps -xauf ?

Redis-server shouldn't be able to launch now that you've run those earlier commands. The foresting from that ps command should show what redis's parent processes are.

this is what I get
pi@raspberrypi:~ $ ps -xauf
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 2 0.0 0.0 0 0 ? S 22:00 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [rcu_gp]
root 4 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [rcu_par_gp
root 5 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/0:
root 6 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/0:
root 7 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/u8
root 8 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [mm_percpu_
root 9 0.0 0.0 0 0 ? S 22:00 0:00 \_ [rcu_tasks_
root 10 0.0 0.0 0 0 ? S 22:00 0:00 \_ [rcu_tasks_
root 11 0.2 0.0 0 0 ? S 22:00 0:00 \_ [ksoftirqd/
root 12 0.2 0.0 0 0 ? I 22:00 0:00 \_ [rcu_sched]
root 13 0.0 0.0 0 0 ? S 22:00 0:00 \_ [migration/
root 14 0.0 0.0 0 0 ? S 22:00 0:00 \_ [cpuhp/0]
root 15 0.0 0.0 0 0 ? S 22:00 0:00 \_ [cpuhp/1]
root 16 0.0 0.0 0 0 ? S 22:00 0:00 \_ [migration/
root 17 0.2 0.0 0 0 ? S 22:00 0:00 \_ [ksoftirqd/
root 18 0.2 0.0 0 0 ? I 22:00 0:00 \_ [kworker/1:
root 19 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/1:
root 20 0.0 0.0 0 0 ? S 22:00 0:00 \_ [cpuhp/2]
root 21 0.0 0.0 0 0 ? S 22:00 0:00 \_ [migration/
root 22 0.1 0.0 0 0 ? S 22:00 0:00 \_ [ksoftirqd/
root 23 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/2:
root 24 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/2:
root 25 0.0 0.0 0 0 ? S 22:00 0:00 \_ [cpuhp/3]
root 26 0.0 0.0 0 0 ? S 22:00 0:00 \_ [migration/
root 27 0.1 0.0 0 0 ? S 22:00 0:00 \_ [ksoftirqd/
root 28 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/3:
root 29 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/3:
root 30 0.0 0.0 0 0 ? S 22:00 0:00 \_ [kdevtmpfs]
root 31 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [netns]
root 32 0.4 0.0 0 0 ? I 22:00 0:00 \_ [kworker/0:
root 33 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/1:
root 34 0.1 0.0 0 0 ? I 22:00 0:00 \_ [kworker/2:
root 35 0.0 0.0 0 0 ? S 22:00 0:00 \_ [kauditd]
root 36 0.0 0.0 0 0 ? S 22:00 0:00 \_ [khungtaskd
root 37 0.0 0.0 0 0 ? S 22:00 0:00 \_ [oom_reaper
root 38 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [writeback]
root 39 0.0 0.0 0 0 ? S 22:00 0:00 \_ [kcompactd0
root 57 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kblockd]
root 58 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [blkcg_punt
root 59 0.0 0.0 0 0 ? S 22:00 0:00 \_ [watchdogd]
root 60 0.1 0.0 0 0 ? I 22:00 0:00 \_ [kworker/3:
root 61 0.2 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/3:
root 62 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [rpciod]
root 63 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/u9
root 64 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [xprtiod]
root 65 0.3 0.0 0 0 ? S 22:00 0:00 \_ [kswapd0]
root 66 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [nfsiod]
root 67 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [iscsi_eh]
root 68 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [iscsi_dest
root 69 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [dwc_otg]
root 70 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [DWC Notifi
root 71 0.2 0.0 0 0 ? I 22:00 0:00 \_ [kworker/1:
root 72 0.0 0.0 0 0 ? S< 22:00 0:00 \_ [vchiq-slot
root 73 0.0 0.0 0 0 ? S< 22:00 0:00 \_ [vchiq-recy
root 74 0.0 0.0 0 0 ? S< 22:00 0:00 \_ [vchiq-sync
root 75 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [zswap-shri
root 76 0.4 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 77 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmc_comple
root 78 0.4 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/1:
root 79 0.3 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/0:
root 80 0.0 0.0 0 0 ? S 22:01 0:00 \_ [jbd2/mmcbl
root 81 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [ext4-rsv-c
root 82 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/0:
root 83 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [ipv6_addrc
root 84 0.1 0.0 0 0 ? I 22:01 0:00 \_ [kworker/0:
root 85 0.1 0.0 0 0 ? I 22:01 0:00 \_ [kworker/u8
root 87 0.4 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/2:
root 102 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/2:
root 103 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/3:
root 108 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/1:
root 124 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/3:
root 140 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/u8
root 164 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/2:
root 167 0.0 0.0 0 0 ? S 22:01 0:00 \_ [vchiq-keep
root 171 0.0 0.0 0 0 ? S< 22:01 0:00 \_ [SMIO]
root 188 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmal-vchiq
root 189 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmal-vchiq
root 193 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmal-vchiq
root 195 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmal-vchiq
root 246 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [cfg80211]
root 253 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [brcmf_wq/m
root 254 0.0 0.0 0 0 ? S 22:01 0:00 \_ [brcmf_wdog
root 261 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/0:
root 284 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 541 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/u9
root 543 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/u9
root 570 0.0 0.0 0 0 ? S< 22:01 0:00 \_ [krfcommd]
root 1454 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1455 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1456 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1457 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1458 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1459 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1460 0.2 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1461 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1462 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1723 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/2:
root 2030 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2031 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2032 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2033 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2034 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2035 0.1 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2036 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2037 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 1 5.7 0.8 33852 8136 ? Ss 22:00 0:07 /sbin/init spla
root 112 0.8 0.7 33232 7072 ? Ss 22:01 0:01 /lib/systemd/sy
root 147 0.9 0.4 18536 4168 ? Ss 22:01 0:01 /lib/systemd/sy
systemd+ 319 0.3 0.5 22416 5412 ? Ssl 22:01 0:00 /lib/systemd/sy
root 356 0.1 0.3 25512 3028 ? Ssl 22:01 0:00 /usr/sbin/rsysl
nobody 360 0.0 0.2 4320 2020 ? Ss 22:01 0:00 /usr/sbin/thd -
root 364 0.2 0.6 13044 5892 ? Ss 22:01 0:00 /lib/systemd/sy
root 369 0.0 0.2 7948 2228 ? Ss 22:01 0:00 /usr/sbin/cron
message+ 373 0.6 0.3 6808 3780 ? Ss 22:01 0:00 /usr/bin/dbus-d
root 378 0.0 0.3 10744 3724 ? Ss 22:01 0:00 /sbin/wpa_suppl
avahi 382 0.1 0.3 5768 2940 ? Ss 22:01 0:00 avahi-daemon: r
avahi 422 0.0 0.0 5768 220 ? S 22:01 0:00 \_ avahi-daemo
root 384 0.5 0.9 63212 9128 ? Ssl 22:01 0:00 /usr/lib/udisks
root 395 0.0 0.0 3692 752 ? SNs 22:01 0:00 /usr/sbin/alsac
root 400 0.2 0.8 54648 7912 ? Ssl 22:01 0:00 /usr/sbin/Modem
root 408 0.0 0.0 27656 72 ? SLsl 22:01 0:00 /usr/sbin/rngd
root 440 0.0 0.1 2904 1680 ? Ss 22:01 0:00 /sbin/dhcpcd -q
root 474 0.1 0.6 37964 5776 ? Ssl 22:01 0:00 /usr/lib/policy
root 480 0.4 1.6 38720 15784 ? Ssl 22:01 0:00 /usr/bin/python
root 491 0.1 0.6 37504 5816 ? Ssl 22:01 0:00 /usr/sbin/light
root 513 2.4 5.3 235496 50764 tty7 Ssl+ 22:01 0:02 \_ /usr/lib/xo
root 681 0.0 0.6 29908 6184 ? Sl 22:01 0:00 \_ lightdm --s
pi 691 0.2 1.2 54460 11776 ? Ssl 22:01 0:00 \_ /usr/bi
pi 735 0.0 0.0 4520 288 ? Ss 22:01 0:00 \_ /us
pi 760 0.4 1.5 62608 14680 ? S 22:01 0:00 \_ ope
pi 769 0.0 1.1 47136 11016 ? Sl 22:01 0:00 \_ lxp
pi 770 2.2 2.9 148996 28176 ? Sl 22:01 0:02 \_ lxp
pi 2317 9.3 5.0 235384 47380 ? Sl 22:02 0:01 | lxt
pi 2347 1.0 0.3 8516 3592 pts/0 Ss 22:02 0:00 | bas
pi 2444 0.0 0.2 9944 2644 pts/0 R+ 22:03 0:00 | ps
pi 2318 9.7 4.9 235240 47184 ? Sl 22:02 0:01 | lxt
pi 2346 1.0 0.3 8516 3536 pts/1 Ss+ 22:02 0:00 | bas
pi 771 1.5 2.5 104584 24508 ? Sl 22:01 0:01 \_ pcm
root 495 1.6 3.9 963904 37044 ? Ssl 22:01 0:01 /usr/bin/contai
root 503 0.0 0.4 11004 3792 ? Ss 22:01 0:00 wpa_supplicant
root 514 0.0 0.2 5620 2464 tty1 Ss 22:01 0:00 /bin/login -f
pi 662 0.2 0.3 8492 3624 tty1 S+ 22:01 0:00 \_ -bash
root 526 26.8 1.2 186124 11740 ? Sl 22:01 0:30 /opt/teamviewer
root 542 0.0 0.0 2140 48 ? S 22:01 0:00 /usr/bin/hciatt
root 554 0.0 0.4 9808 4396 ? Ss 22:01 0:00 /usr/lib/blueto
root 557 0.0 0.1 50232 1264 ? Ss 22:01 0:00 nginx: master p
www-data 559 0.0 0.2 50392 2668 ? S 22:01 0:00 \_ nginx: work
www-data 560 0.0 0.2 50392 2668 ? S 22:01 0:00 \_ nginx: work
www-data 561 0.0 0.2 50392 2668 ? S 22:01 0:00 \_ nginx: work
www-data 562 0.0 0.2 50392 2668 ? S 22:01 0:00 \_ nginx: work
root 558 0.0 0.4 26708 4112 ? Ssl 22:01 0:00 /usr/bin/blueal
root 577 3.6 7.2 1019432 68860 ? Ssl 22:01 0:04 /usr/bin/docker
pi 583 1.1 0.7 14848 7412 ? Ss 22:01 0:01 /lib/systemd/sy
pi 584 0.0 0.1 16748 1660 ? S 22:01 0:00 \_ (sd-pam)
pi 699 0.1 0.3 6544 3532 ? Ss 22:01 0:00 \_ /usr/bin/db
pi 744 2.1 8.2 396968 77864 ? Sl 22:01 0:02 \_ /opt/teamvi
pi 747 0.0 0.6 43412 6184 ? Ssl 22:01 0:00 \_ /usr/lib/gv
pi 886 0.3 0.6 52984 6412 ? Sl 22:01 0:00 | \_ /usr/li
pi 752 0.0 0.5 54512 5216 ? Sl 22:01 0:00 \_ /usr/lib/gv
pi 816 1.4 1.0 79348 9952 ? Ssl 22:01 0:01 \_ /usr/lib/gv
pi 826 0.0 0.4 40104 4360 ? Ssl 22:01 0:00 \_ /usr/lib/gv
pi 830 0.0 0.7 56028 6860 ? Ssl 22:01 0:00 \_ /usr/lib/gv
pi 836 0.0 0.5 41696 4988 ? Ssl 22:01 0:00 \_ /usr/lib/gv
pi 842 0.0 0.4 40128 4648 ? Ssl 22:01 0:00 \_ /usr/lib/gv
ferment+ 676 2.5 1.7 46800 16392 ? Sl 22:01 0:02 /home/fermentra
ferment+ 702 3.6 3.7 46768 35184 ? Ss 22:01 0:03 \_ /home/ferme
ferment+ 708 3.4 3.7 46768 35172 ? Ss 22:01 0:03 \_ /home/ferme
ferment+ 709 5.8 5.1 83728 49188 ? Ssl 22:01 0:06 \_ /home/ferme
ferment+ 710 3.6 3.8 64348 36796 ? Ssl 22:01 0:03 \_ /home/ferme
ferment+ 712 6.3 2.0 46444 19092 ? Ssl 22:01 0:06 \_ /home/ferme
ferment+ 1122 4.6 4.1 58884 38876 ? Ssl 22:01 0:03 \_ python -um
ferment+ 2369 56.3 3.8 75068 36464 ? Ssl 22:03 0:03 \_ python -um
pi 778 0.0 0.0 4520 288 ? Ss 22:01 0:00 /usr/bin/ssh-ag
pi 785 0.0 0.4 40452 4616 ? Sl 22:01 0:00 /usr/lib/geoclu
pi 863 0.0 0.5 26444 5176 ? Sl 22:01 0:00 /usr/lib/menu-c
root 1147 0.0 0.6 802816 5904 ? Sl 22:01 0:00 /usr/bin/contai
999 1228 0.6 0.5 48300 5260 ? Ssl 22:01 0:00 \_ redis-serve
root 1154 0.0 0.7 802816 6768 ? Sl 22:01 0:00 /usr/bin/contai
999 1236 0.4 2.0 199068 19824 ? Ss 22:01 0:00 \_ postgres
999 1637 0.0 0.4 199068 3840 ? Ss 22:01 0:00 \_ postgre
999 1638 0.0 0.4 199068 4560 ? Ss 22:01 0:00 \_ postgre
999 1639 0.0 0.8 199068 7900 ? Ss 22:01 0:00 \_ postgre
999 1640 0.0 0.6 199484 5760 ? Ss 22:01 0:00 \_ postgre
999 1642 0.0 0.3 55928 3540 ? Ss 22:01 0:00 \_ postgre
999 1643 0.0 0.4 199344 4712 ? Ss 22:01 0:00 \_ postgre
root 2397 1.5 0.7 802688 6916 ? Sl 22:03 0:00 /usr/bin/contai
sshd 2422 2.5 0.2 4308 2140 ? Ss 22:03 0:00 \_ /bin/bash /
sshd 2440 63.0 1.6 19204 15240 ? R 22:03 0:01 \_ python
pi@raspberrypi:~ $


I should also add got this issue after I updated my pi because I was installing teamviewer.

 

[jeeppilot]

Interesting note...I also have been using TeamViewer and it no longer seems to communicate. It will connect, but I can no longer “do” anything using it. I did NOT try and update anything on TeamViewer in the last couple days though.

 

[Thorrak]

I ran the above command and I'm pasting the result as it failed to update. Same version as previous, and the error message is at the end of this string.

pi@brewpi:~ $ curl -fsSL get.docker.com -o get-docker.sh && sh get-docker.sh
# Executing docker install script, commit: 7cae5f8b0decc17d6571f9f52eb840fbc13b2737
Warning: the "docker" command appears to already exist on this system.

If you already have Docker installed, this script can cause trouble, which is
why we're displaying this warning and provide the opportunity to cancel the
installation.

If you installed the current Docker package using this script and are using it
again to update Docker, you can safely ignore this message.

You may press Ctrl+C now to abort this script.
+ sleep 20
+ sudo -E sh -c apt-get update -qq >/dev/null
+ sudo -E sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
+ sudo -E sh -c curl -fsSL "https://download.docker.com/linux/raspbian/gpg" | apt-key add -qq - >/dev/null
Warning: apt-key output should not be parsed (stdout is not a terminal)
+ sudo -E sh -c echo "deb [arch=armhf] Index of linux/raspbian/ stretch stable" > /etc/apt/sources.list.d/docker.list
+ sudo -E sh -c apt-get update -qq >/dev/null
+ [ -n ]
+ sudo -E sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
+ [ -n 1 ]
+ sudo -E sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce-rootless-extras >/dev/null
E: Unable to locate package docker-ce-rootless-extras
pi@brewpi:~ $ docker --version
Docker version 19.03.15, build 99e3ed8919
pi@brewpi:~ $

Well, shoot. That was a good thought, at least.

There's two ways to proceed from here:

Unfortunately, I don't have Raspbian Stretch installed on a Pi here, so I don't have a system I can easily test on, and I don't have any other ideas at the moment for how to get Docker updated. If you want to wait a bit, I can try to get a system set up this weekend and poke at it a bit to see if I can determine how to get Docker updated.

Alternatively, if you want, you can install the latest RPi OS and then just run the Fermentrack install command against it. I did this myself a few weeks ago without any issue, so you should be good-to-go. Not ideal, I recognize, but it's the fastest way to get you back up and running (and - benefit - into the Docker configuration which should be much easier to maintain going forward)

 

[Thorrak]

this is what I get
pi@raspberrypi:~ $ ps -xauf
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 2 0.0 0.0 0 0 ? S 22:00 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [rcu_gp]
root 4 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [rcu_par_gp
root 5 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/0:
root 6 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/0:
root 7 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/u8
root 8 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [mm_percpu_
root 9 0.0 0.0 0 0 ? S 22:00 0:00 \_ [rcu_tasks_
root 10 0.0 0.0 0 0 ? S 22:00 0:00 \_ [rcu_tasks_
root 11 0.2 0.0 0 0 ? S 22:00 0:00 \_ [ksoftirqd/
root 12 0.2 0.0 0 0 ? I 22:00 0:00 \_ [rcu_sched]
root 13 0.0 0.0 0 0 ? S 22:00 0:00 \_ [migration/
root 14 0.0 0.0 0 0 ? S 22:00 0:00 \_ [cpuhp/0]
root 15 0.0 0.0 0 0 ? S 22:00 0:00 \_ [cpuhp/1]
root 16 0.0 0.0 0 0 ? S 22:00 0:00 \_ [migration/
root 17 0.2 0.0 0 0 ? S 22:00 0:00 \_ [ksoftirqd/
root 18 0.2 0.0 0 0 ? I 22:00 0:00 \_ [kworker/1:
root 19 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/1:
root 20 0.0 0.0 0 0 ? S 22:00 0:00 \_ [cpuhp/2]
root 21 0.0 0.0 0 0 ? S 22:00 0:00 \_ [migration/
root 22 0.1 0.0 0 0 ? S 22:00 0:00 \_ [ksoftirqd/
root 23 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/2:
root 24 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/2:
root 25 0.0 0.0 0 0 ? S 22:00 0:00 \_ [cpuhp/3]
root 26 0.0 0.0 0 0 ? S 22:00 0:00 \_ [migration/
root 27 0.1 0.0 0 0 ? S 22:00 0:00 \_ [ksoftirqd/
root 28 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/3:
root 29 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/3:
root 30 0.0 0.0 0 0 ? S 22:00 0:00 \_ [kdevtmpfs]
root 31 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [netns]
root 32 0.4 0.0 0 0 ? I 22:00 0:00 \_ [kworker/0:
root 33 0.0 0.0 0 0 ? I 22:00 0:00 \_ [kworker/1:
root 34 0.1 0.0 0 0 ? I 22:00 0:00 \_ [kworker/2:
root 35 0.0 0.0 0 0 ? S 22:00 0:00 \_ [kauditd]
root 36 0.0 0.0 0 0 ? S 22:00 0:00 \_ [khungtaskd
root 37 0.0 0.0 0 0 ? S 22:00 0:00 \_ [oom_reaper
root 38 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [writeback]
root 39 0.0 0.0 0 0 ? S 22:00 0:00 \_ [kcompactd0
root 57 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kblockd]
root 58 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [blkcg_punt
root 59 0.0 0.0 0 0 ? S 22:00 0:00 \_ [watchdogd]
root 60 0.1 0.0 0 0 ? I 22:00 0:00 \_ [kworker/3:
root 61 0.2 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/3:
root 62 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [rpciod]
root 63 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [kworker/u9
root 64 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [xprtiod]
root 65 0.3 0.0 0 0 ? S 22:00 0:00 \_ [kswapd0]
root 66 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [nfsiod]
root 67 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [iscsi_eh]
root 68 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [iscsi_dest
root 69 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [dwc_otg]
root 70 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [DWC Notifi
root 71 0.2 0.0 0 0 ? I 22:00 0:00 \_ [kworker/1:
root 72 0.0 0.0 0 0 ? S< 22:00 0:00 \_ [vchiq-slot
root 73 0.0 0.0 0 0 ? S< 22:00 0:00 \_ [vchiq-recy
root 74 0.0 0.0 0 0 ? S< 22:00 0:00 \_ [vchiq-sync
root 75 0.0 0.0 0 0 ? I< 22:00 0:00 \_ [zswap-shri
root 76 0.4 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 77 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmc_comple
root 78 0.4 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/1:
root 79 0.3 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/0:
root 80 0.0 0.0 0 0 ? S 22:01 0:00 \_ [jbd2/mmcbl
root 81 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [ext4-rsv-c
root 82 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/0:
root 83 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [ipv6_addrc
root 84 0.1 0.0 0 0 ? I 22:01 0:00 \_ [kworker/0:
root 85 0.1 0.0 0 0 ? I 22:01 0:00 \_ [kworker/u8
root 87 0.4 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/2:
root 102 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/2:
root 103 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/3:
root 108 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/1:
root 124 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/3:
root 140 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/u8
root 164 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/2:
root 167 0.0 0.0 0 0 ? S 22:01 0:00 \_ [vchiq-keep
root 171 0.0 0.0 0 0 ? S< 22:01 0:00 \_ [SMIO]
root 188 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmal-vchiq
root 189 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmal-vchiq
root 193 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmal-vchiq
root 195 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [mmal-vchiq
root 246 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [cfg80211]
root 253 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [brcmf_wq/m
root 254 0.0 0.0 0 0 ? S 22:01 0:00 \_ [brcmf_wdog
root 261 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/0:
root 284 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 541 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/u9
root 543 0.0 0.0 0 0 ? I< 22:01 0:00 \_ [kworker/u9
root 570 0.0 0.0 0 0 ? S< 22:01 0:00 \_ [krfcommd]
root 1454 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1455 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1456 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1457 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1458 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1459 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1460 0.2 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1461 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1462 0.0 0.0 0 0 ? I 22:01 0:00 \_ [kworker/1:
root 1723 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/2:
root 2030 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2031 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2032 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2033 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2034 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2035 0.1 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2036 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 2037 0.0 0.0 0 0 ? I 22:02 0:00 \_ [kworker/0:
root 1 5.7 0.8 33852 8136 ? Ss 22:00 0:07 /sbin/init spla
root 112 0.8 0.7 33232 7072 ? Ss 22:01 0:01 /lib/systemd/sy
root 147 0.9 0.4 18536 4168 ? Ss 22:01 0:01 /lib/systemd/sy
systemd+ 319 0.3 0.5 22416 5412 ? Ssl 22:01 0:00 /lib/systemd/sy
root 356 0.1 0.3 25512 3028 ? Ssl 22:01 0:00 /usr/sbin/rsysl
nobody 360 0.0 0.2 4320 2020 ? Ss 22:01 0:00 /usr/sbin/thd -
root 364 0.2 0.6 13044 5892 ? Ss 22:01 0:00 /lib/systemd/sy
root 369 0.0 0.2 7948 2228 ? Ss 22:01 0:00 /usr/sbin/cron
message+ 373 0.6 0.3 6808 3780 ? Ss 22:01 0:00 /usr/bin/dbus-d
root 378 0.0 0.3 10744 3724 ? Ss 22:01 0:00 /sbin/wpa_suppl
avahi 382 0.1 0.3 5768 2940 ? Ss 22:01 0:00 avahi-daemon: r
avahi 422 0.0 0.0 5768 220 ? S 22:01 0:00 \_ avahi-daemo
root 384 0.5 0.9 63212 9128 ? Ssl 22:01 0:00 /usr/lib/udisks
root 395 0.0 0.0 3692 752 ? SNs 22:01 0:00 /usr/sbin/alsac
root 400 0.2 0.8 54648 7912 ? Ssl 22:01 0:00 /usr/sbin/Modem
root 408 0.0 0.0 27656 72 ? SLsl 22:01 0:00 /usr/sbin/rngd
root 440 0.0 0.1 2904 1680 ? Ss 22:01 0:00 /sbin/dhcpcd -q
root 474 0.1 0.6 37964 5776 ? Ssl 22:01 0:00 /usr/lib/policy
root 480 0.4 1.6 38720 15784 ? Ssl 22:01 0:00 /usr/bin/python
root 491 0.1 0.6 37504 5816 ? Ssl 22:01 0:00 /usr/sbin/light
root 513 2.4 5.3 235496 50764 tty7 Ssl+ 22:01 0:02 \_ /usr/lib/xo
root 681 0.0 0.6 29908 6184 ? Sl 22:01 0:00 \_ lightdm --s
pi 691 0.2 1.2 54460 11776 ? Ssl 22:01 0:00 \_ /usr/bi
pi 735 0.0 0.0 4520 288 ? Ss 22:01 0:00 \_ /us
pi 760 0.4 1.5 62608 14680 ? S 22:01 0:00 \_ ope
pi 769 0.0 1.1 47136 11016 ? Sl 22:01 0:00 \_ lxp
pi 770 2.2 2.9 148996 28176 ? Sl 22:01 0:02 \_ lxp
pi 2317 9.3 5.0 235384 47380 ? Sl 22:02 0:01 | lxt
pi 2347 1.0 0.3 8516 3592 pts/0 Ss 22:02 0:00 | bas
pi 2444 0.0 0.2 9944 2644 pts/0 R+ 22:03 0:00 | ps
pi 2318 9.7 4.9 235240 47184 ? Sl 22:02 0:01 | lxt
pi 2346 1.0 0.3 8516 3536 pts/1 Ss+ 22:02 0:00 | bas
pi 771 1.5 2.5 104584 24508 ? Sl 22:01 0:01 \_ pcm
root 495 1.6 3.9 963904 37044 ? Ssl 22:01 0:01 /usr/bin/contai
root 503 0.0 0.4 11004 3792 ? Ss 22:01 0:00 wpa_supplicant
root 514 0.0 0.2 5620 2464 tty1 Ss 22:01 0:00 /bin/login -f
pi 662 0.2 0.3 8492 3624 tty1 S+ 22:01 0:00 \_ -bash
root 526 26.8 1.2 186124 11740 ? Sl 22:01 0:30 /opt/teamviewer
root 542 0.0 0.0 2140 48 ? S 22:01 0:00 /usr/bin/hciatt
root 554 0.0 0.4 9808 4396 ? Ss 22:01 0:00 /usr/lib/blueto
root 557 0.0 0.1 50232 1264 ? Ss 22:01 0:00 nginx: master p
www-data 559 0.0 0.2 50392 2668 ? S 22:01 0:00 \_ nginx: work
www-data 560 0.0 0.2 50392 2668 ? S 22:01 0:00 \_ nginx: work
www-data 561 0.0 0.2 50392 2668 ? S 22:01 0:00 \_ nginx: work
www-data 562 0.0 0.2 50392 2668 ? S 22:01 0:00 \_ nginx: work
root 558 0.0 0.4 26708 4112 ? Ssl 22:01 0:00 /usr/bin/blueal
root 577 3.6 7.2 1019432 68860 ? Ssl 22:01 0:04 /usr/bin/docker
pi 583 1.1 0.7 14848 7412 ? Ss 22:01 0:01 /lib/systemd/sy
pi 584 0.0 0.1 16748 1660 ? S 22:01 0:00 \_ (sd-pam)
pi 699 0.1 0.3 6544 3532 ? Ss 22:01 0:00 \_ /usr/bin/db
pi 744 2.1 8.2 396968 77864 ? Sl 22:01 0:02 \_ /opt/teamvi
pi 747 0.0 0.6 43412 6184 ? Ssl 22:01 0:00 \_ /usr/lib/gv
pi 886 0.3 0.6 52984 6412 ? Sl 22:01 0:00 | \_ /usr/li
pi 752 0.0 0.5 54512 5216 ? Sl 22:01 0:00 \_ /usr/lib/gv
pi 816 1.4 1.0 79348 9952 ? Ssl 22:01 0:01 \_ /usr/lib/gv
pi 826 0.0 0.4 40104 4360 ? Ssl 22:01 0:00 \_ /usr/lib/gv
pi 830 0.0 0.7 56028 6860 ? Ssl 22:01 0:00 \_ /usr/lib/gv
pi 836 0.0 0.5 41696 4988 ? Ssl 22:01 0:00 \_ /usr/lib/gv
pi 842 0.0 0.4 40128 4648 ? Ssl 22:01 0:00 \_ /usr/lib/gv
ferment+ 676 2.5 1.7 46800 16392 ? Sl 22:01 0:02 /home/fermentra
ferment+ 702 3.6 3.7 46768 35184 ? Ss 22:01 0:03 \_ /home/ferme
ferment+ 708 3.4 3.7 46768 35172 ? Ss 22:01 0:03 \_ /home/ferme
ferment+ 709 5.8 5.1 83728 49188 ? Ssl 22:01 0:06 \_ /home/ferme
ferment+ 710 3.6 3.8 64348 36796 ? Ssl 22:01 0:03 \_ /home/ferme
ferment+ 712 6.3 2.0 46444 19092 ? Ssl 22:01 0:06 \_ /home/ferme
ferment+ 1122 4.6 4.1 58884 38876 ? Ssl 22:01 0:03 \_ python -um
ferment+ 2369 56.3 3.8 75068 36464 ? Ssl 22:03 0:03 \_ python -um
pi 778 0.0 0.0 4520 288 ? Ss 22:01 0:00 /usr/bin/ssh-ag
pi 785 0.0 0.4 40452 4616 ? Sl 22:01 0:00 /usr/lib/geoclu
pi 863 0.0 0.5 26444 5176 ? Sl 22:01 0:00 /usr/lib/menu-c
root 1147 0.0 0.6 802816 5904 ? Sl 22:01 0:00 /usr/bin/contai
999 1228 0.6 0.5 48300 5260 ? Ssl 22:01 0:00 \_ redis-serve
root 1154 0.0 0.7 802816 6768 ? Sl 22:01 0:00 /usr/bin/contai
999 1236 0.4 2.0 199068 19824 ? Ss 22:01 0:00 \_ postgres
999 1637 0.0 0.4 199068 3840 ? Ss 22:01 0:00 \_ postgre
999 1638 0.0 0.4 199068 4560 ? Ss 22:01 0:00 \_ postgre
999 1639 0.0 0.8 199068 7900 ? Ss 22:01 0:00 \_ postgre
999 1640 0.0 0.6 199484 5760 ? Ss 22:01 0:00 \_ postgre
999 1642 0.0 0.3 55928 3540 ? Ss 22:01 0:00 \_ postgre
999 1643 0.0 0.4 199344 4712 ? Ss 22:01 0:00 \_ postgre
root 2397 1.5 0.7 802688 6916 ? Sl 22:03 0:00 /usr/bin/contai
sshd 2422 2.5 0.2 4308 2140 ? Ss 22:03 0:00 \_ /bin/bash /
sshd 2440 63.0 1.6 19204 15240 ? R 22:03 0:01 \_ python
pi@raspberrypi:~ $


I should also add got this issue after I updated my pi because I was installing teamviewer.

Huh. Interestingly enough, that would almost seem to indicate that you have a working copy of Fermentrack installed/running. If you go to your fermentrack-tools directory and run docker-compose down what happens?

 

[matridium]

Huh. Interestingly enough, that would almost seem to indicate that you have a working copy of Fermentrack installed/running. If you go to your fermentrack-tools directory and run docker-compose down what happens?

pi@raspberrypi:~ $ cd fermentrack-tools
pi@raspberrypi:~/fermentrack-tools $ docker-compose down
ERROR:
Can't find a suitable configuration file in this directory or any
parent. Are you in the right directory?

Supported filenames: docker-compose.yml, docker-compose.yaml

pi@raspberrypi:~/fermentrack-tools $ dir
automated_install install.log sample.docker-compose.yml
docker-create-superuser.sh install.sh sample_envs
Dockerfile non_docker_install
docker-update.sh README.md

 

[jeeppilot]

Well, shoot. That was a good thought, at least.

There's two ways to proceed from here:

Unfortunately, I don't have Raspbian Stretch installed on a Pi here, so I don't have a system I can easily test on, and I don't have any other ideas at the moment for how to get Docker updated. If you want to wait a bit, I can try to get a system set up this weekend and poke at it a bit to see if I can determine how to get Docker updated.

Alternatively, if you want, you can install the latest RPi OS and then just run the Fermentrack install command against it. I did this myself a few weeks ago without any issue, so you should be good-to-go. Not ideal, I recognize, but it's the fastest way to get you back up and running (and - benefit - into the Docker configuration which should be much easier to maintain going forward)

I’m happy to update to the latest RPi OS. Is there a command I can run from the terminal to do this or do I have to download it to the USB card? Sorry for the NOOB questions, I just don’t know enough to do anything besides have my hand held through all this.

 

[Thorrak]

pi@raspberrypi:~ $ cd fermentrack-tools
pi@raspberrypi:~/fermentrack-tools $ docker-compose down
ERROR:
Can't find a suitable configuration file in this directory or any
parent. Are you in the right directory?

Supported filenames: docker-compose.yml, docker-compose.yaml

pi@raspberrypi:~/fermentrack-tools $ dir
automated_install install.log sample.docker-compose.yml
docker-create-superuser.sh install.sh sample_envs
Dockerfile non_docker_install
docker-update.sh README.md

...huh. That sounds like an oversight on my part. Give me a few minutes...

I’m happy to update to the latest RPi OS. Is there a command I can run from the terminal to do this or do I have to download it to the USB card? Sorry for the NOOB questions, I just don’t know enough to do anything besides have my hand held through all this.

No worries! Unfortunately, you'll need to download the OS and reflash it to the Micro SD card. You can find instructions (and a helpful app for doing the actual imaging) here: Raspberry Pi OS – Raspberry Pi

 

[matridium]

...huh. That sounds like an oversight on my part. Give me a few minutes...




No worries! Unfortunately, you'll need to download the OS and reflash it to the Micro SD card. You can find instructions (and a helpful app for doing the actual imaging) here: Raspberry Pi OS – Raspberry Pi

Seems to me fermentrack is actually installed but I cannot receive LCD readout or update and it can't connect to the controller. I have a fresh install of RPI OS on a new CD card, and the fermentrack install just worked perfect. But something is definitely wrong with the other installation.

 

[Thorrak]

pi@raspberrypi:~ $ cd fermentrack-tools
pi@raspberrypi:~/fermentrack-tools $ docker-compose down
ERROR:
Can't find a suitable configuration file in this directory or any
parent. Are you in the right directory?

Supported filenames: docker-compose.yml, docker-compose.yaml

pi@raspberrypi:~/fermentrack-tools $ dir
automated_install install.log sample.docker-compose.yml
docker-create-superuser.sh install.sh sample_envs
Dockerfile non_docker_install
docker-update.sh README.md

I just pushed an update to fermentrack_tools to GitHub. Try deleting your fermentrack_tools directory and then re-running the install command. It should now create a docker-compose.yml file for you, attempt to shut down the existing Fermentrack installation, then restart the installation. Once we get that done we should be able to proceed with debugging further.

 

[matridium]

I just pushed an update to fermentrack_tools to GitHub. Try deleting your fermentrack_tools directory and then re-running the install command. It should now create a docker-compose.yml file for you, attempt to shut down the existing Fermentrack installation, then restart the installation. Once we get that done we should be able to proceed with debugging further.

pi@raspberrypi:~ $ curl -L install.fermentrack.com| sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 123 100 123 0 0 602 0 --:--:-- --:--:-- --:--:-- 600
100 6918 100 6918 0 0 24104 0 --:--:-- --:--:-- --:--:-- 24104

<<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>>
:: Checking user
::: This script was launched as root. Although this used to be the recommended installation method,
::: installs now recommend being launched under the standard user (generally 'pi' for Raspberry Pi
::: installations). If you wish to cancel this installation and relaunch as a different user, press
::: Ctrl+C now. If you wish to continue to install as 'root' wait 10 seconds and the script will
::: continue.
:: Verifying free disk space...
::: Sufficent free space for installation
:: Installing dependencies using apt-get
::: installing git and build-essential.
::: (This may take a few minutes during which everything will be silent)
:::: All packages installed successfully.
:: Cloning fermentrack-tools repo from GitHub into /home/pi/fermentrack-tools
Unable to clone from GitHub


*** ERROR ERROR ERROR ERROR ERROR ***
----------------------------------
See above lines for error message
Setup NOT completed
this was after I tried deleting the folder, its not letting me delete the entire folder says its not empty. but I deleted everything in it.

 

[Thorrak]

pi@raspberrypi:~ $ curl -L install.fermentrack.com| sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 123 100 123 0 0 602 0 --:--:-- --:--:-- --:--:-- 600
100 6918 100 6918 0 0 24104 0 --:--:-- --:--:-- --:--:-- 24104

<<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>>
:: Checking user
::: This script was launched as root. Although this used to be the recommended installation method,
::: installs now recommend being launched under the standard user (generally 'pi' for Raspberry Pi
::: installations). If you wish to cancel this installation and relaunch as a different user, press
::: Ctrl+C now. If you wish to continue to install as 'root' wait 10 seconds and the script will
::: continue.
:: Verifying free disk space...
::: Sufficent free space for installation
:: Installing dependencies using apt-get
::: installing git and build-essential.
::: (This may take a few minutes during which everything will be silent)
:::: All packages installed successfully.
:: Cloning fermentrack-tools repo from GitHub into /home/pi/fermentrack-tools
Unable to clone from GitHub


*** ERROR ERROR ERROR ERROR ERROR ***
----------------------------------
See above lines for error message
Setup NOT completed
this was after I tried deleting the folder, its not letting me delete the entire folder says its not empty. but I deleted everything in it.

Try running sudo rm -rf fermentrack-tools to delete the folder

Of note - the new installation command is curl -L install.fermentrack.com | bash - not |sudo bash - if you pipe it to sudo, then you'll have to use sudo to delete it.

 

[jeeppilot]

I successfully reimaged the latest Raspberry Pi OS to my card and will run the Fermentrack install when it’s finished updating. I should have more info tomorrow. Thank you @Thorrak for all your help so far. As always you have gone above and beyond when I have needed assistance.

 

[matridium]

I’m going to work on this tomorrow.. even after deleting the folder with the command you told me to use the instillation still says that port 6379 is still in use but I deleted the entire folder for fermentrack. I looked up the port same as before redis is using the port along with fermentrack

 

[jeeppilot]

Well the brewery is back up and running! Wiping and restarting from scratch wasn’t nearly the process I thought it would be. The new OS installed and Fermentrack did smoothly as well. Immediately my off-network access was restored. Even the sensors and devices were automatically restored, except for my Tilt. Reinstalled TeamViewer.

I did have one question...I saw in the Fermentrack install log that Fermentrack-tools_redis_1 was created and then later was verified up to date. I assume this is something separate for what we were having a problem with earlier?

 

[Thorrak]

Well the brewery is back up and running! Wiping and restarting from scratch wasn’t nearly the process I thought it would be. The new OS installed and Fermentrack did smoothly as well. Immediately my off-network access was restored. Even the sensors and devices were automatically restored, except for my Tilt. Reinstalled TeamViewer.

I did have one question...I saw in the Fermentrack install log that Fermentrack-tools_redis_1 was created and then later was verified up to date. I assume this is something separate for what we were having a problem with earlier?

Sort of -- The install script's need to create that container (fermentrack-tools_redis_1) is the reason that it checks that you don't have an existing copy of Redis already installed. Since the install script created that container you should be fine going forward.

 

[matridium]

Sort of -- The install script's need to create that container (fermentrack-tools_redis_1) is the reason that it checks that you don't have an existing copy of Redis already installed. Since the install script created that container you should be fine going forward.

Well I did the same, Made a whole knew install on new sd card and reinstalled fermentrack. all went well until this morning. I had to reboot the pi because it had lost connection to my tilt. After reboot it goes back to saying cant recieve txt from LCS I cant control it any more. I did run the debug here is the output.
Tests Performed

Test	Parameter	Pass/Fail	Output
Device Status Test	active	Passed	Device active & managed by Circus
DNS Lookup Test	esp2779438.local	Passed	192.168.0.244
Connection Test	esp2779438.local	Passed	Connected
Controller Response Test	esp2779438.local	Passed	b'N:{"v":"0.2.4","n":0,"c":"00000000","s":0,"y":0,"b":"e","l":"3"}'
Cached IP Test	192.168.0.244	Passed	Available
Connection Test	192.168.0.244	Passed	Connected
Controller Response Test	192.168.0.244	Passed	b'N:{"v":"0.2.4","n":0,"c":"00000000","s":0,"y":0,"b":"e","l":"3"}'

 

[Thorrak]

After reboot it goes back to saying cant recieve txt from LCS I cant control it any more.

What is LCS? What is the exact error message you're seeing? What can't you control?

 

[jeeppilot]

Sort of -- The install script's need to create that container (fermentrack-tools_redis_1) is the reason that it checks that you don't have an existing copy of Redis already installed. Since the install script created that container you should be fine going forward.

Great. Well thanks again for the help. Good to have things running smoothly again!