Fermentrack: Fermentation monitoring & BrewPi-www Replacement for Raspberry Pi

[pers]

1. http://server_ip/ispindel/

Both of my iSpindels have the path/URI set to http://iSpindel_ip/ispindel/ and work fine.

Any idea why that is? Set them up so long ago can't remember the why or how I came up with that.

 

[Thorrak]

Both of my iSpindels have the path/URI set to http://iSpindel_ip/ispindel/ and work fine.

Any idea why that is? Set them up so long ago can't remember the why or how I came up with that.

No idea how/why that works. This is set on the iSpindel itself? It should fail, as the iSpindel would try to send itself its readings.

(With all the above said, I’ve been neck-deep in work on the FT2 iSpindel support, so I may be missing something from the previous implementation)

 

[pers]

No idea how/why that works. This is set on the iSpindel itself? It should fail, as the iSpindel would try to send itself its readings.

(With all the above said, I’ve been neck-deep in work on the FT2 iSpindel support, so I may be missing something from the previous implementation)

Yes, this is the screenshot of the iSpindle settings itself. The server field has the Fermentrack server ip and path/uri is the iSpindel ip.

It somehow works.

 

[Thorrak]

Yes, this is the screenshot of the iSpindle settings itself. The server field has the Fermentrack server ip and path/uri is the iSpindel ip.

It somehow works.

Wild that works, but it’s possibly taking advantage of an edge case in the way I constructed the Fermentrack URL paths. It should just be “ispindel” but it’s possible that it’s fine so long as it ends in “/ispindel”. (There could also be some processing taking place in the ispindel firmware - hard to know without digging into the code!)

But yeah - host should be your Fermentrack IP, port will typically be 80, and path should be ispindel.

 

[Abnormal1]

Hey there! Glad to hear it's been working for you over the years!

To answer your questions:

1. http://server_ip/ispindel/
2. Yes -- but you can tell from the URL you use to access Fermentrack as well, if you are still able to access it. If you are accessing it at http://<server_ip>/ then the port is 80. If you're accessing it at, for example, http://<server_ip>:1234/ then the port is 1234 (or whatever follows the colon). If you can't access the site then how you can tell depends on if you are using the docker or non-docker version.

If you are using the non-docker version then you can tell from you can also tell from the nginx configuration (if you're using the non-docker version) which is in /etc/nginx/sites-available/something.conf (I don't recall offhand what "something" is here -- if you ssh into the Pi and do 'cd /etc/nginx/sites-available' and then 'ls' you should see the file, and can just run 'cat <filename>'


If you are using the docker version, you can tell by changing to the Fermentrack tools directory and running `grep listen /compose/production/nginx/nginx.conf` . There should be a line like "listen [::]:123 default_server ipv6only=off;"(where 123 in this case is the port number)

Thorrak and Pers,

Thank you both for your help. I was able to confirm it was port 80. With a little tweaking and using UBI dots and the serial port to debug, I was able to get iSpindel to record values to my ferment tracker! With my 4 lb bag of sugar and water, I was also able to get it calibrated.

I'm going to start the sugar water fermenting as a first test. It's been a while since I made boozy root beer.

For what's it worth, my working settings are below. The path/uri is the http://server.ip/ispindel.

Happy to help troubleshoot or document any of this process for folx going forward.

 

[pers]

I have a wondering what could have went wrong question.

Had a perfect running Fermentrack setup using Linux Mint in Windows Hyper-V. I'm sure it was overkill but was looking for easy since my linux skills are limited.

As I started adding more projects to the machine with Hyper-V, realized it would probably be better to get a dedicated machine and learn more about proxmox.

Found great deal on used mini pc from ebay, got proxmox up and running, and spun up an Ubuntu Server VM. Got Fermentrack running on Ubuntu Server with no issues. Made a Fermentrack backup and restored it. Everything seemed fine and didn't pay attention to it till a couple days before brew day.

When I checked in before brew day, realized there were all sorts of problems. Would constantly get the Internal Server Error every 6-24 hours needing to run the ./docker-update.sh to fix. My first brewpi device would lose connection and restart every couple of minutes. The second one completely became unusable (that was when I was scrambling to flash the S2). Managed to get the S2 working only to have errors with the temperature sensors. Replaced the temperature sensors with new ones, which seemed to fix the errors. But still had the other issues.

After a week of nursing the fermentations to complete, decided to try a new VM with Mint. Restored everything and all the errors are gone. Been completely stable for 2 days.

Bad install of Ubuntu Server? Bad backup and restore? Your instructions for proxmox use Ubuntu Server so I'm sure it's fine to use.

Sorry for long post but it was a rough 2 weeks with this, home air conditioning problems, and water main problems while brewing. Turns out having your water go to a dribble in the middle of a double brew day isn't fun.

 

[pers]

Spoke too soon. Got my first "Internal Server Error".

The problem mirrors this post:

https://www.homebrewtalk.com/thread...for-raspberry-pi.649303/page-67#post-10298635

with "Internal Server Error" and oddly rendered web pages cycling when you refresh the page.

What is best way to get the Nginx logs?

 

[Thorrak]

I have a wondering what could have went wrong question.

Had a perfect running Fermentrack setup using Linux Mint in Windows Hyper-V. I'm sure it was overkill but was looking for easy since my linux skills are limited.

As I started adding more projects to the machine with Hyper-V, realized it would probably be better to get a dedicated machine and learn more about proxmox.

Found great deal on used mini pc from ebay, got proxmox up and running, and spun up an Ubuntu Server VM. Got Fermentrack running on Ubuntu Server with no issues. Made a Fermentrack backup and restored it. Everything seemed fine and didn't pay attention to it till a couple days before brew day.

When I checked in before brew day, realized there were all sorts of problems. Would constantly get the Internal Server Error every 6-24 hours needing to run the ./docker-update.sh to fix. My first brewpi device would lose connection and restart every couple of minutes. The second one completely became unusable (that was when I was scrambling to flash the S2). Managed to get the S2 working only to have errors with the temperature sensors. Replaced the temperature sensors with new ones, which seemed to fix the errors. But still had the other issues.

After a week of nursing the fermentations to complete, decided to try a new VM with Mint. Restored everything and all the errors are gone. Been completely stable for 2 days.

Bad install of Ubuntu Server? Bad backup and restore? Your instructions for proxmox use Ubuntu Server so I'm sure it's fine to use.

Sorry for long post but it was a rough 2 weeks with this, home air conditioning problems, and water main problems while brewing. Turns out having your water go to a dribble in the middle of a double brew day isn't fun.

Oh man! I feel you on the busted brew days. Thankfully I haven't had water problems (yet?), but I definitely realized the impeller on my pump was busted after I had already mashed in a few weeks ago. Thankfully I had a backup (but it was a backup I had never used before, which - unbeknownst to me - had an open air release valve. Sticky shoes are fun!)

Great question on what happened -- and unfortunately, I don't have a good answer for you. The temperature sensors are managed independently from the Fermentrack install, so there's no relationship between those two problems, but that's not any comfort vs. having things disconnect.

Spoke too soon. Got my first "Internal Server Error".

The problem mirrors this post:

https://www.homebrewtalk.com/thread...for-raspberry-pi.649303/page-67#post-10298635

with "Internal Server Error" and oddly rendered web pages cycling when you refresh the page.

What is best way to get the Nginx logs?

To see the logs, you can run the appropriate "docker logs" command, but you will need the correct container name which can be found by running "docker ps". For me, for example, it is:

docker logs fermentrack-tools-nginx-1

With that said... I don't really know what to expect it to say for the issue you quoted. Internal server error/oddly rendering pages points to some kind of filesystem issue, but unless you have something funky going on with your proxmox settings (or a hard drive is dying!) you shouldn't experience any problems. If I recall correctly the guy you linked ended up determining that his issue was the power supply he was using for his Raspberry Pi, which makes sense as SD card operations can be power hungry.

 

[pers]

Oh man! I feel you on the busted brew days. Thankfully I haven't had water problems (yet?), but I definitely realized the impeller on my pump was busted after I had already mashed in a few weeks ago. Thankfully I had a backup (but it was a backup I had never used before, which - unbeknownst to me - had an open air release valve. Sticky shoes are fun!)

Great question on what happened -- and unfortunately, I don't have a good answer for you. The temperature sensors are managed independently from the Fermentrack install, so there's no relationship between those two problems, but that's not any comfort vs. having things disconnect.


To see the logs, you can run the appropriate "docker logs" command, but you will need the correct container name which can be found by running "docker ps". For me, for example, it is:

docker logs fermentrack-tools-nginx-1

With that said... I don't really know what to expect it to say for the issue you quoted. Internal server error/oddly rendering pages points to some kind of filesystem issue, but unless you have something funky going on with your proxmox settings (or a hard drive is dying!) you shouldn't experience any problems. If I recall correctly the guy you linked ended up determining that his issue was the power supply he was using for his Raspberry Pi, which makes sense as SD card operations can be power hungry.

The log doesn't appear to show anything useful. The attached pic shows what came up.

Guess it's gonna remain a mystery because I can't see it being a ssd issue, swapped the one that came with mini pc with a very lightly used one. Ran some checks on it and everything appears normal.

Also have 2 other VMs running with web servers in proxmox that don't seem to have any issues. Not knowing much about proxmox I basically used the default settings when creating all the VMs.

Realized that if I refresh the page enough it will eventually cycle to a proper visual and functional homepage. Each input change will register but then popup a weird render when changed. Can then refresh to reach a proper render. A little annoying but no real reason to run the ./docker-update.sh command all the time.

Will keep you updated if anything noticible happens.

 

[pers]

I noticed a bunch of errors and warnings when I run ./docker-update.sh. Vaguely remember reading about in an earlier part of thread but can't find it. It's probably nothing but figured I'd post just in case something isn't right.

WARN[0000] /home/michael/fermentrack-tools/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Pulling 5/5
 ! redis Warning            pull access denied for ferme...                0.4s
 ! nginx Warning            pull access denied for ferme...                0.4s
 ✔ django Pulled                                                           0.5s
 ! postgres Warning         pull access denied for fe...                   0.4s
 ✔ tiltbridge-junior Pulled                                                0.5s
WARNING: Some service image(s) must be built from source by running:
    docker compose build nginx postgres redis
3 errors occurred:
        * Error response from daemon: pull access denied for fermentrack_nginx, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
        * Error response from daemon: pull access denied for fermentrack_postgres, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
        * Error response from daemon: pull access denied for fermentrack_redis, repository does not exist or may require 'docker login': denied: requested access to the resource is denied


latest: Pulling from jdbeeler/fermentrack
Digest: sha256:67a85dcbe49836b5ca0e7be757075018f0ea77a0b20fb89fe94f43e2d7ad47ee
Status: Image is up to date for jdbeeler/fermentrack:latest
docker.io/jdbeeler/fermentrack:latest
WARN[0000] /home/michael/fermentrack-tools/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 5/5
 ✔ Container fermentrack-tools-tiltbridge-junior-1  Removed               10.1s
 ✔ Container fermentrack-tools-nginx-1              Removed                0.1s
 ✔ Container fermentrack-tools-django-1             Removed               10.1s
 ✔ Container fermentrack-tools-redis-1              Removed                0.1s
 ✔ Container fermentrack-tools-postgres-1           Removed                0.1s
WARN[0000] /home/michael/fermentrack-tools/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
#1 [internal] load local bake definitions
#1 reading from stdin 1.49kB done
#1 DONE 0.0s

#2 [redis internal] load build definition from Dockerfile
#2 transferring dockerfile: 188B done
#2 DONE 0.0s

#3 [postgres internal] load build definition from Dockerfile
#3 transferring dockerfile: 268B done
#3 DONE 0.0s

#4 [nginx internal] load build definition from Dockerfile
#4 transferring dockerfile: 486B done
#4 DONE 0.0s

#5 [redis internal] load metadata for docker.io/library/redis:6.0
#5 ...

#6 [postgres internal] load metadata for docker.io/library/postgres:12.3
#6 DONE 0.2s

#7 [redis internal] load .dockerignore
#7 transferring context: 2B done
#7 DONE 0.0s

#8 [postgres 1/4] FROM docker.io/library/postgres:12.3@sha256:a06e6e6e519b7a329c419f8221edec66cfc45511e8b80e262c12103ba745cf19
#8 DONE 0.0s

#9 [postgres internal] load build context
#9 transferring context: 5.02kB done
#9 DONE 0.0s

#10 [nginx internal] load metadata for docker.io/library/nginx:1.18.0-alpine
#10 DONE 0.3s

#5 [redis internal] load metadata for docker.io/library/redis:6.0
#5 DONE 0.3s

#11 [postgres 3/4] RUN chmod +x /usr/local/bin/maintenance/*
#11 CACHED

#12 [postgres 2/4] COPY ./compose/production/postgres/maintenance /usr/local/bin/maintenance
#12 CACHED

#13 [postgres 4/4] RUN mv /usr/local/bin/maintenance/* /usr/local/bin     && rmdir /usr/local/bin/maintenance
#13 CACHED

#14 [nginx 1/2] FROM docker.io/library/nginx:1.18.0-alpine@sha256:93baf2ec1bfefd04d29eb070900dd5d79b0f79863653453397e55a5b663a6cb1
#14 DONE 0.0s

#15 [redis 1/2] FROM docker.io/library/redis:6.0@sha256:b99ffd0554dc8d300230b9d1b9f2a129a6abf595bf8589883beb980ed1feae3d
#15 DONE 0.0s

#16 [nginx internal] load build context
#16 transferring context: 166B done
#16 DONE 0.0s

#17 [postgres] exporting to image
#17 exporting layers done
#17 writing image sha256:2c734d039f00b479c403131c78b9710910b46c53f3019d93890bf2760340fd36 done
#17 naming to docker.io/library/fermentrack_postgres done
#17 DONE 0.0s

#18 [redis internal] load build context
#18 transferring context: 85.03kB done
#18 DONE 0.0s

#19 [nginx 2/2] COPY ./compose/production/nginx/nginx.conf /etc/nginx/nginx.conf
#19 CACHED

#20 [redis 2/2] COPY ./compose/production/redis/redis.conf /usr/local/etc/redis/redis.conf
#20 CACHED

#21 [redis] exporting to image
#21 exporting layers done
#21 writing image sha256:35665aefb9607c297fa931fda3a8008ffea6494936143c81d4a4543cc70d47ce done
#21 naming to docker.io/library/fermentrack_redis done
#21 DONE 0.0s

#22 [nginx] exporting to image
#22 exporting layers done
#22 writing image sha256:9f0872710621438ed96fac0f0515805c7a2aaf1f0de861fb7cfc65ffc77fe3ee done
#22 naming to docker.io/library/fermentrack_nginx done
#22 DONE 0.0s

#23 [postgres] resolving provenance for metadata file
#23 DONE 0.0s

#24 [redis] resolving provenance for metadata file
#24 DONE 0.0s

#25 [nginx] resolving provenance for metadata file
#25 DONE 0.0s
[+] Building 3/3
 ✔ fermentrack_nginx     Built                                             0.0s
 ✔ fermentrack_postgres  Built                                             0.0s
 ✔ fermentrack_redis     Built                                             0.0s
WARN[0000] /home/michael/fermentrack-tools/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
WARN[0000] mount of type `volume` should not define `bind` option
WARN[0000] mount of type `volume` should not define `bind` option
[+] Creating 2/2
 ✔ Container fermentrack-tools-redis-1     Created                         0.1s
 ✔ Container fermentrack-tools-postgres-1  Created                         0.1s
[+] Running 2/2
 ✔ Container fermentrack-tools-redis-1     Started                         0.1s
 ✔ Container fermentrack-tools-postgres-1  Started                         0.1s
WARN[0000] mount of type `volume` should not define `bind` option
WARN[0000] mount of type `volume` should not define `bind` option
WARN[0000] mount of type `volume` should not define `bind` option
PostgreSQL is available
Operations to perform:
  Apply all migrations: admin, app, auth, backups, constance, contenttypes, external_push, firmware_flash, gravity, sessions
Running migrations:
  No migrations to apply.
WARN[0000] /home/michael/fermentrack-tools/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
WARN[0000] mount of type `volume` should not define `bind` option
WARN[0000] mount of type `volume` should not define `bind` option
WARN[0000] mount of type `volume` should not define `bind` option
WARN[0000] mount of type `volume` should not define `bind` option
[+] Running 3/4
[+] Running 5/5rmentrack-tools-redis-1     Running                         0.0s
 ✔ Container fermentrack-tools-redis-1              Running                0.0s
 ✔ Container fermentrack-tools-postgres-1           Running                0.0s
 ✔ Container fermentrack-tools-django-1             Started                0.2s
 ✔ Container fermentrack-tools-nginx-1              Started                0.3s
 ✔ Container fermentrack-tools-tiltbridge-junior-1  Started                0.4s